proof-of-work
Proof of Work
Show, don't tell. Never make claims about code verification without providing concrete evidence.
Core Principle
Trust through transparency. Every assertion about code quality, test results, builds, or verification must be backed by actual command output, not summaries or assumptions.
Implementation Proof
When implementing features:
- USE Write/Edit tools to make changes
- Never just describe what should be written
- Actually call Write tool to create files
- Actually call Edit tool to modify files
More from thebushidocollective/han
android-jetpack-compose
Use when building Android UIs with Jetpack Compose, managing state with remember/mutableStateOf, or implementing declarative UI patterns.
1.1Kfastapi-async-patterns
Use when FastAPI async patterns for building high-performance APIs. Use when handling concurrent requests and async operations.
785storybook-story-writing
Use when creating or modifying Storybook stories for components. Ensures stories follow CSF3 format, properly showcase component variations, and build successfully.
487atomic-design-fundamentals
Use when applying Atomic Design methodology to organize UI components into quarks, atoms, molecules, organisms, templates, and pages. Core principles and hierarchy.
366solid-principles
Use during implementation when designing modules, functions, and components requiring SOLID principles for maintainable, flexible architecture.
250angular-rxjs-patterns
Use when handling async operations in Angular applications with observables, operators, and subjects.
216