Help us improve
Share bugs, ideas, or general feedback.
From atlas
Turn a stated need into a full system design by mining the Atlas knowledge graph. Use this skill when asked to design a system from a goal, discover the components/processes/data a domain needs, mine processes or data models, or collect domain nuances. (atlas, design a system, what does X need, system discovery, process mining, data mining, collect nuances, blueprint from a need, graph-driven design)
npx claudepluginhub a5c-ai/atlas-claude --plugin atlasHow this skill is triggered — by the user, by Claude, or both
Slash command
/atlas:atlasThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
This skill turns a stated need into an entire system design by mining the Atlas
Creates p5.js generative art with seeded randomness, noise fields, and interactive parameter exploration. Use for algorithmic art, flow fields, or particle systems.
Share bugs, ideas, or general feedback.
This skill turns a stated need into an entire system design by mining the Atlas
knowledge graph. It is the brain of the atlas plugin. For non-trivial runs it
delegates orchestration to babysitter:babysit using an atlas-specific .a5c
process; for simple lookups it queries the graph directly.
Atlas is a knowledge graph of agents, processes, data models, capabilities,
workflows, clusters, and wiki pages. You reach it through the
mcp__atlas__atlas_public_* MCP tools, which this plugin wires natively into
your harness (see the plugin README "Atlas MCP" section; the server URL is
overridable via ATLAS_MCP_URL). Never assume the graph's shape — discover it
through the tools.
| Trigger phrase | Command |
|---|---|
| design a system, blueprint from a need, graph-driven design | /atlas:discover |
| process mining, what processes does X need | /atlas:mine-processes |
| data mining, what data does X need | /atlas:mine-data |
| collect nuances, edge cases/constraints for X | /atlas:collect-nuances |
AskUserQuestion). Per repo
policy, interview ONLY when requirements are genuinely unclear.atlas_public_search(q=<need terms>) to find seed nodes;
atlas_public_clusters / atlas_public_kinds to scope the domain.atlas_public_neighbors(id, depth, edges, kinds) from
the anchors to gather the system's parts: components, workflows, processes,
data models, capabilities.atlas_public_record(id, expandNeighbors) for fields and
edges; atlas_public_wiki_page for narrative context..a5c/atlas/<run>/design.md plus a machine mirror.For any non-trivial run, hand off to babysitter:babysit (via the Skill tool)
naming the matching atlas process:
/atlas:discover → atlas-systems-discovery/atlas:mine-processes → atlas-process-mining/atlas:mine-data → atlas-data-mining/atlas:collect-nuances → atlas-collect-nuancesDo not hand-roll orchestration when a process exists.
kind: 'shell' subtasks unless the user explicitly asks for a
shell-oriented workflow.