Source profileQuality 65/100
nexu-io/open-design/plugins/_official/atoms/direction-picker/SKILL.md
direction-picker
Optional 3-5 direction picker for users who explicitly ask to compare visual directions.
- Source repository stars
- 91,167
- Declared platforms
- 0
- Static risk flags
- 0
- Last source update
- 2026-08-25
- Source checked
- 2026-08-25
Decision brief
What it does: where it fits
Generative work benefits from explicit divergence before it converges. This atom defines how to present 3–5 distinct visual / structural / tonal directions when the user explicitly asks to see or compare direction options. Only in that case, emit one inline with a direction-card…
Not for
- More than 5 directions on one turn (decision fatigue).
- Two directions that are minor variations of each other.
Compatibility matrix
Platform support, with evidence labels
| Platform | Status | Evidence | What to check |
|---|---|---|---|
| Codex | Not declared | No explicit evidence | Portability before use |
| Claude Code | Not declared | No explicit evidence | Portability before use |
| Cursor | Not declared | No explicit evidence | Portability before use |
| Gemini CLI | Not declared | No explicit evidence | Portability before use |
Installation
Inspect first. Install second.
The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.
Source-detected install commandSource
npx skills add https://github.com/nexu-io/open-design --skill "plugins/_official/atoms/direction-picker"Safe inspection promptEditorial
Inspect the Agent Skill "direction-picker" from https://github.com/nexu-io/open-design/blob/edfa6b5f447e95cb120eae030f03baba00dc34de/plugins/_official/atoms/direction-picker/SKILL.md at commit edfa6b5f447e95cb120eae030f03baba00dc34de. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.
Workflow
What the source asks the agent to do
- 01
Convergence
When a picker was explicitly requested, the atom completes when the submitted form answer contains a direction id. The agent's next turn must lock onto that direction — backtracking forces a fresh devloop iteration of the picker stage.
When a picker was explicitly requested, the atom completes when the submitted form answer contains a direction id. The agent's next turn must lock onto that direction — backtracking forces a fresh devloop iteration of t… - 02
Anti-patterns the prompt fragment forbids
More than 5 directions on one turn (decision fatigue).
More than 5 directions on one turn (decision fatigue).Two directions that are minor variations of each other.Locking the user into a single direction with cosmetic alternates
Permission review
Static risk signals and limitations
No configured static risk pattern was detected
This is not proof of safety. Runtime behavior, indirect dependencies, and hidden external systems are outside the static scan.
Evidence record
Why each signal appears
EvidenceSourceComputedTestedEditorial
| Signal | Value | Evidence type | Meaning |
|---|---|---|---|
| Quality score | 65/100 | Computed | Documentation, specificity, maintenance, and trust rules |
| Repository stars | 91,167 | Source | Repository attention, not individual Skill quality |
| Compatibility | 0 platforms | Source | Declared in the catalog source record |
| Usage guide | automated source guide | Editorial | Generated or reviewed according to the visible evidence level |
Pinned source
Provenance and original SKILL.md
- Repository
- nexu-io/open-design
- Skill path
- plugins/_official/atoms/direction-picker/SKILL.md
- Commit
- edfa6b5f447e95cb120eae030f03baba00dc34de
- License
- Apache-2.0
- Collected
- 2026-08-25
- Default branch
- main
View the original SKILL.md
Direction picker
Generative work benefits from explicit divergence before it converges.
This atom defines how to present 3–5 distinct visual / structural / tonal
directions when the user explicitly asks to see or compare direction options.
Only in that case, emit one inline <question-form> with a direction-cards
question. The submitted choice returns as the next user message.
The presence of this atom or the plan stage does not trigger a picker. Do not
emit direction cards proactively. When the user has not explicitly requested
options, infer a fitting direction from the brief, active design system, and
known context, then continue.
Convergence
When a picker was explicitly requested, the atom completes when the submitted form answer contains a direction id. The agent's next turn must lock onto that direction — backtracking forces a fresh devloop iteration of the picker stage.
Anti-patterns the prompt fragment forbids
- More than 5 directions on one turn (decision fatigue).
- Two directions that are minor variations of each other.
- Locking the user into a single direction with cosmetic alternates (every direction must be a defensible standalone bet).
Frequently asked questions
What to verify before installation and use
What does the direction-picker source document cover?
Generative work benefits from explicit divergence before it converges. This atom defines how to present 3–5 distinct visual / structural / tonal directions when the user explicitly asks to see or compare direction options. Only in that case, emit one inline with a direction-card…
How do I install direction-picker?
The source record exposes this install command: npx skills add https://github.com/nexu-io/open-design --skill "plugins/_official/atoms/direction-picker". Inspect the command and pinned source before running it.
Alternatives
Compare before choosing
Computed 10045,511
coreyhaines31/marketingskills
ab-testing
When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program
Computed 10045,511
coreyhaines31/marketingskills
churn-prevention
When the user wants to reduce churn, build cancellation flows, set up save offers, recover failed payments, or implement retention strategies. Also use when the user mentions 'churn,' 'cancel flow,' 'offboarding,' 'save offer,' 'dunning,' 'failed payment recovery,' 'win-back,' 'retention,' 'exit survey,' 'pause subscription,' 'involuntary churn,' 'people keep canceling,' 'churn rate is too high,' 'how do I keep users,' or 'customers are leaving.' Use this whenever someone is losing subscribers o
Computed 10014,671
prowler-cloud/prowler
postgresql-indexing
PostgreSQL indexing best practices for Prowler: index design, partial indexes, partitioned table indexing, EXPLAIN ANALYZE validation, concurrent operations, monitoring, and maintenance. Trigger: When creating or modifying PostgreSQL indexes, analyzing query performance with EXPLAIN, debugging slow queries, reviewing index usage statistics, reindexing, dropping indexes, or working with partitioned table indexes. Also trigger when discussing index strategies, partial indexes, or index maintenance
Computed 100147
oaustegard/claude-skills
featuring
Generate hierarchical _FEATURES.md files that describe what a codebase DOES from a user/consumer perspective, anchored to source symbols via tree-sitting. Supports large complex codebases through feature-driven decomposition into sub-feature files. Uses a multi-pass synthesis: orientation → detail → overview rewrite. Use when someone says "what does this do", "document features", "feature inventory", "_FEATURES.md", or needs to understand a codebase's purpose before modifying it. Complements tre