Stats
Actions
Tags
From praxis
Explains how Praxis works, what skills are available, and how to use them. Usage: /help Also use when: "how does this work", "what commands do I have", "what is Praxis", "how do I start", "what is a wave", "what is a CR".
How this skill is triggered — by the user, by Claude, or both
Slash command
/praxis:help (optional: topic or question)(optional: topic or question)The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Show the guide below. If `$ARGUMENTS` contains a specific question or topic, answer it
Show the guide below. If $ARGUMENTS contains a specific question or topic, answer it
directly and concisely instead of showing the full guide.
Praxis is a two-command system that helps you build features faster and with less chaos. Instead of jumping straight into code, you plan first — then build wave by wave.
Works with Claude Code, OpenCode, and Antigravity.
/plan describe what you want to buildTell Praxis what you want. It scans your codebase, asks at most 3 questions, then produces a wave-structured implementation plan saved to a file.
Plain description:
/plan I want to add Google login
/plan Fix the bug where users can see each other's data
Architect brief (MD file):
/plan briefs/google-login.md
Stitch screen (folder with code.html + DESIGN.md + screenshot):
/plan convert stitch/chat-screen to a Next.js page
What it creates: specs/cr/<id>.md — your plan file with waves, units, and scope.
/build <cr-id>Takes the plan file and implements it wave by wave. Runs tests after each wave. Updates the plan file when done.
/build 260315-142300
The CR-ID comes from the /plan output — it's the timestamp ID printed at the end.
A wave is a group of implementation units that can be built independently — no unit in a wave depends on another unit in the same wave.
Wave 1: Tailwind tokens, font setup ← independent, no waiting
Wave 2: Layout component ← needs Wave 1 first
Wave 3: Interactive input wiring ← needs Wave 2 first
/build works through waves in order. Within each wave it implements all units before
moving to the next. If a unit fails, it skips units that depend on it and continues
with the rest.
specs/cr/
260315-142300.md ← one file per feature (plan + build log)
BACKLOG.md ← running list of all features and their status
code.html, DESIGN.md, and a screenshotstitch/<screen-name>/ in your project/plan convert stitch/<screen-name> to a Next.js page/build <cr-id>Praxis reads all three files: DESIGN.md for the design system (colors, fonts, rules),
code.html for structure and tokens, and knows the screenshot is the visual target.
It produces waves: tokens → TSX components → interactivity wiring.
/plan produces a plan that's off, edit specs/cr/<id>.md directly before running /build./build hits something unexpected mid-wave, it asks you what to do — pick A, B, or C and it continues.specs/cr/BACKLOG.md to see all features and their status at a glance.Creates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.
npx claudepluginhub angel1104/praxis-core --plugin praxis