writing-claude-design-prompts
Writing Claude Design Prompts
Principle
Commission visual judgement and implementation. Let surrounding engineering agents prepare technical truth and prove integration.
Route before writing
Use this skill if the primary deliverable is visual. Do not use it merely because Claude, Opus, or Fable will perform a non-visual engineering task. If available, use writing-gpt-5-6-prompts for GPT-5.6 engineering or research prompts.
Use the installed design skill, if available, to classify the surface and select route-specific design judgement. Import its classification and visual principles, not its validation or release contract. If visual and non-visual work have independently testable acceptance contracts, split them.
For a mixed programme, write separate missions:
- Preparation — a cheaper engineering agent establishes product truth, relevant files, working preview, screenshots, assets, and constraints.
- Visual production — the design model chooses the visual direction, implements it, renders it, inspects it, and iterates.
- Engineering closure — a cheaper engineering agent owns tests, CI, formal audits, backend/data integration, performance, deployment, and production proof.
“Production-ready” does not justify copying closure into visual production.