marvs/kantan-dev

kantan-finish-feature

Use when a feature is complete or wrapping up implementation in a Rails + React app. Records how the feature was built as a docs file and captures new reusable patterns into each repo's conventions file.

kantan-plan-feature

Use when planning a feature or before writing implementation code in a Rails + React app. Produces an approved implementation plan, asking clarifying questions and grounding the plan in repo conventions and prior feature docs. Never starts implementation.

kantan-review-feature

Use when implementation is complete, before reporting or marking any feature as done, and before finishing a feature in a Rails + React app. Mandatory review step of the Kantan workflow — never skip it. Performs an expert Rails + React code review of the…

kantan-backend-tdd

Use when implementing Rails backend code — models, services, controllers, jobs, or APIs. Follows the backend repo's own conventions, applies test-driven development, and keeps the test suite and linter green.

kantan-frontend

Use when implementing React frontend changes — components, hooks, pages, or UI. Follows the frontend repo's own stack and conventions, and keeps the formatter and linter clean.

kantan-start-feature

Use when starting a new feature or building something new in a Rails + React app. Trigger on messages like "I want to build a new feature", "let's add X", or "new feature" — even in plan mode, and even if branches are already set up or requirements are…