
Philosophy Compliance Workflow
This is a systematic code review workflow that checks whether your implementation actually follows amplihack's core principles: ruthless simplicity, brick philosophy, and Zen minimalism. It walks through a structured five question analysis (Do we need this? What's simplest? Is it a self-contained brick? Can AI rebuild it from spec? Does complexity add value?) and generates a scored report with critical violations, warnings, and specific fix recommendations. Use it before merging, during architecture reviews, or when you suspect complexity creep. The scoring rubric is opinionated but clear, and the "regeneratable by AI" lens is an interesting forcing function for keeping module boundaries clean. Most valuable when you need someone to tell you that your eight-responsibility SessionManager should actually be three separate bricks.
- skills.sh installs
- 136
- GitHub stars
- 76
- last updated
- Aug 21, 2026
Install
$ npx -y skills add rysweet/amplihack --skill philosophy-compliance-workflow --agent claude-codeInstalls into .claude/skills of the current project.
Files
Philosophy Compliance Workflow Skill
Purpose
Systematic philosophy compliance review that ensures all code and architecture aligns with amplihack's core principles: ruthless simplicity, brick philosophy, and Zen-like minimalism. This skill validates that implementations serve clear purposes without unnecessary complexity.
When to Use This Skill
USE FOR:
- Architecture reviews before implementation
- Code reviews for philosophy alignment
- Refactoring validation (did we actually simplify?)
- Module design verification
- Pre-merge philosophy checks
- Identifying over-engineering and complexity creep
AVOID FOR:
- Functional bug fixes (not philosophy issues)
- Performance optimization alone
- Documentation updates
- Pure syntax/style issues
Core Philosophy Principles
The Zen of Simple Code
- Each line serves a clear purpose without embellishment
- As simple as possible, but no simpler
- Complex systems from simple, well-defined components
- Handle what's needed now, not hypothetical futures
The Brick Philosophy
Sponsors
Details
- Repository
- github.com/rysweet/amplihack
- Categories
- Git & Pull Requests, Code Review & Quality, Automation & Workflows
- First seen
- Jun 3, 2026
More from rysweet/amplihack
All 58- N Version Workflow134
- Outside In Testing134
- Xlsx
- Cybersecurity Analyst1.5K
- Lawyer Analyst690
- Psychologist Analyst456
- Mermaid Diagram Generator429
- Pptx422
- Economist Analyst382
- Design Patterns Expert359
- Learning Path Builder342
- Philosopher Analyst321
- Storytelling Synthesizer311
- Documentation Writing308
- Political Scientist Analyst303
- Novelist Analyst288
- Knowledge Extractor281
- Socratic Review278
- Physicist Analyst277
- Chemist Analyst276
- Computer Scientist Analyst272
- Docx268
- Journalist Analyst264
- Roadmap Strategist262