← ClaudeAtlas

util-projectinitlisted

Initialize a new CO2 project by analyzing a free-form prompt or markdown brief and generating the three foundational documents at the project root: `CLAUDE.md` (project detail, terminology, supporting 3rd party applications, custom applications, port allocation, system modules, business modules, rules), `DEVTOOL.md` (skeleton of development tools required by the inferred technology stack) and `ENVIRONMENT.md` (skeleton of local environment variables and credentials matching the 3rd party applications and external services declared in CLAUDE.md). Infers required infrastructure (databases, message queues, caches, SSO, file storage, SMTP, etc.), the number and names of custom applications, the adequacy of the standard system modules and the project-specific business modules from the input. This skill seeds the project — it is the first skill to run before any `modelgen-*`, `mockgen-*`, `specgen-*`, `testgen-*`, `util-projectsync` or `util-preparek8senv` invocation. Trigger on keywords: "init project", "initializ
rashidee/co2-skills · ★ 3 · Data & Documents · score 79
Install: claude install-skill rashidee/co2-skills
# Util Project Init Bootstrap a new CO2 project by transforming a free-form prompt or markdown brief into the three foundational documents at the project root: - `CLAUDE.md` — canonical project context: project detail, terminology, infrastructure, applications, port allocation, modules, rules. - `DEVTOOL.md` — skeleton of the local development tools the inferred technology stack will need (JDK, Maven, Node, PNPM, database/queue CLIs, kubectl, etc.). - `ENVIRONMENT.md` — skeleton of local environment variables and credentials for every supporting 3rd party application and external service declared in `CLAUDE.md`. This skill is the **first** skill in the CO2 workflow. Once these three files exist, downstream skills (`util-projectsync`, `util-preparek8senv`, `modelgen-*`, `mockgen-*`, `specgen-*`, `testgen-*`, `conductor-*`) can take over. ## Input Resolution This skill accepts a single optional argument: ``` /util-projectinit [prompt-or-markdown-path] ``` | Argument | Required | Example | Description | |----------|----------|---------|-------------| | `<input>` | No | `"A universal recruitment platform between countries"` or `./brief.md` | Free-form prompt OR path to a markdown file describing the project | ### Input Detection 1. If the argument is omitted or empty → ask the user: *"Provide a one-paragraph project brief, or the path to a markdown file describing the project."* Stop until the user responds. 2. If the argument **points to an existing file** with a