Route atelier work to an execution SOP, a creative heuristic, or a direct answer. Use when the needed kind of help is unclear; do not impose a suite-wide pipeline.
$npx -y skills add IamK77/Skill --skill pilot --agent claude-code
Installs into .claude/skills of the current project.
Are you the author of Pilot?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/iamk77-pilot)
---
name: pilot
description: "Route atelier work to an execution SOP, a creative heuristic, or a direct answer. Use when the needed kind of help is unclear; do not impose a suite-wide pipeline."
argument-hint: "<the design task, goal, or confusion — e.g. 'make this dashboard look premium' or 'the colors feel cheap'>"
metadata:
kind: router
---
<!--
Copyright 2026 IamK77 — Licensed under the Apache License, Version 2.0.
See ./LICENSE and ./NOTICE · https://www.apache.org/licenses/LICENSE-2.0
-->
# pilot
Route atelier work to an execution SOP, a creative heuristic, or a direct answer. Use when the needed kind of help is unclear; do not impose a suite-wide pipeline.
## Choose the kind of help
- A chosen outcome needing steps, artifacts, and verification: suggest the smallest relevant SOP.
- An open question, stuck framing, or desire for possibilities: suggest a heuristic. Explore rather than inspect every dimension.
- A small factual, syntax, or local implementation question: answer directly; no skill is a valid choice.
Ask a short clarifying question only if the distinction changes the work. A router is an auxiliary entrypoint, not a third substantive skill category. It starts no run and requires no CLI to offer directions.
## Map
| Skill | Kind | Use |
| --- | --- | --- |
| [canon](../canon/SKILL.md) | heuristic | Generate visual points of view and unexpected design languages from a product’s tensions and meaning. |
| [color](../color/SKILL.md) | heuristic | Explore palette ideas through perception, material associations, temperature, and semantic relationships. |
| [form](../form/SKILL.md) | heuristic | Explore shape, depth, light, texture, and material metaphors for an interface. |
| [graphics](../graphics/SKILL.md) | heuristic | Invent imagery, iconography, illustration, and generative visual languages. |
| [layout](../layout/SKILL.md) | heuristic | Invent spatial compositions through attention, rhythm, and alternative information metaphors. |
| [motion](../motion/SKILL.md) | heuristic | Explore motion as rhythm, continuity, character, and narrative. |
| [systems](../systems/SKILL.md) | sop | Turn a selected visual direction into versioned tokens, reusable components, and an inspectable handoff. |
| [type](../type/SKILL.md) | heuristic | Explore typographic voices, rhythm, and multilingual expression. |
## Handoff
Name the selected skill, why it fits, and the concrete input it needs. Suggest a chain only when a real artifact connects its steps. Heuristics have no completion gates and need not converge; begin an SOP only after its target is selected. Check runtime availability only when executing an SOP, not before creative exploration. Never silently install tools or reset an existing run.
The seven visual lenses are peers: begin with the interesting dimension, not necessarily `canon`. Only `systems` is an execution SOP. For ordinary CSS mechanics, answer directly; for a chosen end-to-end product journey, consider surface `keel`.
[Suite map](references/suite-map.md).