Use when wiring a single-concern lifecycle integration (Swagger, DevTools, Sentry, Redis client).
forinda/kick-fullstack-netlify
- Latest recorded source activity
- SkillsMP catalog refreshed
- skills collected
- 30
- GitHub stars
- 0
- GitHub forks
- 0
Loading the repository README…
Skills in this repository
Showing 30 of 30 collected skills.
Use when the user asks to add a new feature module (controller + service + repo + DTOs).
Use when scaffolding a feature that bundles modules + DI + middleware + adapters together (auth, monitoring suite, multi-tenant scaffolding).
Use when HMR is silently doing full restarts on every save, or createTestApp can't find the app handle.
Use as a quick reference for the most common kick CLI workflows — scaffolding, dev/build/start, generation, inspection.
Use when a middleware's only job is to set ctx values consumed elsewhere — replace with defineHttpContextDecorator (HTTP) or defineContextDecorator (transport-agnostic).
Patterns to refuse outright when the user asks for them — they break v4 invariants.
Use FIRST when unsure about any KickJS API, option, or behaviour — before guessing from memory or inferring from surrounding code.
Use when ConfigService.get('SOME_KEY') returns undefined or @Value silently falls back to process.env.
Use when adding auth checks, request-scoped values, or anything "before the handler" — picks between a guard, a middleware, and a context contributor.
Use when adding a paginated/filterable list route — emit ctx.qs + ctx.paginate with an allow-list.
Use after a KickJS version bump to sync the .agents/ docs with the latest CLI templates.
Use when src/index.ts is accumulating module/middleware/plugin/adapter literals.
Use when code reads template files / JSON fixtures via fs.readFile + path arithmetic — switch to assets.<ns>.<key>() and the kick.config.ts assetMap.
Use when adding a Vitest test that exercises an HTTP route or DI graph.
Use when wiring a single-concern lifecycle integration (Swagger, DevTools, Sentry, Redis client).
Use when the user asks to add a new feature module (controller + service + repo + DTOs).
Use when scaffolding a feature that bundles modules + DI + middleware + adapters together (auth, monitoring suite, multi-tenant scaffolding).
Use when HMR is silently doing full restarts on every save, or createTestApp can't find the app handle.
Use as a quick reference for the most common kick CLI workflows — scaffolding, dev/build/start, generation, inspection.
Use when a middleware's only job is to set ctx values consumed elsewhere — replace with defineHttpContextDecorator (HTTP) or defineContextDecorator (transport-agnostic).
Patterns to refuse outright when the user asks for them — they break v4 invariants.
Use FIRST when unsure about any KickJS API, option, or behaviour — before guessing from memory or inferring from surrounding code.
Use when ConfigService.get('SOME_KEY') returns undefined or @Value silently falls back to process.env.
Use when adding auth checks, request-scoped values, or anything "before the handler" — picks between a guard, a middleware, and a context contributor.
Use when adding a paginated/filterable list route — emit ctx.qs + ctx.paginate with an allow-list.
Use after a KickJS version bump to sync the .agents/ docs with the latest CLI templates.
Use when src/index.ts is accumulating module/middleware/plugin/adapter literals.
Use when code reads template files / JSON fixtures via fs.readFile + path arithmetic — switch to assets.<ns>.<key>() and the kick.config.ts assetMap.
Use when adding a Vitest test that exercises an HTTP route or DI graph.
Install with an AI assistant
Copy this prompt into the AI assistant you're using.
Follow https://skillsmp.com/skill-install/prompt.md to install Agent Skills from https://github.com/forinda/kick-fullstack-netlify.