What problem does it solve? Designing a database schema and API specification for a project requires synthesizing scattered requirements documents, screen specs, and design decisions into consistent, engine-agnostic technical documents. This Skill guides that process for the Projexa project, ensuring every conceptual design decision is explicitly confirmed by the user rather than guessed. ## Core Features & Use Cases - Conceptual Schema Design: Produces table definitions with conceptual data types, keys, relationships, and a mandatory Mermaid ER diagram, kept independent of any specific DBMS or ORM. - API Spec Generation: Defines resource-oriented endpoints with role-based permissions, including the mandatory two-step propose/confirm pattern for all AI-related endpoints. - Rigorous Interview Workflow: Asks structured questions with at least three options and pros/cons for every undocumented design decision, shows drafts for review before writing files, and delegates final file writing to a dedicated sub agent. - Use Case: Ask it to design the database schema and API spec for the MVP screens, and it will read the system design document, interview you on key strategies (ID strategy, audit scope, AI result storage), present an ER diagram and endpoint tables for confirmation, then write database-schema.md and api-spec.md. ## Quick Start Ask the assistant to create the conceptual database schema and API spec for the Projexa MVP screens using this skill.
