co2-skills

Compound Context (CO2) Workflow

https://compound-context.com

Logo	Description
	an OPINIONATED approach to software development using AI coding agents. It emphasizes the importance of comprehensive and structured context to reduce AI hallucination and AI slop:

Key Features

📝 User Story to drive UI and UX design + Non-Functional Requirement to drive business logic and technical design + Constraints to drive technical design and implementation.

🔄 Versioning to keep track of the changes and updates in the context as the project progresses.

📦 Multi application support where each application will have its own context. This is to support:

• Microservices architecture (multiple backend services with REST API or GraphQL API)
• Mobile application development (mobile frontend + REST API backend)
• Single Page Application development (web frontend + REST API backend)

🔗 Traceability from the generated code to the artifacts in the context to the User Stories, Non-Functional Requirements and Constraints.

🧠 Comprehensive context to reduce AI hallucination and AI slop, which includes:

• Data Models
• HTML Mockups
• Technical Specifications
• Test Specifications

Pre-requisites

• Claude Code (Preferably MAX plan)
• Claude Code Plugins
  • Playwright Test Generator Plugin (for generating Playwright test specifications and test scripts)
  • Ralph Loop Plugin (for orchestrating the development and bug fixing process)
• Node and npm version 18 or above (for serving the HTML mockups and running the Playwright test scripts)

Getting Started

• Plugin Name: Compound Context (CO2) Workflow (see below for details)

To install the plugin:

# Step 1: Add the marketplace
/plugin marketplace add rashidee/co2-skills

# Step 2: Install the plugin
/plugin install co2-skills@co2

Development Workflow

Context Window Preparation

This is the initial step where you want to ensure the AI coding agent has all the information needed to work.

💡 Bootstrapping a brand-new project? Use /util-projectinit "<one-paragraph brief>" or /util-projectinit <brief.md> to auto-generate skeleton CLAUDE.md, DEVTOOL.md and ENVIRONMENT.md from a free-form prompt or markdown brief. The skill infers 3rd-party infrastructure, custom applications, system/business modules and the local toolchain. It is non-destructive — it refuses to overwrite an existing CLAUDE.md.

CLAUDE.md

⚠️ Shared by the team - Checked in the repository

• Project detail
• Project goals
• Terminology (if any)
• Applications (1 or more)
• Modules (System Modules and Business Modules)

DEVTOOL.md

⚠️ Per developer - NOT CHECKED IN the repository

• Local development tools available to the AI coding agent (JDK, Maven, Node.js, kubectl, database CLIs, etc.)

ENVIRONMENT.md

⚠️ Per developer - NOT CHECKED IN the repository

• Per-environment configs and credentials for all 3rd party supporting applications
• Auto-generated/updated by util-preparek8senv skill

PRD Development

PRD.md is the main input for the development phase, which contains the User Stories, Non-Functional Requirements and Constraints. It is also the main reference for all the skills in this phase. The PRD.md should be updated and versioned as the project progresses.

Example of the PRD.md structure:

# Business Modules

## <Module 1>
### User Story
[v1.0.0]
- As a <type of user> I want to <perform some task> so that I can <achieve some goal>.
- As a <type of user> I want to <perform some task> so that I can <achieve some goal>.
### Non-Functional Requirement
[v1.0.0]
- <Non-Functional Requirement 1>
- ~~<Non-Functional Requirement 2>~~
[v1.0.1]
- <Updated Non-Functional Requirement 1>
- Removed <Non-Functional Requirement 2> since <reason for removal>
### Constraint
[v1.0.0]
- <Constraint 1>
- <Constraint 2>
### Reference
[v1.0.0]
- <Reference 1>

### <Module 2>
...

PRD Clean Up

Since PRD.md is based on human input, it may require some validation and each new points added need to be tagged with unique ID for traceability:

The skills to invoke the clean-up process are: