backend

To generate database schemas and API routes from a feature spec, you invoke the backend skill with the path to your spec file. It reads your design docs and project context to create tables, relationships, and CRUD endpoints automatically.

Yes, you can add authentication and validation logic to API endpoints during generation. The backend skill implements CRUD endpoints with built-in authentication, validation, and error handling based on your feature specifications and access-control standards.

To build backend logic, you need to provide a feature specification, technical design documents, and existing project context. The skill uses these inputs to generate secure, performant server-side code that aligns with your project's specific architecture.

Yes, the backend skill handles database migrations and row-level security policies. It creates database tables, manages relationships and indexes, and configures row-level security to ensure your backend meets strict access-control and performance standards.

The best way to connect newly built APIs to existing frontend components is using the backend skill after your frontend is ready. It integrates the generated server-side logic and endpoints directly with your frontend components.

Yes, this tool will update project documentation when new database patterns are created. It automatically records new patterns, learnings, and architectural decisions in your project documentation to maintain context and consistency.