A professional collection of Agent Skills for AI-powered Platonic Coding workflow.
Platonic Coding is a coding style designed for complex projects and cross-team collaboration with AI agents. Instead of relying on prompts, vibes, or implicit assumptions, it treats specifications as abstract laws that define what can exist, what can change, and what must always hold. Agents operate inside a shared, closed spec world where meaning is explicit, violations are detectable, and evolution is traceable over time, making large systems reproducible, reviewable, and stable across teams, agents, and long development cycles.
See a full description in Manifesto.
If using Claude Code CLI with marketplace support:
claude-code marketplace add caesar0301/platonic-codingnpx skills add caesar0301/platonic-coding- 📦 ClawHub:
clawhub install platonic-coding
Platonic Coding now includes structured design exploration as a built-in mode — no separate skill required. The former platonic-brainstorming skill has been merged into platonic-coding as BRAINSTORM mode.
- Phase 1 (RFC Specification): BRAINSTORM mode helps explore requirements, compare approaches, and validate design before RFC formalization
- Phase 2 (Implementation): BRAINSTORM mode helps refine architecture decisions and validate implementation approach against RFC constraints
It activates automatically when your request signals exploration (e.g., "brainstorm", "discuss", "investigate", "deep analysis"), or when you invoke it explicitly. After a design draft is approved, the skill presents alternative paths to continue: pause at each phase gate, quick-pass multiple phases for a fast fix, or update vs. create an RFC/IG.
All skills follow the Agent Skills specification for maximum compatibility across AI coding agents.
| Skill | Purpose | Docs |
|---|---|---|
| 🎯 platonic-coding | Intelligent orchestrator for the complete Platonic Coding workflow. Auto-detects intent and project state, then routes to the right next step: brainstorm a design, initialize a project, run recovery for existing code, formalize drafts into RFCs, refine specs, implement from guides with tests, or review code compliance. | SKILL.md |
Platonic Coding follows a three-phase workflow (after initialization) with intelligent auto-detection:
Init → Bootstrap infrastructure (new project or recovery flow for existing code)
Phase 1 → RFC Specification (optional BRAINSTORM mode → design draft → RFC → specs-refine)
Phase 2 → Implementation (optional BRAINSTORM mode → impl-full: guide + code + tests)
Phase 3 → Spec Compliance Review (verify code against RFCs and guides)
Each phase optionally enters BRAINSTORM mode for structured design exploration and validation.
The skill automatically detects your intent and project state, then suggests the next step:
- Request mentions brainstorm / discuss / investigate / explore / deep analysis? → Enter BRAINSTORM mode (design exploration first), then hand off to Phase 1 or 2
- No
.platonic.yml? → Initialize (init-scaffold) or start the recovery flow (init-scan→ recovery operations) - Has design drafts but no RFCs? → Run Phase 1 (RFC Specification)
- Has RFCs but no implementation guides? → Run Phase 2 (Implementation)
- Has RFCs and implementation guides? → Resume Phase 2 implementation or run Phase 3 review, depending on completeness
- State is ambiguous? → Resume the current phase or ask whether you want refine / implement / review
Prefer canonical operation names when overriding auto-detection: brainstorm, init-scaffold, init-scan, specs-refine, impl-full, review, workflow --phase <N>
Use platonic-coding to set up my new project "Acme" (TypeScript/Next.js).
Auto-detects missing infrastructure → scaffolds .platonic.yml, directories, templates.
Use platonic-coding to recover design specs for this codebase.
Auto-detects existing code → scans → proposes RFC dependency graph → generates Draft RFCs.
Use platonic-coding to brainstorm the message queue design.
Intent keyword detected → enters BRAINSTORM mode → collaborative dialogue → approved design draft → presents post-draft routing (pause / quick-pass / update or create RFC / update or create IG).
Use platonic-coding workflow to implement user preferences.
Phase 1: RFC Specification (optional BRAINSTORM mode for conceptual design → RFC → specs-refine) → Phase 2: Implementation (optional BRAINSTORM mode → impl-full) → Phase 3: Review.
Use platonic-coding impl-full for RFC-0001-user-authentication (Authentication).
Creates impl guide (with confirmation) → generates coding plan (with confirmation) → writes code + tests.
Use platonic-coding to review src/auth/ against RFC-0001-user-authentication.md.
Generates compliance report: implemented ✅, missing ❌, inconsistent
BRAINSTORM mode (the built-in design exploration capability, formerly the standalone platonic-brainstorming skill) is adapted from the upstream Superpowers skill collection by Will Barton. It enhances design exploration in Platonic Coding Phases 1 and 2 with structured requirements gathering, multiple approach comparison, and incremental validation at key decision points.
MIT License - see LICENSE file for details.
Xiaming Chen
- Website: https://xiaming.site/
- GitHub: @caesar0301
Built with ❤️ following the Agent Skills standard
