create-agents-workflow

Verify Clean Architecture layer boundaries — domain and application must not import infrastructure. Use when the user says 'check boundaries', 'verify architecture', 'run boundary check', 'validate layers', or after any code change that touches domain or application layers. Don't use for writing new code — use the appropriate create-usecase or add-endpoint skill.

Write an Architecture Decision Record (ADR) capturing a significant technical decision. Use when the user says 'document this decision', 'write an ADR', 'record why we chose X', 'add a technical decision'. Don't use for user stories — use write-spec. Don't use for general documentation — use write-readme.

Create or update a README.md for a module, feature, or the project root. Use when the user says 'write a README', 'update the docs', 'document this module', 'add a getting started guide'. Don't use for architecture decisions — use write-adr. Don't use for user stories — use write-spec.

Create or update a user story with acceptance criteria following the As-a/I-want/So-that format. Use when the user says 'write a user story', 'create a spec', 'define requirements for X', 'add acceptance criteria'. Don't use for architecture decisions — use write-adr. Don't use for README files — use write-readme.

Add a new Gin HTTP endpoint wired to a Use Case following Clean Architecture in a Go project. Use when the user says 'add endpoint', 'create route', 'new API', 'expose X via HTTP', 'add a GET/POST/PUT/DELETE'. Don't use for business logic — use create-usecase-go. Don't use for tests — use write-unit-test-go.

Scaffold a new Use Case following Clean Architecture with TDD in a Go project. Use when the user says 'create use case', 'new service', 'new business operation', 'add X logic', 'implement Y feature'. Don't use for HTTP endpoints — use add-endpoint-gin. Don't use for frontend components — use create-component-mantine or create-component-mui.

Write a unit test for a Use Case or domain entity using Go's standard testing package with table-driven tests. Use when the user says 'write test', 'add tests', 'test this', 'TDD', 'cover X with tests'. Don't use for HTTP handler tests — use add-endpoint-gin for the handler, then test the use case. Don't use for integration tests with real databases.

Add a new Spring Boot REST endpoint wired to a Use Case following Clean Architecture. Use when the user says 'add endpoint', 'create route', 'new API', 'expose X via HTTP', 'add a GET/POST/PUT/DELETE'. Don't use for business logic — use create-usecase-spring. Don't use for tests — use write-unit-test-junit.

Scaffold a new Use Case class following Clean Architecture with TDD in a Java + Spring Boot project. Use when the user says 'create use case', 'new service', 'new business operation', 'add X logic', 'implement Y feature'. Don't use for HTTP endpoints — use add-endpoint-spring. Don't use for frontend components — use create-component-mantine or create-component-mui.

Write a unit test for a Use Case or domain entity using JUnit 5 and AssertJ in a Java + Spring Boot project. Use when the user says 'write test', 'add tests', 'test this', 'TDD', 'cover X with tests'. Don't use for integration tests with Spring context — those require @SpringBootTest. Don't use for HTTP endpoint tests — test the use case directly.

Add a new FastAPI HTTP endpoint wired to a Use Case following Clean Architecture. Use when the user says 'add endpoint', 'create route', 'new API', 'expose X via HTTP', 'add a GET/POST/PUT/DELETE'. Don't use for business logic — use create-usecase-fastapi. Don't use for tests — use write-unit-test-pytest.

Scaffold a new Use Case class following Clean Architecture with TDD in a Python + FastAPI project. Use when the user says 'create use case', 'new service', 'new business operation', 'add X logic', 'implement Y feature'. Don't use for HTTP endpoints — use add-endpoint-fastapi. Don't use for frontend components — use create-component-mantine or create-component-mui.

Write a unit test for a Use Case or domain entity using pytest with fixtures and async support in a Python project. Use when the user says 'write test', 'add tests', 'test this', 'TDD', 'cover X with tests'. Don't use for integration tests with real databases. Don't use for API endpoint tests — test the use case directly.

Scaffold a new React component using Mantine UI primitives with typed props and a colocated test. Use when the user says 'create component', 'new card', 'new widget', 'add a UI element', 'build X component'. Don't use for full pages — use create-page-mantine. Don't use for data hooks — use frontend-hooks-react-query.

Scaffold a new page component using Mantine layout primitives, wired to the router and data hooks. Use when the user says 'create page', 'new screen', 'add a page for X', 'list page', 'detail page'. Don't use for small UI widgets — use create-component-mantine. Don't use for data hooks — use frontend-hooks-react-query.

Create a data-fetching hook using TanStack Query (React Query) for a backend endpoint with centralized query keys. Use when the user says 'create hook', 'fetch data', 'add query', 'add mutation', 'connect to API', 'wire up the endpoint'. Don't use for UI components — use create-component-mantine. Don't use for backend endpoints — use the backend stack's add-endpoint skill.

Scaffold a new React component using Material UI primitives with typed props and a colocated test. Use when the user says 'create component', 'new card', 'new widget', 'add a UI element', 'build X component'. Don't use for full pages — use create-page-mui. Don't use for data hooks — use frontend-hooks-react-query.

Scaffold a new page component using Material UI layout primitives, wired to the router and data hooks. Use when the user says 'create page', 'new screen', 'add a page for X', 'list page', 'detail page'. Don't use for small UI widgets — use create-component-mui. Don't use for data hooks — use frontend-hooks-react-query.

Add a new Express HTTP endpoint wired to a Use Case following Clean Architecture in a TypeScript + Node project. Use when the user says 'add endpoint', 'create route', 'new API', 'expose X via HTTP', 'add a GET/POST/PUT/DELETE'. Don't use for business logic — use create-usecase. Don't use for tests — use write-unit-test-jest.

Scaffold a new Use Case class following Clean Architecture with TDD in a TypeScript + Node project. Use when the user says 'create use case', 'new service', 'new business operation', 'add X logic', 'implement Y feature'. Don't use for HTTP endpoints — use add-endpoint-express. Don't use for frontend components.

Write a unit test for a Use Case or domain entity using Jest in a TypeScript + Node project. Use when the user says 'write test', 'add tests', 'test this', 'TDD', 'cover X with tests'. Don't use for integration tests with real databases. Don't use for API endpoint tests — test the use case directly.