What problem does it solve?
Aesth removes ambiguity in interface decisions for dashboards, admin tools, and data-heavy apps by enforcing craft-first rules so designs remain consistent, teachable, and repeatable across sessions.
Core Features & Use Cases
- Persistent design memory: Stores design direction, tokens, component patterns, and decisions in Subcog under the
patterns namespace for project- and user-scoped reuse.
- Automated validation: Checks code and styles against a strict 4px grid, a single depth strategy, and consistent border-radius and typography rules to catch off-grid values and anti-patterns.
- Pattern capture & extraction: Extracts component patterns from existing code and offers to save direction, tokens, and patterns back to Subcog for future sessions.
- Use case: Validate a dashboard card component for spacing, depth, and typography; extract its component pattern and persist it for reuse across projects.
Quick Start
Run /aesth:init to load or initialize the project's design system from Subcog.