Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

backend-mindset

Étoiles19

Forks1

Mis à jour14 juillet 2026 à 14:27

Build robust backend systems — APIs (REST, GraphQL, gRPC), authentication (OAuth 2.1, JWT), databases, performance optimization, security (OWASP Top 10), scalability patterns (microservices, caching, sharding), and testing. Use when designing APIs, implementing auth, optimizing queries, handling security vulnerabilities, building microservices, or developing production-ready backend systems.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

DangQuangSE

DangQuangSE/team-development-skills

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Développeurs de logicielsProfessions informatiques et mathématiques·SOC 15-1252

Explorateur de fichiers

9 fichiers

SKILL.md

readonly

name	backend-mindset
description	Build robust backend systems — APIs (REST, GraphQL, gRPC), authentication (OAuth 2.1, JWT), databases, performance optimization, security (OWASP Top 10), scalability patterns (microservices, caching, sharding), and testing. Use when designing APIs, implementing auth, optimizing queries, handling security vulnerabilities, building microservices, or developing production-ready backend systems.
license	MIT
version	1.1.0

Backend Development Skill

References

File	Covers
`.cursor/skills/backend-mindset/references/api-design.md`	REST, GraphQL, gRPC — URL rules, status codes, protocol selection
`.cursor/skills/backend-mindset/references/authentication.md`	OAuth 2.1, JWT, RBAC, MFA, session management
`.cursor/skills/backend-mindset/references/security.md`	OWASP Top 10 (2025), rate limiting, headers, secrets
`.cursor/skills/backend-mindset/references/performance.md`	Indexing, caching patterns, load balancing, async processing
`.cursor/skills/backend-mindset/references/architecture.md`	Microservices patterns, event-driven, CQRS, scalability
`.cursor/skills/backend-mindset/references/testing.md`	TDD, test pyramid, contract testing, migration tests
`.cursor/skills/backend-mindset/references/code-quality.md`	SOLID, design patterns, refactoring signals

Quick Decision Guide

Need	Choose
Public / browser clients	REST or GraphQL
Internal high-throughput	gRPC
Flexible data fetching	GraphQL
Streaming	gRPC (bidirectional) or SSE
Single team, unclear domain	Monolith
Multiple autonomous teams	Microservices
Audit trail required	Event Sourcing
Read/write load imbalance	CQRS
Task >200ms off request path	Async queue
Session across instances	Redis (never in-process)

Defaults

Every non-public endpoint requires explicit auth declaration — no implicit defaults
Input validation at every system boundary (API handler, event consumer, file parser)
Parameterized queries everywhere — never string-interpolate user input
Rate limiting on auth endpoints, public API, and file upload (see security.md for thresholds)
Integration tests hit real infrastructure (Testcontainers) — in-memory substitutes hide real bugs
TDD: write the failing test before any implementation
Services return result envelopes — never throw for expected failures (404, 400, 409)

Plus depuis ce dépôt

même dépôt

ck-brainstorm

DangQuangSE/team-development-skills

Explore and debate solutions before writing code. Use when the user poses a design question, asks "how should I approach X", wants to think through options before committing, or says anything like "let's brainstorm", "what's the best way to...", "I'm not sure how to tackle this", or "should I use X or Y". Always runs before /ck:plan for novel or ambiguous features. No code is written — only: explore → clarify → spec → report.

2026-07-1419

ck-cook

DangQuangSE/team-development-skills

Implement a feature phase by phase from a phased JSON master or Markdown plan. Before each phase, confirm whether to create/run unit tests and whether to run ck:quality, unless explicit flags supply those choices. Supports token-budgeted execution, resumable state, and TDD handoff to ck:test.

2026-07-1419

ck-fix

DangQuangSE/team-development-skills

Fix a bug using Scout → Diagnose → Fix → Review → Finalize. Use when the user pastes an error message, stack trace, or test failure, or says "fix this bug", "something's broken", "tests are failing", "I'm getting an error". Also accepts `--from-quality <report>` or `--from-test <report>` to fix exactly the findings/failures a report lists. Modes (pick one): --fast (trivial errors — lint, type, build — skip scout and review), --hard (mandatory review, no auto-approve).

2026-07-1419

ck-plan-json

DangQuangSE/team-development-skills

Create a machine-readable phased JSON plan bundle from a spec or feature description. Produces a compact master manifest plus per-phase step files for resumable ck:cook execution.

2026-07-1419

ck-plan

DangQuangSE/team-development-skills

Plan a feature or system before implementation. Use when the user says "plan this", "I want to build X", "how do I implement Y", or when /ck:brainstorm produces a spec.md. Always run before /ck:cook. Modes (pick one): --fast (simple, single-file), --hard (research + red-team + validate). Composable flag (combine with any mode): --tdd — propagates into the cook pipeline. Every phase gets Design Constraints and Quality/Testing State; ck:cook confirms optional test and quality checks per phase.

2026-07-1419

ck-quality

DangQuangSE/team-development-skills

Independent senior-engineering quality auditor — architecture, ownership, domain integrity, abstraction, and maintainability. Use as `--gate` inside the ck:cook pipeline (blocks a phase on BLOCKER/HIGH/current-change MEDIUM findings) or call directly with `--audit`, `--diff`, `--changed` on any repository, directory, or file. Never writes tests and never edits production code — it returns structured findings only; ck:cook or ck:fix apply the fix.

2026-07-1419

name	backend-mindset
description	Build robust backend systems — APIs (REST, GraphQL, gRPC), authentication (OAuth 2.1, JWT), databases, performance optimization, security (OWASP Top 10), scalability patterns (microservices, caching, sharding), and testing. Use when designing APIs, implementing auth, optimizing queries, handling security vulnerabilities, building microservices, or developing production-ready backend systems.
license	MIT
version	1.1.0

Backend Development Skill

References

File	Covers
`.cursor/skills/backend-mindset/references/api-design.md`	REST, GraphQL, gRPC — URL rules, status codes, protocol selection
`.cursor/skills/backend-mindset/references/authentication.md`	OAuth 2.1, JWT, RBAC, MFA, session management
`.cursor/skills/backend-mindset/references/security.md`	OWASP Top 10 (2025), rate limiting, headers, secrets
`.cursor/skills/backend-mindset/references/performance.md`	Indexing, caching patterns, load balancing, async processing
`.cursor/skills/backend-mindset/references/architecture.md`	Microservices patterns, event-driven, CQRS, scalability
`.cursor/skills/backend-mindset/references/testing.md`	TDD, test pyramid, contract testing, migration tests
`.cursor/skills/backend-mindset/references/code-quality.md`	SOLID, design patterns, refactoring signals

Quick Decision Guide

Need	Choose
Public / browser clients	REST or GraphQL
Internal high-throughput	gRPC
Flexible data fetching	GraphQL
Streaming	gRPC (bidirectional) or SSE
Single team, unclear domain	Monolith
Multiple autonomous teams	Microservices
Audit trail required	Event Sourcing
Read/write load imbalance	CQRS
Task >200ms off request path	Async queue
Session across instances	Redis (never in-process)

Defaults

Every non-public endpoint requires explicit auth declaration — no implicit defaults
Input validation at every system boundary (API handler, event consumer, file parser)
Parameterized queries everywhere — never string-interpolate user input
Rate limiting on auth endpoints, public API, and file upload (see security.md for thresholds)
Integration tests hit real infrastructure (Testcontainers) — in-memory substitutes hide real bugs
TDD: write the failing test before any implementation
Services return result envelopes — never throw for expected failures (404, 400, 409)