From praxis
Designs software features collaboratively through visual scenarios and iterative refinement. Use when designing features, workflows, or any system before implementation.
How this skill is triggered — by the user, by Claude, or both
Slash command
/praxis:collaborative-designThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
icon: 🎨
icon: 🎨
Stay in design mode. Resist jumping to implementation. Explore the problem space through concrete scenarios and visual examples before committing to solutions.
Show it visually. Before/after states, input/output pairs, workflow diagrams. Visual beats prose.
Problem → Research → Timeline → Scenarios → Decisions → Validation
↑__________________________________________________|
(iterate freely)
Before slicing, check if the work is actually multiple things bundled together.
Red flags — words that signal a story is too big:
Splitting heuristics:
When a feature needs to be broken into deliverable pieces:
Force radical slicing by asking: "If you had to ship by tomorrow, what would you build?"
Distinguish learning steps (time-boxed research to reduce uncertainty) from earning steps (deliver working software). Learning before earning.
Example — "User uploads a document and receives a summary by email":
| Layer | Manual | Scripted | Automated | Scalable |
|---|---|---|---|---|
| Receive document | Copy file to folder | Web form | Form with validation | Upload with resume support |
| Extract content | Read plain text | Parse PDF with library | Multi-format extraction | OCR for scanned docs |
| Generate summary | Write it yourself | Hardcoded prompt to LLM | Tuned prompt with chunking | Fine-tuned model |
| Deliver result | Send email manually | Script sends email | SMTP service with template | Multi-channel with tracking |
Smallest slice: all manual except "hardcoded prompt to LLM" — ship in hours.
Then iterate: add a web form, support PDF, improve the prompt, add email templates.
Then: implementation.
npx claudepluginhub acunap/praxis --plugin praxisGuides collaborative dialogue to turn ideas into validated feature specs with built-in expert review. Useful when designing features, planning approaches, or shaping work before coding.
Generates user stories via 3 C's and INVEST criteria with titles, descriptions, design links, and acceptance criteria. For feature breakdown into sprint-sized backlog items.
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.