This workspace contains a set of high-precision "Source of Truth" documents designed to bridge the gap between abstract style guides and production-grade implementation.
Most style guides provide "recommendations." These frameworks provide "decision logic."
Instead of generic rules, these documents define technical constraints, performance thresholds, and explicit architectural patterns that an autonomous agent or a senior engineer can execute with surgical precision. The goal is to eliminate ambiguity and prevent technical debt before the first line of code is written.
Focuses on the raw mechanics of the JavaScript language. It defines rigorous standards for:
- Memory & Reference Engineering: Managing the lifecycle of objects to prevent leaks.
- Type Safety: Eliminating implicit coercion bugs through a strict truthiness matrix.
- Concurrency: Standardizing Promise lifecycles and parallel execution strategies.
Translates the Airbnb React Style Guide into an actionable decision engine. It covers:
- Component Architecture: Exact criteria for choosing between functions, classes, and hooks.
- JSX Rigor: Precise formatting and attribute standards to ensure codebase uniformity.
- A11y Compliance: Mandatory accessibility patterns for production-ready UI.
A high-precision technical specification for CSS-in-JS implementation. It defines standards for:
- Naming Conventions: Strict rules for object keys, modifiers, and device-agnostic breakpoints.
- Structural Ordering: Optimized placement of styles relative to components to reduce indirection.
- Theming Architecture: Rigorous domain boundaries for design tokens and cardinality logic for inline styles.
When implementing a feature or fixing a bug, refer to the corresponding SKILLS.md file. The documents are structured as:
- Constraints: What is strictly prohibited (e.g., "
varis a critical system failure"). - Decision Matrices: Tables that map specific scenarios to the correct technical implementation.
- Checklists: Verification steps to ensure the implementation meets the architectural standard.
This approach transforms documentation from a passive reference into an active logic engine for high-quality software engineering.
Created by miii-cli