design-artifact

# Design Artifact Give each HTML artifact a visual identity that belongs to its brief. This skill can work alone for broad visual deliverables or alongside `html`, `html-wireframe`, `html-prototype`, `html-plan`, or `html-diagram`. It is creative-direction guidance, not a template. Do not reproduce a house palette, type stack, card system, layout, or static reference from a previous artifact. ## Compose it with the artifact skill Let the artifact skill own the form: - `html` chooses the broad workflow and shared build contract. - `html-wireframe` keeps the result intentionally low fidelity. - `html-prototype` decides whether the artifact is a mockup or working flow. - `html-plan` preserves source commitments and traceability. - `html-diagram` chooses the visual model and rendering method. - `design-artifact` shapes palette, type, composition, visual register, and the amount of expressive treatment. Creative direction must not smuggle polish into a wireframe, decoration into a plan, or spectacle into a diagram whose relationships need to remain quiet and legible. ## Establish authority before taste Inspect the request, supplied references, and current project before choosing a direction. Look for `AGENTS.md`, `CLAUDE.md`, `DESIGN.md`, product documentation, tokens, components, screenshots, and nearby artifacts. Authority runs in this order: 1. The user's explicit instructions and accepted decisions. 2. The project's established design system and conventions. 3. The...