What problem does it solve? Codebases built by AI assistants often drift into generic patterns: framework-shaped file structures, purple-gradient templated UI, and vague auto-generated docs. This Skill defines a consistent house style so every route, screen, and doc follows the same opinionated rules. ## Core Features & Use Cases - Route-based file layout: One route owns one file, with shared code extracted only when two or more routes genuinely use it, covering both Bun REST APIs and WebSocket gateways. - UI aesthetic rules: Enforces calm, Apple/Google-grade design with Tailwind, restrained color, spring-based micro-animations under 300ms, and explicit rules for when gradients are allowed. - Documentation ownership workflow: The human writes feature docs in plain and technical layers while the agent audits them for outcomes, real names, and accuracy. - Use Case: When starting a new frontend screen or backend endpoint, load this Skill so the agent places handlers in the right route file, avoids gradient-heavy templated UI, and prompts you to write the docs instead of drafting them for you. ## Quick Start Load the house-style skill before writing code or designing a screen so all output follows my route-based layout and design rules.
