design-direction
Explore or refine a product's visual direction and carry approved design decisions into specs and implementation without repeating the source article or prior conversation.
- License 许可
- MIT
- 最近更新
- 2026-11-14
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- design-direction
- description
- Explore or refine a product's visual direction and carry approved design decisions into specs and implementation without repeating the source article or prior conversation.
02 资源文件 3
- 参考文档references/brief.md2.0 KB
- 参考文档references/handoff.md1.7 KB
- 参考文档references/sources.md1.8 KB
03 SKILL.md 正文
Design direction
Carry the method here; keep each product's choices in its own brief. The user need not supply an article, remember skill names, or retell earlier decisions. For provenance or extending the method, read sources.md. Ordinary use is self-contained and needs no web lookup.
Recover the current decision
Read the supplied brief/spec first. Otherwise follow the project's design-context pointer, or search its planning/spec directories for the affected surface. Load Impeccable context once at the actual app; a missing discovered surface brief does not mean no brief exists. Preserve the incumbent identity unless replacement is requested. Use brief.md when recording or handing off choices.
Continue from the supported phase: unresolved direction, refinement of a selected direction, or implementation of an approved one. Current user corrections replace older assumptions. Update the existing brief/spec and mark obsolete boards as superseded; keep one clear current decision. Ask only about unresolved choices that materially change the result. Group a visual grill's questions by topic and reuse answers already given. For an approved direction or explicit continuation, the user's existing decision satisfies downstream confirmation prompts, including Impeccable's exploration probe. Resume the selected phase; request input only for a genuinely unresolved choice. Small styling fixes stay in Impeccable's refinement workflow without a new direction exercise.
Explore, then commit
For unresolved direction, produce several concise, structurally different ideas before rendering selected candidates. Three comparable directions are a useful starting point, not a quota. Describe the intended feeling, task hierarchy, density, composition and visual references; palette changes alone are not distinct directions. Keep factual content, capabilities and comparison states fixed.
Use Impeccable's matching playbook and the project's comp/code preference. Image generation can express composition or supply assets when their medium matters. Use an executable prototype for a question about interaction or motion. A generated still cannot prove precise tokens, breakpoint behavior or a working transition.
Refine the user's chosen direction rather than reopening alternatives. Preserve its distinguishing choices while removing ornamental containers, redundant copy and effects that compete with the task. If proposals converge on one generic pattern, try a contrasting reference or an optional externally generated seed for creative inspiration; product truth and approved constraints remain fixed.
Make the direction transferable
Compare the same representative tasks and states across the required device classes. Decide how hierarchy, density and context adapt, including constrained and wide layouts when relevant. Record tokens from the product, explicit open/closed behavior, and preservation of navigation, focus and task state. Use the brief's reference-status field to distinguish exploratory images, approved composition and verified implementation.
design-quality owns independent Astra critique and evidence-capture owns the
final walkthrough. Reuse that review: give the critic the selected intent,
references and current working images, without implementation rationalizations.
Resolve specific gaps in a batch and confirm affected states; a taste score is
not a retry trigger. Capture final evidence after the reviewed candidate is ready.
At handoff, use handoff.md to put the current decision, viewable approved images and slice-specific acceptance in the spec, tickets and worker packet. Reuse the project's design-context pointer. Check the actual attachments before diagnosing missing images; a path mentioned in a document does not establish whether a separate upload exists. A copied skill does not itself prove automatic discovery or behavior.
Done means the next model can identify the selected direction, what it may change, which references govern and how the requested slice will be accepted. Continue to specs, tickets or implementation when already authorized, without another ceremony.
04 同仓库更多 Skills
working-backwards
Define a software feature through PRFAQ and staged documents when the user requests working backwards before coding.
flow-implement
Implement a requested software change through verification, corrections, and its authorized delivery endpoint.
development-steward
Run the scheduled, read-only weekly maintenance review for the six explicitly opted-in repositories and prepare one concise private report for Check-in.
grill-with-docs
Run one recoverable interview for functional, visual, or mixed software grills; reuse equivalent answers and offer the shared HTML questionnaire.
global-agent-guardrails
Install, audit, test, or update the Development System's global destructive-command guard for Codex, Claude Code and T3 Code. Use when configuring agent safety hooks or investigating whether dangerous shell operations are blocked.
impeccable
Design or refine frontend UI using project context and a focused design playbook; also handles visual critique and polish.