expressjs-rest-api
Purpose
Use this skill to design and implement Express 5 REST APIs in a way that fits the target repository first.
When local patterns exist, use them as the source of truth. When they do not, use the references in this skill as portable patterns to generate a coherent structure rather than one-off route code.
This skill is about Express API structure and boundaries, not database design. Persistence guidance in this skill stops at the boundary:
- controllers and services should depend on repositories, not datastore clients
- repositories should be aggregated behind one context or composition object when multiple repositories are used together
- business and domain layers should not construct datastore-specific requests directly
Portable references live in references/. Load only the patterns needed for the task:
More from stack-shifter/skills
spec-workflow
Drives a spec-first workflow where the spec is the locked source of truth and implementation runs through plan mode. Use whenever the user wants a feature spec drafted with explicit clarification questions, locked requirements in `docs/specs`, or a "do the next chunk then check in" implementation loop.
26cdk-rest-api-postgres
Designs and implements REST APIs on AWS using the target repository's CDK patterns first, with AWS Lambda handlers and Postgres via Drizzle as the default datastore. Use this whenever the user wants to add or modify API Gateway REST endpoints, Lambda handlers, Cognito auth, request models, reusable CDK constructs, Drizzle schema, SQL repositories, or database-backed CRUD routes, even if they only ask for "an endpoint", "a handler", "a table", "a repository", or "some CDK wiring".
12cdk-rest-api
Designs and implements REST APIs on AWS using the target repository's CDK patterns first. Use this whenever the user wants to add or modify API Gateway REST endpoints, Lambda handlers, Cognito auth, middleware, request models, reusable CDK constructs, runtime composition, scheduled jobs, or repository-backed CRUD routes, even if they only ask for "an endpoint", "a handler", "some CDK wiring", or "an API route".
1dynamodb-design
Designs DynamoDB data models from access patterns first. Use this whenever the user needs help modeling a DynamoDB schema, choosing between single-table and multi-table design, defining partition and sort keys, GSIs, item collections, one-to-many or many-to-many relationships, filtering, sorting, uniqueness, TTL, pagination, or deciding whether DynamoDB is even the right fit for the workload.
1cdk-rest-api-dynamodb
Designs and implements REST APIs on AWS using the target repository's CDK patterns first, with AWS Lambda handlers and DynamoDB as the primary datastore. Use this whenever the user wants to add or modify API Gateway REST endpoints, Lambda handlers, Cognito auth, request models, reusable CDK constructs, or DynamoDB-backed CRUD routes, even if they only ask for "an endpoint", "a handler", "a table", or "some CDK wiring".
1