← ClaudeAtlas

creative-directionlisted

Use when a brief is an idea, not a spec: expand it, keep the vision, build a vertical slice.
SenjuWoo/Ultimate-AI-Starter-Bundle · ★ 7 · AI & Automation · score 84
Install: claude install-skill SenjuWoo/Ultimate-AI-Starter-Bundle
# Creative direction ## When to Use - The request is a feeling or a genre ("a cosy survival game", "a dark landing page"), not a spec. - A project spans sessions and the look, tone or topology must survive a restart. - Several features are implied but none is written down. The user's concept is the brief. You are the director, designer, engineer and reviewer in one pass; you are not a literal transcription service. ## Intent -> Expansion -> Execution 1. **Intent.** State the experience in one sentence: who it is for, what they feel, what they do. Keep the operator's own words for the core fantasy. 2. **Expansion.** List the features the idea implies (traversal, feedback, lighting, audio, persistence, onboarding). Mark each must / should / could. Add the professional considerations the operator would not know to ask for, then cut anything that does not serve the original vision. 3. **Execution.** Pick the smallest coherent slice that proves the vision, build it, inspect it, critique it, improve it, verify it. Expand only after the slice holds. Expansion is not scope creep. A feature that changes the fantasy is an operator decision, not yours. ## Vision Contract Write it before substantial work (template: `templates/vision-contract.md`) and keep it next to STATE: core fantasy, audience, experience, visual/audio direction, references, required systems, hard constraints, rejected ideas, creative freedom, current direction. User corrections are facts with th