Community kit for apps built on Arc Network

Your AI build team for apps on Arc

One command gives Claude Code and Codex six specialists, Circle’s skills, Arc Studio and a guard that flags Arc mistakes while the code is being written.

curl -fsSL https://raw.githubusercontent.com/pedro-pelicioni/stable-build/main/install.sh | bash
the install command

One question, then everything is set up · testnet first · never touches your keys

Meet the team Read the code
A coding session with stable-build, from idea to go-live.
  1. Tim, what should I build on Arc?
  2. Tim 5 ranked ideas, each tied to the Request for Builders
  3. Bobbilee, write the PRD for idea 2
  4. Bobbilee docs/plan/prd.md, with an onchain section
  5. Sam, design the architecture
  6. Sam docs/plan/architecture.md, starting from Arc invariants
  7. Pedro, implement the next story
  8. Pedro writing src/history.ts
  9. guard Arc gotcha: a 0x3600-only filter misses native USDC sends
  10. Pedro switched to the system emitter, 18 decimals
  11. are we ready for mainnet?
  12. go-live 14 gates checked → docs/go-live-report.md
  • Works with
  • Claude Code
  • Codex
  • Brings in
  • Circle’s skills
  • Arc Studio
  • Arc docs MCP

01 The team

Meet your team

Six specialists who know Arc. Call one by name, or just say what you need.

  • Sam

    Architect

    Team lead

    Leads the plan. Starts from Arc invariants like decimals, the fee floor and finality, then checks the plan is ready to build.

    “Sam, design the architecture” /stable-build:architect

  • Bobbilee

    Product manager

    Writes the PRD with an onchain section: network plan, fees in USDC, EOA or smart account.

    “Bobbilee, write the PRD” /stable-build:pm

  • Tim

    Analyst

    Brainstorms and researches, then ranks ideas against the Request for Builders and open programs.

    “Tim, what should I build on Arc?” /stable-build:analyst

  • Joshua

    UX designer

    Specs screens with Arc states built in: one USDC balance, pending then final, a testnet banner.

    “Joshua, design the payout screens” /stable-build:ux-designer

  • Pedro

    Developer

    Builds each story test-first on Arc Foundry. Done means green tests and a testnet tx hash.

    “Pedro, implement the next story” /stable-build:dev

  • Mike

    Tech writer

    Docs, explainers and diagrams, with every Arc fact linked to docs.arc.io.

    “Mike, document this flow” /stable-build:tech-writer

  • Layered review: five independent passes, one of them an Arc gotcha hunter.
  • Arc Studio: hand off contract writing, audits and testnet deploys.

The names are a tribute to people from the Arc community, with the kit’s author as the developer. They did not build or endorse this kit, and the agents never speak for them or for Circle.

02 The journey

From idea to mainnet

Each step leaves a file in your repo that the next one reads, so nothing gets lost between chats.

  1. Idea

    5 ranked ideas from the Request for Builders, each with a first-2-hours plan.

  2. Plan

    Brief, PRD, UX, architecture and stories in docs/plan.

  3. Build

    Start from the payouts starter, then ship story by story, test-first.

  4. Review

    Five review layers, each finding verified before it reaches you.

  5. Go live

    14 gates before mainnet. It never deploys and never touches keys.

03 Arc-native

Built for how Arc actually works

Arc is EVM, with differences that break code written the Ethereum way. The kit knows them.

A guard that reads every edit

An opt-in check reads the lines the agent just wrote for 10 Arc mistakes, each tied to a docs page. Advisory: your edit is kept.

src/history.ts
import { arcTestnet } from "viem/chains"; const USDC = "0x3600000000000000000000000000000000000000";const transfer = parseAbiItem("event Transfer(address indexed from, address indexed to, uint256 value)"); const logs = await client.getLogs({  address: USDC,  event: transfer,  args: { to },  fromBlock,  toBlock,});

stable-build guard: 1 Arc gotcha in src/history.ts (transfer-filter-no-emitter) — advisory, edit kept

Native USDC sends log only from the system emitter, so this filter misses them. Why, on docs.arc.io

Payouts starter

CSV in, one Multicall3From batch with a Memo per row, reconciled ledger out. Testnet by default.

Straight from the source

Circle’s skills, Arc Studio (CLI, plugin and sign-in), Arc Foundry and the Arc docs MCP are installed alongside the kit, after one yes.

  • Circle’s skills
  • Arc Studio
  • Arc docs MCP
  • Circle codegen MCP

English and Português

The installer and the kit’s replies, in your language.

Safe to try

No keys, no transactions. --dry-run shows the plan; --uninstall removes only what it added.

Start building on Arc

Paste this in a terminal. Then open Claude Code or Codex and ask what to build.

curl -fsSL https://raw.githubusercontent.com/pedro-pelicioni/stable-build/main/install.sh | bash
the install command

Needs Node.js 20+ and Claude Code or Codex. Prefer /plugin, Codex or a dry run first? All install options