Agent skill

Direction Picker

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

Apache-2.0Auto-check: warningsFrontend & Design

Install Direction Picker

The automated check flagged lines worth reading first. See the safety section below.

skills CLI

$ npx skills add nexu-io/open-design --skill direction-picker -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install nexu-io/open-design direction-picker --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/nexu-io/open-design.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/_official/atoms/direction-picker .claude/skills/direction-picker && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "direction-picker" agent skill from https://github.com/nexu-io/open-design/tree/main/plugins/_official/atoms/direction-picker into .claude/skills/direction-picker/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "direction-picker", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/nexu-io/open-design/tree/main/plugins/_official/atoms/direction-picker

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add nexu-io/open-design --skill direction-picker -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install nexu-io/open-design direction-picker --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/nexu-io/open-design.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/_official/atoms/direction-picker .agents/skills/direction-picker && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "direction-picker" agent skill from https://github.com/nexu-io/open-design/tree/main/plugins/_official/atoms/direction-picker into .agents/skills/direction-picker/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "direction-picker", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add nexu-io/open-design --skill direction-picker -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install nexu-io/open-design direction-picker --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/nexu-io/open-design.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/_official/atoms/direction-picker .cursor/skills/direction-picker && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "direction-picker" agent skill from https://github.com/nexu-io/open-design/tree/main/plugins/_official/atoms/direction-picker into .cursor/skills/direction-picker/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "direction-picker", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/nexu-io/open-design.git --path plugins/_official/atoms/direction-picker

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add nexu-io/open-design --skill direction-picker -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install nexu-io/open-design direction-picker --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/nexu-io/open-design.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/_official/atoms/direction-picker .gemini/skills/direction-picker && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "direction-picker" agent skill from https://github.com/nexu-io/open-design/tree/main/plugins/_official/atoms/direction-picker into .gemini/skills/direction-picker/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "direction-picker", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install nexu-io/open-design direction-picker

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add nexu-io/open-design --skill direction-picker -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/nexu-io/open-design.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/_official/atoms/direction-picker .github/skills/direction-picker && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "direction-picker" agent skill from https://github.com/nexu-io/open-design/tree/main/plugins/_official/atoms/direction-picker into .github/skills/direction-picker/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "direction-picker", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add nexu-io/open-design --skill direction-picker -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install nexu-io/open-design direction-picker --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/nexu-io/open-design.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/_official/atoms/direction-picker .opencode/skills/direction-picker && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "direction-picker" agent skill from https://github.com/nexu-io/open-design/tree/main/plugins/_official/atoms/direction-picker into .opencode/skills/direction-picker/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "direction-picker", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: direction-picker
GitHub stars: 100k
Token cost: ~472 tokens
SKILL.md length: 262 words
Files: 2
Skills in repo: 245
Repo updated: Oct 9, 2026
First seen: Oct 7, 2026
Licence: Apache-2.0

At a glance

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

Works in 3 steps: An active design system — its DESIGN.md… → A brand spec, reference URL, or… → Otherwise, infer the best-matching…
Tasks that involve Design systems
SKILL.md covers Convergence and Anti-patterns the prompt…
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Direction Picker is an agent skill from nexu-io/open-design. Resolves the visual direction at the plan stage from the brief and design system, without asking the user.

Its SKILL.md is about 470 tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `open-design.json`).

It sits in Frontend & Design, covering Design systems. The repository describes itself as: 🎨 Best DeepSeek Harness Design Plugin. The open-source Claude Design alternative. 🖥️ Local-first desktop app. 🖼️ Your coding agent becomes the design engine: prototypes… The licence is Apache-2.0.

When your agent uses it

Tasks that involve Design systems

Example prompts

“Use the direction-picker skill to resolve the visual direction at the plan stage from the brief and design system, without asking the user”
“/direction-picker”

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

An active design system — its DESIGN.md palette, typography, spacing, and
A brand spec, reference URL, or screenshot the user supplied — parse that
Otherwise, infer the best-matching direction yourself from the brief's

What it can do on your machine

Read from SKILL.md and the folder at commit d9dd6fe. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Direction Picker loads about 472 tokens when it runs. Until then it costs about 31 tokens; SKILL.md has 262 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~31
When it runs · the whole SKILL.md, loaded when a task matches: ~472

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: warnings

The automated check found patterns that need a careful read before installing.

WarningTells the agent its actions are pre-authorized / not to stop for confirmationSKILL.md:3
```
stage from the brief and design system, without asking the user.
```

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from nexu-io/open-design at commit d9dd6fe, republished under its Apache-2.0 licence (© nexu-io). 262 words, ~472 tokens.

Download SKILL.mdSave it as .claude/skills/direction-picker/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from 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
od.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:

An active design system — its DESIGN.md palette, typography, spacing, and component rules are the direction. Bind its tokens and stop here.
A brand spec, reference URL, or screenshot the user supplied — parse that source directly.
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.

Files

SKILL.md and 1 other file in plugins/_official/atoms/direction-picker of nexu-io/open-design.

SKILL.md
open-design.json

Open the folder on GitHubat commit d9dd6fe

Compare with similar skills

Direction Picker next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Direction Picker compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Direction Picker this skillnexu-io/open-design	100k	—	~472	Automated safety check: Warn	Apache-2.0	today
Impeccablebestofjs/bestofjs	3.1k	27 repos	~2.6k	Automated safety check: Pass	MIT	5 days ago
Figma Design System Builderwarpdotdev/warp	65k	2 repos	~4.4k	Automated safety check: Pass	AGPL-3.0	today
Figma use_figma Plugin API Ruleswarpdotdev/warp	65k	4 repos	~4.4k	Automated safety check: Pass	AGPL-3.0	today
UI StylingOhh-889/skyroc	795	13 repos	~2.5k	Automated safety check: Pass	MIT	1 mo ago
Shadcnsupabase/evals	143	42 repos	~4.5k	Automated safety check: Pass	Apache-2.0	today

Similar skills

Impeccable
bestofjs/bestofjs
A skill your agent uses when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a…
3.1k GitHub starsUsed in 27 repos~2.6k tokens
Frontend & DesignAuto-check passed
Figma Design System Builder
warpdotdev/warp
Builds or updates a design system in Figma from a codebase in ordered phases: discovery, variables and tokens, components, theming and documentation, with checkpoints.
65k GitHub starsUsed in 2 repos~4.4k tokens
Frontend & DesignAuto-check passed
Figma use_figma Plugin API Rules
warpdotdev/warp
Required groundwork before any use_figma call: the rules and reference files for running JavaScript in a Figma file through the Plugin API without common failures.
65k GitHub starsUsed in 4 repos~4.4k tokens
Frontend & DesignAuto-check passed
UI Styling
Ohh-889/skyroc
Create beautiful, accessible user interfaces with shadcn/ui components (built on Radix UI + Tailwind), Tailwind CSS utility-first styling, and canvas-based visual designs.
795 GitHub starsUsed in 13 repos~2.5k tokens
Frontend & DesignAuto-check passed
Shadcn
supabase/evals
Official
Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI.
143 GitHub starsUsed in 42 repos~4.5k tokens
Frontend & DesignAuto-check passed
Design System
Ohh-889/skyroc
Token architecture, component specifications, and slide generation.
795 GitHub starsUsed in 11 repos~1.7k tokens
Frontend & DesignAuto-check passed

More from nexu-io/open-design

All 245 skills in this repo

Humanize PPT
nexu-io/open-design
Turns raw notes into a talk-ready slide outline with per-page image, diagram or video decisions, then checks the rendered deck against that outline.
100k GitHub stars~4k tokensUpdated today
Auto-check passed
Last 30 Days Trend Research
nexu-io/open-design
Produces a cited Markdown briefing on recent community sentiment and social reaction to a topic, labeling every source it could not actually check.
100k GitHub stars~1.3k tokensUpdated today
Auto-check passed
OpenDesign Contribution Flow
nexu-io/open-design
Helps newcomers contribute to OpenDesign: ship a skill or design system, translate docs, fix docs or report a bug, ending in a pull request or issue.
100k GitHub stars~3.5k tokensUpdated today
Auto-check: notes
Chat Motion Overlay Generator
nexu-io/open-design
Turns a chat transcript or screenshot into a configurable animated chat clip, rendered as a Remotion bundle with optional transparency.
100k GitHub stars~1.1k tokensUpdated today
Auto-check passed
Flowai Live Dashboard Template
nexu-io/open-design
Team-management dashboard skill in the FlowAI aesthetic — three tabs (Team Members, Team Details, Activity Log), KPI stat row, member table, role distribution bar chart, online presence and activity…
100k GitHub stars~865 tokensUpdated today
Auto-check passed
Hatch Pet
nexu-io/open-design
Create, repair, validate, preview, and package Codex-compatible animated pet spritesheets from character art, screenshots, generated images, or visual references.
100k GitHub stars~6k tokensUpdated today
Auto-check passed

Questions about Direction Picker

What does Direction Picker do?

Resolves the visual direction at the plan stage from the brief and design system, without asking the user. Direction Picker is an agent skill from nexu-io/open-design. Resolves the visual direction at the plan stage from the brief and design system, without asking the user.

When should I use Direction Picker?

Direction Picker fits situations like: tasks that involve Design systems.

How do I install Direction Picker in Claude Code?

Run `npx skills add nexu-io/open-design --skill direction-picker -a claude-code`. Or copy the skill folder (plugins/_official/atoms/direction-picker in nexu-io/open-design) into .claude/skills/direction-picker in your project. Claude Code loads it when a task matches its description.

How do I install Direction Picker in Codex?

Run `npx skills add nexu-io/open-design --skill direction-picker -a codex`. Or copy the skill folder (plugins/_official/atoms/direction-picker in nexu-io/open-design) into .agents/skills/direction-picker in your project. Codex loads it when a task matches its description.

Can I use Direction Picker in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add nexu-io/open-design --skill direction-picker -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/direction-picker, .gemini/skills/direction-picker, .github/skills/direction-picker and .opencode/skills/direction-picker in your project.

What does Direction Picker need to run?

SKILL.md names no scripts, command-line tools or credentials: Direction Picker is instructions for the agent only.

Does Direction Picker access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Direction Picker safe to install?

Our automated static check of SKILL.md flagged 1 warning(s): tells the agent its actions are pre-authorized / not to stop for confirmation. Read the flagged lines before installing; the check is not a guarantee either way.

What licence does Direction Picker use?

Direction Picker is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Direction Picker use?

About 472 tokens (SKILL.md is roughly 1.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Direction Picker?

Skills that share tags, products or a category with Direction Picker: Impeccable (bestofjs/bestofjs, 3.1k stars), Figma Design System Builder (warpdotdev/warp, 65k stars), Figma use_figma Plugin API Rules (warpdotdev/warp, 65k stars) and UI Styling (Ohh-889/skyroc, 795 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Direction Picker?

nexu-io (a GitHub organization) maintains it in nexu-io/open-design, which has 100,100 GitHub stars. The repository holds 245 skills in this directory. The repository was last updated on October 9, 2026.

Source: nexu-io/open-design on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Direction Picker

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Direction picker

Convergence

Anti-patterns the prompt fragment forbids

Files

Compare with similar skills

Similar skills

More from nexu-io/open-design

Related

Questions about Direction Picker