backend-patterns
/backend-patterns
Wdraża API, dostęp do danych, cache i zadania w usługach Node.js i TypeScript, dopasowując wzorce do stosu.
- Autor
- Selenophile2004 ↗
- Repozytorium
- applied-agent-skills ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 03.11.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 5
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 2
Brak sygnałów. Repozytorium zmienione 03.11.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Wdraża API, dostęp do danych, cache i zadania w usługach Node.js i TypeScript, dopasowując wzorce do stosu.
Oryginalny opis (EN)
Implement backend APIs, data access, caches and jobs for Node.js/TypeScript services; use for substantive server-side changes, with patterns adapted to the existing stack.
Jak działa
- Specialized cases and output contract
- Task contract
Podgląd SKILL.md
--- name: backend-patterns description: Implement backend APIs, data access, caches and jobs for Node.js/TypeScript services; use for substantive server-side changes, with patterns adapted to the existing stack. metadata: source: https://github.com/WorldFlowAI/everything-claude-code source-commit: 432485ba6b92c14fb357276a98957f348bcff9ee adaptation: Agent Skills; English; task-scoped; 2026-11-02 --- # Backend implementation patterns Use for implementing or materially changing Node.js/TypeScript services, Express or Next.js API routes, database access, caches and background jobs. Preserve the project's stack and contracts; other stacks can reuse general principles without importing Node-specific APIs. - Inspect the relevant endpoint, data model, authorization boundary and existing implementation. Choose only the layers the task needs; do not introduce repositories, queues or microservices by default. - Keep API contracts explicit: runtime input validation, consistent errors, pagination/filtering, status codes and backwards compatibility. Enforce resource/tenant authorization separately from authentication. - Select needed fields, batch related queries and inspect actual query behavior to avoid N+1 work. Use transactions for genuine atomic invariants, parameterized operations and migrations appropriate to the change. - Design caches with explicit keys, tenant/permission isolation, freshness and invalidation. Choose shared storage when cross-instance consistency matters; process-local caches and limiters are not distributed guarantees. - Retry transient failures with bounds, backoff and cancellation where appropriate. Retry writes only with idempotency or equivalent protection. Preserve meaningful errors, timeouts and partial-failure state. - Use durable queues for jobs that must survive process restarts. Define retries, deduplication, concurrency and failure handling according to requirements; an in-memory example is not a durable job system. - Keep logs useful and redacted; preserve request correlation without exposing credentials or user data. Validate affected contracts, data integrity and failure paths with existing commands, broadening checks when dependencies require it. - Make focused changes and reuse existing libraries/runtime. Do not add infrastructure, dependencies or deployments solely to conform to a pattern. For implementation illustrations, search the relevant API, Database, Caching, Error Handling, Authorization or Background Jobs heading in [upstream reference](https://github.com/WorldFlowAI/everything-claude-code/blob/432485ba6b92c14fb357276a98957f348bcff9ee/skills/backend-patterns/SKILL.md). Read only needed sections. The samples require validation against current library APIs; do not copy them as complete middleware, authorization or durable-queue implementations. ## Specialized cases and output contract For substantive relevant work, read [the applied workflow](references/transactional-api-cases.md). Keep unrelated references unloaded. ## Task contract Inputs: Existing stack/contracts, data invariants, tenancy, durability requirements and tests. Deliver: Focused implementation/design, contract/invariant notes and relevant failure-path verification. Acceptance: No blind write retries; concurrency invariants; tenant-safe cache/invalidation; durable required jobs; justified infrastructure.
Pliki w paczce (5)
- LICENSE 1 KB
- README.md 1 KB
- SKILL.md 3 KB
- agents/openai.yaml 1 KB
- references/transactional-api-cases.md 1 KB
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · Selenophile2004/applied-agent-skills | 100 | MIT |
| Sanit-mann/The-Insectoids | 100 | MIT |
| tadokoro-ryusuke/cc-plugins | 100 | MIT |
| kensaurus/cursor-kenji | 100 | MIT |
| tranhieutt/software_development_department | 100 | MIT |
| affaan-m/ECC | 95 | MIT |
| affaan-m/ECC | 95 | MIT |
| SHRIJANAGAIN/Nemo-Cli | 95 | Apache-2.0 |
| andersonlimahw/lemon-ai-hub | 95 | MIT |
Migawka bazy z 13.11.2026 · wersja paczki 79dcce255cbe (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 1 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100node-patterns
Podaje wzorce architektury backendu, projektowania API i optymalizacji bazy dla Node.js, Express i tras API w Next.js. - 100backend-dev-guidelines
Ustala wytyczne dla backendu Node.js, Express i TypeScript: architektura warstwowa, obsługa błędów, walidacja, middleware, dostęp do bazy danych i testy. - 100backend-api-builder
Projektuje i buduje backendy API w Pythonie lub Node: trasy, autoryzację, bazy, zadania w tle i wdrożenie. - 100nodejs-backend
Stosuje wzorce backendu Node.js: dobór frameworka, architektura warstwowa, TypeScript, walidacja, obsługa błędów, bezpieczeństwo i wdrożenie produkcyjne. - 90node-typescript-backend
Pomaga budować produkcyjne backendy w Node.js i TypeScript z Fastify, NestJS lub Express: strukturę, walidację, błędy i wydajność. - 100backend
Podaje wzorce tworzenia backendu: usługi, obsługa błędów, logowanie i cache, przy budowie serwisów, API i mikroserwisów.