/arc:vision

The full arc from idea to shipped code.

A workflow toolkit for Claude Code, Codex, and 40+ agents with 9 skills and 26 specialized agents. Skills orchestrate workflows: exploring your codebase, asking clarifying questions, spawning agents for parallel review. Agents are specialists: security auditors, performance analysts, architecture reviewers, each with deep domain expertise.

Made by Daniel Howells

Install

$claude plugins install arc@howells

Full plugin: skills, agents, commands, references, and disciplines. Requires Claude Code 2.1.16+.

Update

$claude plugins update arc@howells

Claude Code auto-updates plugins, but you can trigger it manually. In Cursor, use this command — it doesn't auto-update.

Start here

/arc:ideate add team invitations

Start with the workflow you need. For a new feature, turn the idea into a concrete spec first.

Getting started

Open your project in Claude Code or Codex and run a command. Commands chain together: /arc:ideate creates a feature spec, then asks if you want to continue to /arc:implement. You can enter at any point — already have a feature spec? Start at /arc:implement.

#Design a feature
/arc:ideate add a notification system
#Audit current health
/arc:audit
#Launch / go live
/arc:launch

Why this exists

If you've spent time teaching Claude how you like to work (tests first, one question at a time, review as you go) Arc is that knowledge already written down. You get to skip the setup conversations and start building.

It's opinionated because good defaults save time. If something doesn't fit how you work, take what's useful and leave the rest.

Principles

  • Tests first. Not negotiable.
  • Review is continuous, not a gate at the end.
  • Ask one question at a time. Too many questions at once stalls progress.
  • The user decides. Agents advise, they don't dictate.
  • Frontend delivery included. Implement the experience, but defer independent visual direction to the project's design source of truth.
  • YAGNI where appropriate. Simplifications suggested, but you have final say.

How commands connect

  • /arc:ideate flows into /arc:implement — specify, then build with TDD.
  • /arc:implement scales between quick fixes and full plan-driven execution.
  • /arc:launch records whether /arc:testing and /arc:audit are done, missing, or intentionally deferred.
  • Arc workflows are invoked directly; the README carries the command catalog.

Optional integrations

Arc works standalone. These integrations unlock enhanced functionality when available.

IntegrationUsed by
Figma/arc:ideate, /arc:implement
Context7Research and implementation workflows
Claude in ChromeRendered verification during implementation
Linear MCP/arc:audit issue tracking
···

Skills are workflows and capabilities. Most are user-invokable via /arc:name—they orchestrate the development process: gathering context, asking questions, spawning agents, and guiding implementation.