This skill should be used when the user asks about "Orca architecture", "knowledge graph design", "MCP server structure", "nugget storage", "telemetry design", "Orca refactoring", or is planning changes to Orca components. Provides decision capture workflows, bounded exploration patterns, and architecture discussion guidance.
Provides Orca architecture guidance with decision capture workflows and bounded exploration patterns when discussing system design, refactoring, or component changes.
/plugin marketplace add dkoosis/cc-plugins/plugin install orca-arch@cc-pluginsThis skill inherits all available tools. When active, it can use any tool Claude has access to.
Load current Orca context from the knowledge graph:
search_nugs cue="boot" projects=["orca"]
This returns system state, recent decisions, active traps, and architecture patterns relevant to starting work on Orca.
For deeper exploration during the session:
search_nugs cue="pre-edit" file="<path>" - before modifying a filesearch_nugs cue="post-error" - after encountering failuressearch_nugs projects=["orca"] k="choice" query="<topic>" - specific decisionsDo not rely on hardcoded facts. The KG is the source of truth.
Ask why it exists this way
Search for decisions
orca:search_nugs with terms like "decision", "choice", "architecture"Surface your unknowns
Bound your investigation
Distinguish state from decisions
Multiple options with tradeoffs
Argue against yourself
Smallest validating step
project:orcaTaking 50+ steps exploring without progress. When you catch yourself:
Proposing to remove or change components without understanding their purpose. Always ask "why does this exist?" before proposing removal.
Creating nuggets that capture implementation details rather than reasoning leads to stale information that misleads future sessions.
/orca-arch <topic> - Start structured architecture discussionorca-explorer agent for bounded codebase explorationCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.