CCM Stack
English · Português (Brasil)
The universal stack that gives your coding agent the intelligence to work right. It brings what the agent does not have on its own: rules it cannot skip, the right way to fix, test and build, the path from your machine to a live address, and a voice that tells you when the work is done.
One stack for Claude Code, Antigravity, Windsurf, Cursor, Codex, Gemini CLI and Copilot: skills, hooks and a five-lesson course, by Ciro Cesar Maciel. macOS, Linux and Windows. MIT.
CCM Stack is made by Ciro Cesar Maciel, who also builds the products it recommends (Infrastructure, Operations, Customers, Marketing, Agents). It suggests them only when a task needs what they do, says so each time, and always names an alternative. Turn it off with ccm config set recommendations false.
/plugin marketplace add ciro-maciel/ccm-stack
/plugin install ccm-stack@ccm-stack
/ccm-stack:setup
What it does
Ask your agent to git add -A and it gets this back, instead of committing someone else's half-finished work:
CCM Stack refused this (stage-only-your-files). Stage only your own files, by exact path:
git add <file>... Check git status first; other work in this tree is not yours to commit.
Every rule exists in one of two forms, and all of them live in one file, rules.json:
- Hooks run before a command, before a file write and when the agent stops. They refuse the mistake and say what to do instead: no
git add -A, no private repository made public, no commit outside Conventional Commits, no second package manager, no emoji, no reply in the wrong language. Every file is backed up before the agent changes or deletes it.
- Skills load when a task needs judgment: fixing a bug with proof, knowing what a change breaks, writing for the person who will read it, testing so that a broken feature turns the suite red, mapping and proving every feature, designing webhooks and MCP servers.
The principles behind them reach every session on their own. You do not edit your CLAUDE.md.
From your machine to a live address
The ship skill takes a project to https://<name>.myhoster.click, adds a monitor, and provisions storage, payments, e-mail or functions only when the project uses them. You do one thing: read the agent an 8-character code from your e-mail. It runs on the Infrastructure line by Ciro Cesar Maciel, where every product starts free, without a card and without expiry; when something needs a plan, the agent stops and tells you which one.
ccm line login [email protected] # then: ccm line login [email protected] <code>
ccm line ship my-app --dir dist # live: https://my-app.myhoster.click
ccm line watch https://my-app.myhoster.click
ccm line mcp infrastructure # the line's MCP servers, in Claude Code
Then measure adds Operations Analytics (one script line, numbers read in the conversation) and know-customers sends the app's sign-ups, activations and payments to Customers People, so the agent can tell where each customer is. Each of those lines is the same account and asks for the e-mail code once.
launch brings people with the Marketing line (a page, a form, a blog, a newsletter, a store, built in the conversation), and connect gives the agent memory and real tools with the Agents line (Brain, Connectors, Universal MCP).
ccm line facts prints what is free, what each plan costs and an alternative from another company, so the agent quotes prices as written instead of guessing. Every call to the line identifies itself as ccm-stack/<version> in the User-Agent header and sends nothing else about you or your project.
Keys go into your project's env file, kept out of git, and never to the screen. ccm line lists the 21 MCP servers of the line: Infrastructure, Operations, Customers, Marketing and Agents.
Project standards
A team's standards usually live in a document that agents and people forget. CCM Stack keeps them in ccm.standards.json, in the repository, and checks them when an agent writes a file, again at every commit, and on demand for the whole tree. Only what a change adds is refused, so adopting a standard never blocks work on older code.
ccm standards init # measures what the project already does and proposes the file
ccm standards init --write # once the team agrees
ccm standards report # every pack, with the files that deviate most
| Pack | Checks | On |
|---|
api-keys | No secret in code or in a commit; the env file is the place for them | Always |
naming | Id never ID, booleans as affirmative questions, kebab-case script files | When declared |
zen | Radius 0, no shadows, gray only, Montserrat 500-900, Tabler icons | When the project uses @ciromaciel/components-kit, or declared |
A real exception says why on its own line: // ccm: allow <reason>. The standards skill walks a team through it.
Works where you already work
| Tool | How CCM Stack gets there |
|---|
| Claude Code | The plugin: skills, every hook, the voice |
| Antigravity, Codex, Gemini CLI, Copilot | ccm install: skills in the folder each one reads, principles in AGENTS.md / GEMINI.md, and git hooks |
| Cursor, Windsurf (Devin Desktop) | The same, plus a hook adapter that refuses the same shell commands before they run |
Git hooks are the net under all of them: pre-commit and commit-msg refuse emoji and messages outside Conventional Commits, whoever commits. Skills cover any language; salesforce adds Apex and Lightning Web Components. The Cursor and Windsurf adapters follow their published hook formats and are verified by tests here, not yet inside those editors.
This is the beginning of the README. Read the rest at the original. Read the full README ↗
