Evc

EVC

The agent workspace for marketing operators.

42 commands. 12 hooks. 3 modes. 4 starters. One setup.sh.

An opinionated marketing agent system for Claude Code. Clone it, configure it, run /project:monday to start your week.

Visual overview →

What this is

EVC is a folder. Inside it:

Every command is a markdown file. Every hook is a shell script. The workspace is just files — fork it, read it, change it.

Quick start

Setup takes 2 minutes:
1. Pick your industry (Web3, SaaS, E-commerce, Generic)
2. Fill in 5 required variables
3. Done — 42 commands installed, 12 hooks wired

Then open Claude Code in the directory:

Commands

Chains (the point of entry)

Content Engine (daily social)

Blog Engine (long-form)

QA & Review

Comms

Memory & Productivity

Setup

Staging & Pipelines

Pipelines

Content Engine (Mon→Fri)

Blog Engine (per article)

Human gates at every decision point. The system drafts, you approve.

The brand brain

brand/canon-rules.json is the single source of truth:

Every command reads it. The canon-guardrail hook blocks violations before they ship. The canon-changelog hook snapshots every edit to brand/canon-history/. Run /project:canon-diff to see what changed and when.

Hooks

12 shell scripts that fire on Claude Code events. You don't call them — they run automatically.

Configuration

Required (5 variables)

Industry starters

Pre-filled configs in starters/:
- web3.env — crypto compliance, community-first, Discord
- saas.env — LinkedIn-heavy, case studies, product-led
- ecommerce.env — product launches, seasonal cadence, conversion
- generic.env — baseline for anything else

See config.env.example for the full variable list including CMS IDs, Linear prefix, compliance jurisdictions, and credential paths.

Memory

EVC gets smarter the longer…