| name | artifact-template-system-design |
| description | Create a document using the System Design template and its retained reference file. Use when the user selects or names System Design. Document system architecture, requirements, components, data flows, APIs, tradeoffs, and operational considerations. |
System Design
Create a new document from this template. Keep the reference file unchanged.
Workflow
- Read
artifact-template.json and resolve its paths relative to this skill directory.
- Identify the prompt-advertised preinstalled document capability. Use the available resource or filesystem tool to open its advertised resource, plugin, skill, or file target, then follow its reference/template workflow with the retained file. If no such capability can be identified and read, say it is unavailable and stop; do not recreate or install it.
- Treat the user's prompt and available sources as the content input. Do not invent facts merely to fill a template slot.
- Clone or import the reference instead of replacing its visual system with generic defaults.
- Render and verify the finished document, then return the final artifact.
Fidelity
Preserve page setup, sections, styles, lists, tables, headers, footers, and recurring page elements.
User instructions control requested content and explicit deviations. The retained reference controls layout and formatting where the user has not requested a change.
