Individual skill

direction-picker

0upvotes

Resolves the visual direction at the plan stage from the brief and design system, without asking the user.

plugins/_official/atoms/direction-picker/SKILL.md

Read pinned source

Source commit e7a18df64d0e5e1161903e93bb5a302229dbeb96

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: Yes
Repository scan complete: No
Skill scan complete: No
Observed behavior: Network or broad shell
Last checked: Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings): 106,940
Repository last updated: Nov 10, 2026
License: Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

ai-design Repository topic
byok Repository topic
design-systems Repository topic
claude-design Repository topic
hermes-agent Repository topic
agent-skills Repository topic
desktop-app Repository topic
figma-alternative Repository topic
prototyping Repository topic
ui-generator Repository topic
design Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

SKILL.mdcore · 1,893 bytes
SKILL.mdcore · 1,893 bytes
open-design.jsonasset · 844 bytes

Read excerpt


# 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