/coleoni-init

The project knows what it is before the first commit.

From the scope and the mockups, the skill writes everything a person or an agent needs to start right: what the project is and is not, the roadmap, the decisions still open, the real design tokens. It never picks the stack and never writes code.

npx skills add c0le0ni/skills --skill coleoni-init
View on GitHub
Claude Code, Codex and more 10 documents Decisions stay with the team One-page overview
The project overview in a browser and on a phone The project overview on three phones The overview page in a browser The overview on the project’s sage green The overview with the whole page beside it Sections of the overview on three phones
Example

From the scope to a project anyone can open.

The bakery from /coleoni-briefing continues here: its scope and brand notes become the docs of the project, and the docs become one page.

scope + brand notes
# Juniper Bakery: scope            (from /coleoni-briefing)

## 3. First release
Order page (customers, on the phone)
- Today's menu: name, photo, price, "available today"
- Cakes: flavor, size, message, pickup date (48h+)
- Checkout without an account, payment at pickup
Day board (counter, on a tablet)
- One list per day, grouped by pickup time
- States: new, ready, picked up
WhatsApp confirmation · One-page site

## 4. Out of scope (and why)
Card payments ......... Square
Photos and promotions . Instagram
Wholesale orders ...... Google Sheet
Loyalty ............... paper stamp card
Delivery, online payment, reviews ... roadmap

## 9. Open questions
1. Who owns juniperbakery.com
2. Menu photos (not received)
3. Product list with prices
4. Cake rules
5. WhatsApp sender number
6. Budget range

+ brand notes: cream #F6F0E6, sage #2F4A3A,
  terracotta #C8643B, Fraunces + Inter
10documents written
4decisions left to the team
6client blockers in one place
7tokens from the brand
How it works

Documentation first. Decisions with the team.

Whatever is heavy and hard to undo (framework, database, hosting, payments) becomes a decision record to fill in, never a choice made behind the scenes.

  1. Reads what was decided

    The scope, the mockups or brand, and whatever already exists in the repo, which it merges instead of overwriting.

  2. Picks the files

    Ten documents, each with a reason to exist. A privacy note only when there is personal data.

  3. Writes the agent guide

    AGENTS.md in eight fixed sections, read by Codex, Cursor and others; CLAUDE.md points to it.

  4. Takes the real tokens

    Colors, type, spacing and radius from the material the client approved. A guess is marked “to confirm”.

  5. Leaves decisions open

    Stack is always ADR-0001, marked “to record”. The skill lists the decisions; the team makes them.

  6. Shows it on one page

    The overview reads the docs and shows phases, palette, decisions and blockers, so the project fits on one screen.

The files

What every project gets.

Same names and the same structure in every project, so moving between them costs nothing.

FileWhat it holds
AGENTS.mdWhat it is, what it is not, stack (pending), identity, state, workflow, rules, index
CLAUDE.mdOne line pointing to AGENTS.md
README.mdWhat it is and how to run it, once the stack exists
docs/ROADMAP.mdPhases marked done, now or next; phase 1 is always the blocking decisions
docs/STATUS.mdClient blockers on top, then what shipped and how to test it
docs/design-system.mdColor tokens, type, spacing and rules, from the approved material
docs/glossary.mdThe client’s words, one line each
docs/adr/Index of decisions and the template to record them
docs/privacy.mdWhat personal data, why, where, who sees it and for how long
docs/overview.htmlThe one-page view of all of the above
Install

One command, any agent.

Nothing else to install. The overview page needs only Node.js, no packages and no browser.

AgentClaude Code, Codex, Cursor…
Node.js18 or newer, for the overview
A scopefrom /coleoni-briefing or your own
01Install
npx skills add c0le0ni/skills --skill coleoni-init
02Use it in your agent
/coleoni-init ./my-project --write --overview
For your whole user, not just the project-g
Claude Code only-a claude-code
Codex only-a codex
Every Coleoni skillnpx skills add c0le0ni/skills
Examples

Run it where the scope is.

Without flags it only shows the plan. Nothing is written until you ask.

See the plan first: files, decisions and blockers.

/coleoni-init

Write the docs and the overview page.

/coleoni-init ./bakery --write --overview

Use the mockups for the tokens.

/coleoni-init --write, tokens from mockups/home.png and mockups/board.png
Options

The overview, from the terminal.

Run scripts/overview.mjs again whenever the docs change; the page is always rebuilt from them.

OptionWhat it does
<project folder>Where the docs live
--accent "#hex"Accent color. Default: --accent from the design tokens
--out file.htmlOutput file. Default: docs/overview.html

The first commit already knows where it is going.

npx skills add c0le0ni/skills --skill coleoni-init