| name | sdl-author |
| description | Generate, repair, and validate SDL v1.1 YAML from requirements, architecture notes, repo summaries, or diagrams. Use for solution.sdl.yaml, modular .sdl.yaml files, fragments, and review items. |
SDL Author
Instructions
Use this skill to turn architecture intent into valid Solution Definition Language (SDL) v1.1. Favor small, schema-valid SDL over comprehensive-looking YAML that invents facts.
Claude Code can invoke this skill as /sdl-author or use it automatically when generating, repairing, or reviewing SDL.
Reference Loading
- If working in this
solution-definition-language repo, load reference/ai-authoring.md first. It is the compact machine reference.
- For deeper contract questions, load
spec/SDL-v1.1.md or reference/canonical-contract.md.
- If those repo files are unavailable, load
references/authoring-fast-path.md from this skill.
- For unclear input mapping, load
references/input-mapping.md.
Do not use stale README snippets, old .d.ts files, or legacy SDL examples as the source of truth.
Workflow
- Extract facts from the input.
- Identify product name, purpose, stage, architecture style, projects, database, auth, deployment, integrations, compliance, SLOs, and generated artifacts.
- Separate explicit facts from assumptions. Put uncertain details in review notes or
x-* metadata, not stable schema fields.
- Draft the minimum valid SDL first.
- Always include
sdlVersion, solution, architecture, and data.
- Add optional sections only when the input provides real facts or the user asks for a richer architecture baseline.
