Commandkit

CommandKit Core

Activation guidance

Use this skill for framework-level architecture and implementation:

• command and event file placement
• commandkit.config strategy and plugin wiring
• middleware lifecycle behavior
• JSX interaction components and handlers
• project structure validation and migration to convention-based layouts

Required filesystem expectations

• commandkit.config.ts (or .js) at project root
• src/app/commands/** for commands
• src/app/events/** for events
• optional plugin-specific folders (src/app/locales, src/app/tasks, src/workflows) when those plugins are enabled

Configuration expectations

• Use defineConfig from commandkit/config.
• Register plugins explicitly in plugins: [].
• Use startup guards like noBuildOnly() for runtime-only setup (for example task/driver init).
• Keep environment-sensitive plugin toggles explicit.

Execution workflow

1. Validate structure and baseline config first.
2. Place command/event files in convention paths.
3. Implement command logic with typed context and metadata.
4. Add middleware only for cross-cutting concerns.
5. Verify runtime behavior with local dev command.

Guardrails

• Do not invent CommandKit APIs.
• Avoid registration-heavy patterns that bypass convention discovery.
• Keep handlers small and move reusable logic to helpers/services.

Reference index

Tool index