Assistant Creative Agent (ACA)

A Claude Code agent-teams workspace that runs creative builds — web designs and decks — and reviews any work before it goes out. Part of the PARA desktop system.

                 ┌─────────────────────────┐
                 │  Lead session (planner) │
                 └───────────┬─────────────┘
                             │
                 ┌───────────▼─────────────┐
                 │    Shared task list     │
                 └───┬─────┬─────┬─────┬───┘
                     │     │     │     │
             ┌───────▼─┐ ┌─▼───────┐ ┌─▼────────┐ ┌─▼──────────┐
             │ Web UI/ │ │  Deck   │ │  Design  │ │    Copy    │
             │ UX      │ │ Designer│ │ Reviewer │ │ Proofreader│
             │ Designer│ │         │ │          │ │            │
             └─────────┘ └─────────┘ └──────────┘ └────────────┘
               production agents        review gates

The team

Agent	Role	When it runs
web-ui-ux-designer	Designs web interfaces, landing pages, app screens	Web/product builds
deck-designer	Pitch decks and any other slide decks — decks only	Deck builds
design-reviewer	Critically reviews design work before you sign off	After production, and on anything in inbox/
copy-proofreader	Catches errors, misspellings, and wrong details before work ships	After production, in parallel with design review

The lead session plays orchestrator/planner itself: it writes the brief, creates the task list, spawns only the roles the build needs, and finalizes once both reviewers pass.

Setup

1. Clone this repo and run claude inside it. The Agent Teams flag ships in .claude/settings.json, so desktop and Claude Code on the web sessions pick it up automatically — no claude.ai configuration needed.
2. Optional: connect Frame.io / Adobe / Figma MCP tools for asset search and design tooling. Without them, agents ask you to point at assets instead.

Kick off a build

Start a new creative build: a pitch deck for aimed at . Spawn the ACA team.

Claude copies projects/_template/ to a new project folder, captures the brief, spawns the team, and delivers to projects/<name>/final/ once design review and proofing both pass.

Review something sent to you

Drop the file in inbox/, then:

Review the file in inbox/ with the design-reviewer and copy-proofreader.

Both reviewers run in parallel and you get a synthesized verdict.

Folders

• projects/ — active builds, one folder per build (brief.md, working/, review/, final/)
• inbox/ — external work awaiting review
• resources/ — brand material and past documents the agents reference
• archives/ — finished projects

Limitations

Agent Teams is experimental: one team per session, no nested teams, /resume doesn't restore teammates, and task status can lag (nudge a teammate if a task looks stuck). Split-pane view needs tmux or iTerm2; otherwise teammates run in-process in the agent panel. If the feature is unavailable, the same pipeline runs on regular subagents — see CLAUDE.md.