The entity system at the heart of Waaseyaa
How waaseyaa’s EntityInterface, ContentEntityBase, and field system work — and how the entity-system specialist skill made cross-session development possible.
How waaseyaa’s EntityInterface, ContentEntityBase, and field system work — and how the entity-system specialist skill made cross-session development possible.
A skill set that governs framework-app co-development across three repos: enforcing patterns, auditing divergence, and extracting shared code.
Two Claude Code skills for applying and maintaining the three-tier codified context architecture — what they do, how they work, and how to get started.
What waaseyaa is, why it exists, and how planning with GitHub issues before coding changes the dynamic of building complex software with AI.
How subsystem specs and MCP retrieval tools handle architectural knowledge too large for hot memory — and why stale specs are worse than no specs.
What specialist skills are, why the 50% domain knowledge rule matters, and how waaseyaa’s spec-backed orchestration keeps AI consistent across a 29-package PHP monorepo.
How to structure your CLAUDE.md as a routing layer so AI agents always know where to look.
Token limits aren’t the real problem with AI in large codebases — inconsistent context is. Here’s what breaks and why a three-tier architecture fixes it.
How to write reusable Claude Code skills, featuring a codebase cleanup skill I built and ran on this very blog.