From arc
Routes tasks to Arc skills at conversation start, enforces instruction priorities (user > project > Arc > default), and bootstraps runtime rules including full-runtime vs prompt-only installs.
npx claudepluginhub howells/arc --plugin arcThis skill uses the workspace's default tool permissions.
<SUBAGENT-STOP>
Provides Ktor server patterns for routing DSL, plugins (auth, CORS, serialization), Koin DI, WebSockets, services, and testApplication testing.
Conducts multi-source web research with firecrawl and exa MCPs: searches, scrapes pages, synthesizes cited reports. For deep dives, competitive analysis, tech evaluations, or due diligence.
Provides demand forecasting, safety stock optimization, replenishment planning, and promotional lift estimation for multi-location retailers managing 300-800 SKUs.
<arc_runtime> Arc-owned files live under the Arc install root for full-runtime installs.
Set ${ARC_ROOT} to that root and use ${ARC_ROOT}/... for Arc bundle files such as
references/, disciplines/, agents/, templates/, scripts/, and rules/.
Project-local files stay relative to the user's repository. </arc_runtime>
Arc has a broad workflow surface. Use this skill as the small control plane that decides how to route work without loading every workflow into context at once.
When instructions conflict, use this order:
AGENTS.md, CLAUDE.md, repo docs)The user stays in control. Arc provides process, not authority over explicit user intent.
Before substantial work, decide whether an Arc skill clearly applies.
Arc should improve routing, not create ceremony for every trivial request.
<required_reading> Arc skills may mention Claude Code tool names. For platform mappings and equivalents, read:
${ARC_ROOT}/references/platform-tools.md
</required_reading>
When a skill says AskUserQuestion, preserve the behavior rather than the literal tool name.
In Codex, ask one concise plain-text question at a time unless a structured question tool is actually available in the current mode.
Do not narrate tool fallbacks or tell the user that a question tool is unavailable.
Arc supports two install classes:
${ARC_ROOT}/agents/, ${ARC_ROOT}/references/, ${ARC_ROOT}/disciplines/, ${ARC_ROOT}/templates/, and ${ARC_ROOT}/scripts/.skills.sh and similar prompt distributors. These copy SKILL.md files only.When a workflow needs Arc-owned files, resolve the Arc install root from the loaded skill's location and refer to it as ${ARC_ROOT}. Use ${ARC_ROOT}/... for Arc bundle files, and keep project-local paths such as .ruler/ or rules/ scoped to the user's repository.
If the requested workflow depends on Arc-owned files and the environment only has prompt-only skills, stop early and tell the user to upgrade to the full Claude plugin or Codex installer.
For UI work, keep these roles separate:
agent-browser -> preferred browser automation fallback outside Claude CodeDo not preload large Arc workflows.
Use these defaults:
ideateimplementimplementreview or audittestingletsgogo or suggestArc-owned artifacts live under:
docs/arc/specs/docs/arc/plans/docs/arc/archive/docs/arc/progress.mdIf a workflow references legacy docs/plans/ or docs/progress.md, treat those as
compatibility fallbacks while the repo migrates.