Identify complexity and structure improvement opportunities across project docs and code.
npx skills add https://github.com/mdproctor/cc-praxis --skill project-refine
Please help me install this Agent Skill. Skill: project-refine Source: https://github.com/mdproctor/cc-praxis/tree/main/project-refine Command: npx skills add https://github.com/mdproctor/cc-praxis --skill project-refine
Use when seeking improvement opportunities in a project — "find duplication", "bloat check", "look for ways to improve docs", "do a refine session". NOT for correctness or compliance — use project-health for that.
A dedicated improvement session across documentation and code (including tests). Looks at things that already work and asks whether they could be better. Never blocks work — findings are always opportunities, never failures.
Start a refinement session with /project-refine to identify opportunities to shrink and clarify your project.
High-intent search queries and answers about installing and using this skill.
A project refinement session identifies opportunities to reduce complexity and improve structure across docs and code. It scopes health checks to docs, code, and universal areas, outputting actionable findings as opportunities rather than failures.
Improving code organization involves a focused refinement session with tiered depth that enforces domain-driven checks across docs and code. It reviews existing working files to identify opportunities to shrink and clarify project structure.
Run a project health check by starting a refinement session that scopes checks to docs, code, and universal areas. It outputs actionable findings as improvement opportunities without automatically applying changes or blocking work.
Refinement sessions simplify projects by identifying opportunities to shrink and clarify without breaking functionality. Findings are always opportunities, never failures, and no changes are applied automatically, ensuring existing working code remains intact.
No, project refinement does not check correctness or compliance. It focuses on finding duplication, bloat, and improvement opportunities across docs and code. For correctness or compliance checks, use a dedicated project health tool instead.
J-PsterValidate and create mandatory project documentation baseline files before implementation.
oozoofrogAudit CLAUDE.md token efficiency and context architecture across repository layers.
abudhahirAnalyze code for design patterns and anti-patterns with refactoring suggestions.
rafaelminatto1Orchestrate multiple specialized agents for cross-domain analysis and unified reporting.
