artifact-template-system-design

Invoke the Skill and provide your content covering architecture, components, data flows, and APIs. It reads artifact-template.json, loads the retained reference.docx, and generates a new document that preserves the template's layout and formatting.

The template supports documenting system architecture, requirements, components, data flows, APIs, tradeoffs, and operational considerations. The exact sections and styles come from the retained reference file rather than generic defaults.

Yes, the Skill preserves page setup, sections, styles, lists, tables, headers, footers, and recurring page elements from the reference file. User instructions control content and explicit deviations, while the reference controls layout where no change is requested.

No, the reference file must remain unchanged. The Skill clones or imports the reference to create a new document rather than replacing its visual system, so the original template stays intact for future use.

If the preinstalled document capability advertised in the prompt cannot be identified and read, the Skill reports it as unavailable and stops. It does not recreate or install the capability on its own.