SaigonXIII

Evc — Development skill for Claude Code

Development community

The open-source marketing agent workspace for Claude Code.

How to install Evc

This entry records only its repository, not the path inside it, so there is no exact command to give. Open SaigonXIII/evc and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Evc does

The open-source marketing agent workspace for Claude Code. 42 commands, 12 hooks, 4 industry starters.

Alternatives in Development

Knowledge Work Plugins — Open source repository of plugins primarily intended for knowledge workers to use in Claude Cowork 9734 125 18 10.5k ★
Llamacoder — Open source Claude Artifacts – built with Llama 3.1 405B 7.1k ★
Microsandbox — Open-source self-hosted MicroVM sandboxes with sub-200ms startup, hardware-level isolation via libkrun 5k ★

README

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](https://claude.ai/code). Clone it, configure it, run `/project:monday` to start your week.

[**Visual overview →**](https://saigonxiii.github.io/evc)

What this is

EVC is a folder. Inside it:

evc/
├── _templates/                 # Source of truth (tracked in git)
│   ├── commands/               # 42 command prompts with {{TOKENS}}
│   ├── hooks/                  # 12 shell scripts that fire on events
│   ├── contexts/               # 3 mode files (content/build/research)
│   ├── staging/                # Shared staging stylesheet
│   ├── SOUL.md                 # 7 operating principles
│   └── CLAUDE.md               # Top-level agent instructions
│
├── .claude/                    # Rendered output (gitignored)
│   ├── commands/               # Your 42 rendered commands
│   ├── hooks/                  # Your 12 rendered hooks
│   └── contexts/               # Your 3 rendered modes
│
├── brand/                      # Your brand brain
│   ├── canon-rules.json        # Banned phrases, USPs, required language
│   └── canon-history/          # Auto-maintained snapshots + CHANGELOG
│
├── content-engine/             # Working memory
│   ├── memory/                 # Lessons, learning log, visual log
│   ├── output/                 # Weekly posts, blog drafts, reports
│   └── calendar/               # Weekly briefs + reviews
│
├── staging/                    # Browser previews before publish
├── scripts/                    # Validation, secret scan, staging helpers
├── starters/                   # 4 industry configs (web3/saas/ecom/generic)
├── config.env.example          # Template — copy to config.env
└── setup.sh                    # One command to render everything

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