forinda

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 adding a kick <name> command, a kick g <name> generator, or a typegen emitter to this project or a package it ships.

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 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 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 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 adding a kick <name> command, a kick g <name> generator, or a typegen emitter to this project or a package it ships.

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 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 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 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 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 when ConfigService.get('SOME_KEY') returns undefined or @Value silently falls back to process.env.

Pointer file. The actual KickJS framework skill lives at skills/kickjs-skill/SKILL.md inside this repository. Use scripts/install.sh to install it into ~/.claude/skills/ — do NOT install this root file as a skill.

Use whenever working in or with KickJS — the decorator-driven Node.js framework on Express 5 + TypeScript. Triggers on `@forinda/kickjs*` imports, `kick.config.ts`, `kick new`/`kick g`/`kick add` commands, decorators like `@Controller` / `@Service` /…