Using Arc

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.

Instruction Priority

When instructions conflict, use this order:

User instructions in the conversation
Project instructions (AGENTS.md, CLAUDE.md, repo docs)
Arc skills
Default system behavior

The user stays in control. Arc provides process, not authority over explicit user intent.

The Rule

Before substantial work, decide whether an Arc skill clearly applies.

If the user names an Arc skill, use it.
If the task clearly matches an Arc workflow, use that skill before acting.
If the task is small, direct, or outside Arc's workflows, respond normally.

Arc should improve routing, not create ceremony for every trivial request.

Platform Adaptation

<required_reading> Arc skills may mention Claude Code tool names. For platform mappings and equivalents, read:

references/platform-tools.md </required_reading>

For UI work, keep these roles separate:

WireText -> low-fidelity wireframes and layout exploration
Chrome MCP -> preferred rendered-page verification in Claude Code
agent-browser -> preferred browser automation fallback outside Claude Code
Playwright -> scripted browser fallback when needed
Figma MCP -> implementation from real design files

Progressive Disclosure

Do not preload large Arc workflows.

Start with the smallest relevant skill
Load reference files only when the active task actually needs them
Prefer targeted rules and references over broad up-front reading

Workflow Routing

Use these defaults:

New feature or product thinking -> ideate
Plan execution -> implement
Small scoped change -> build
Architecture or quality review -> review or audit
Testing work -> testing
Production readiness -> letsgo
Unsure what to do -> go or suggest

Artifact Locations

Arc-owned artifacts live under:

docs/arc/specs/
docs/arc/plans/
docs/arc/archive/
docs/arc/progress.md

If a workflow references legacy docs/plans/ or docs/progress.md, treat those as compatibility fallbacks while the repo migrates.