nexu-io/open-design / plugins/_official/atoms/direction-picker
direction-picker
VerifiedResolves the visual direction at the plan stage from the brief and design system, without asking the user.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 1.8 KB |
| open-design.json | config | 844 B |
SKILL.md
View on GitHub---
name: direction-picker
description: Resolves the visual direction at the plan stage from the brief and design system, without asking the user.
od:
scenario: general
mode: planning
---
# Direction picker
Converging work needs one committed visual direction before the build starts.
This atom owns that moment in the `plan` stage: decide the direction, state it
in one line, and lock onto it.
Resolve the direction from what you already have, in this order:
1. An active design system — its DESIGN.md palette, typography, spacing, and
component rules **are** the direction. Bind its tokens and stop here.
2. A brand spec, reference URL, or screenshot the user supplied — parse that
source directly.
3. Otherwise, infer the best-matching direction yourself from the brief's
domain, audience, and tone, then bind its visual tokens. If the runtime
provides only an index of direction ids and names, run
`"$OD_NODE_BIN" "$OD_BIN" tools directions --id <id>` to retrieve the full
specification — never infer colors or fonts from the name alone.
**Do not ask the user to choose a visual direction.** Not as a question-form,
not as a markdown list of options, not as a "which of these feels right?"
follow-up. The direction is yours to resolve; asking spends the user's turn on
a decision they hired the agent to make.
## Convergence
The atom completes when the plan states the chosen direction. The agent's next
turn must build against that direction — backtracking forces a fresh devloop
iteration of the plan stage.
## Anti-patterns the prompt fragment forbids
- Asking the user to pick, compare, or confirm a visual direction.
- Locking the user into a single direction with cosmetic alternates
(a stated direction must be a defensible standalone bet).
- Inferring palette or typography from a direction's name instead of
resolving its specification.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation). | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK). | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |