itssungho17/ssdam Skills

First execution skill in the SSDAM pipeline. Produces a full architecture design document (Mermaid diagrams + markdown) from a task-spec. Its output is the required input for all other execution skills.

Backend-specialised design skill in the SSDAM pipeline. Reads architecture-design (and optionally schema-design) to produce a DDD-structured backend specification per domain. Mandatory components per domain are domain/entity, domain/facade, api/controller, and service/store. All other sub-layers (vo, event, exception, shared, request, response, mapper, proxy, config, application service) are optional and included only when needed.

Final backend step in the SSDAM execution chain. Reads backend-design and directly implements the backend code (FastAPI routes, services, repositories, migrations, tests) in the project root. This skill is for Cursor AI agent autonomous execution.

Second step in the SSDAM data chain. Reads architecture-design output and produces a detailed ERD with Mermaid erDiagram. Its output is the required input for schema-design.

Frontend-specialised design skill. Reads architecture-design (required) and backend-design (optional) to produce a complete frontend specification: pages, component tree, state management, API integration, and routing. Its output drives frontend-implementation.

Final frontend step in the SSDAM execution chain. Reads frontend-design and directly implements frontend code (Svelte components, stores, API client, routes, tests) in the project root. This skill is for Cursor AI agent autonomous execution.

Entry point of the SSDAM pipeline. Transforms a user's raw idea into a fully structured `mission-spec.yaml`. Its output is the direct input for the `new-task` skill.

Second skill in the SSDAM pipeline. Transforms one task entry from `mission-spec.yaml` into a fully specified `task-spec.TSK-NNN.yaml` that includes the task's contracts, evaluation criteria, and execution plan.

Third step in the SSDAM data chain. Reads data-modeling output and produces DDL SQL (CREATE TABLE, INDEX, constraints). Its output is consumed by backend-design as the authoritative schema reference.