cc-ecosystem

PRD generation rules and unified template enforced by a Python script. Single 14-section structure for Web, Backend, Mobile, and multi-platform projects.

ADR (Architecture Decision Record) generation + supersession rules. Immutable per-file under docs/adr/ (Status line is the only mutable surface). Bootstrap enumerates from PRD; standalone `/blueprint adr` adds or supersedes. Python-backed renderer.

Shared memory-management guidance for subagents. Preload via the subagent's skills frontmatter field so every agent follows the same rules about what to save, when to save, and when to retrieve.

Generate or update docs/ARCHITECTURE.md via a Python-backed, single unified template. Supports React Router Framework, Expo Router, NestJS, and Tauri 2 across single-package and monorepo layouts. The renderer enforces scope discipline — data model, features, code snippets, and tech-stack recommendations are rejected as PRD-territory.

Orchestrate creation/update of PRD, ADR, ARCHITECTURE, and ROADMAP via a guided 5-mode flow (Bootstrap / PRD / ADR / ARCHITECTURE / ROADMAP). Wraps the six doc subagents with phase-state enforcement so steps cannot be skipped. Use when the user invokes `/blueprint`, asks to "PRD/ROADMAP을 만들자", or wants to initialize/refresh project documentation.

Clean Architecture 4-layer dependency rules, TDD-exempt layer list, and test policy per layer. Reference-only skill preloaded by pipeline, tdd, code-reviewer, and other architecture-aware consumers.

Generate a production-ready GitHub Actions workflow that deploys a project to Cloudflare Workers via the official cloudflare/wrangler-action. Auto-detects the package manager (bun/pnpm/yarn/npm), reads the project's package.json scripts to assemble the right quality gates (lint/typecheck/test) and build step, parameterizes branches from .claude/config.json, and writes the rendered YAML to .github/workflows/deploy-cloudflare-workers.yml. Use whenever the user asks to "set up Cloudflare Workers deployment", "add a Cloudflare deploy workflow", "create a wrangler GitHub Action", "deploy this project to Workers from GitHub", or any phrasing about a CI/CD pipeline targeting Cloudflare Workers — even when they don't say the word "skill". Do not use this skill for Cloudflare Pages, Vercel, Netlify, or other platforms.

Generate a standalone .github/workflows/ci.yml that runs lint / typecheck / test / build on pull requests. Reads the project's package.json to assemble the right step set for the detected package manager (bun / pnpm / yarn / npm). Produces a self-contained workflow — no dependency on cc-ecosystem reusable workflows or composite actions. Triggers: "ci.yml 만들어줘", "GitHub Actions 셋업", "/ci-setup", "set up CI for this project". Do NOT use this skill for deploy/release workflows (cf-deploy, eas-deploy, etc. are separate target-specific skills).

Bridges design tokens from docs/design-system/ to the project's native theme format and enforces component styling rules. Loaded by ux-design-lead in BOOTSTRAP / APPLY / REVIEW / MODIFY modes.

Diagnose the full harness environment. Reports external tool versions, gh auth status, user-project file presence, `_harness_version` drift, and runtime gitignore state in a single screen. Non-blocking — emits the report only. Usage: /harness:doctor

Canonical rules for detecting the frontend/backend framework of a project (React Router, Next.js, Expo+RN, NestJS, Remix, Vite+React). Reference-only skill preloaded by other skills/subagents via the skills frontmatter field.

Git automation skill. Provides task selection UI when /git command is executed. Choose from commit, push, sync, issue, pr, revert operations. GitHub-only — there is no Local Mode; gh auth is a prerequisite.

Find deepening opportunities in the codebase. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled shallow modules, or make code more testable and AI-navigable.

Bootstrap harness user files by copying them from plugin templates into the user project. Seeds files such as `CLAUDE.md`, `.claude/config.json`, and `.claude/rules/*.md` on first install. The default mode is idempotent — existing files are skipped and reported. `--force` makes a `.bak` backup and overwrites; `--check-drift` is a dry-run diff only. Usage: /harness:init [--force] [--check-drift]

Discovery / Ambiguity-Resolution interview protocol for the harness pipeline and any sub-agent that performs requirements gathering, planning, or design decisions. Loaded at Phase 0 of pipeline and preloaded into 4 interview- enabled sub-agents (prd-generator, prd-validator, roadmap-generator, ux-design-lead) via their `skills:` frontmatter. `code-reviewer` is intentionally excluded — code-review findings carry clear single recommendations; multi-resolution cases that would warrant an interview are rare and better escalated to a separate ADR or to the user directly via the parent agent. Core mandate: **Do NOT proceed on inference.** Interview the user relentlessly about every aspect of their intent — until ambiguity is exhausted AND the user explicitly confirms coverage. The interview itself is owned by the main agent; sub-agents enumerate ambiguities and return them for the main agent to ask.

Canonical rules for detecting monorepo/workspace structure (Turborepo, pnpm workspaces, npm/yarn/bun workspaces) and locating the target app or package directory. Reference-only skill preloaded by other skills/subagents.

Unified development pipeline for all implementation tasks. Clean Architecture is the default — file placement follows CA layer templates. Auto-detects execution mode (Sequential or Team) based on task scope. Covers single-file fixes through cross-cutting multi-agent parallel work. Do NOT use for research, documentation-only, or planning-only tasks.

ROADMAP + tasks generation rules. Single template enforced by Python; one input JSON renders ROADMAP.md and every docs/roadmap/tasks/T###-*.md.

TDD (Test-Driven Development) rules and patterns. Use when: (1) Writing unit tests, (2) Determining test targets, (3) Following TDD cycle. Supports Expo, React Native, React Router, NestJS using Vitest/Jest, and Tauri 2 / Rust using cargo test + mockall + tauri::test::MockRuntime + rstest.

Sync user-project files with the plugin templates after an update. Uses a baseline-hash mechanism to detect user edits: unmodified files are auto-applied, modified files are skipped with a diff notice (preserved). The `_harness_version` marker is bumped after a successful sync. Usage: /harness:update [--dry-run]