aesth

Validate interface code against a strict 4px grid and depth strategy.

2|Updated Jan 17, 2026
One-click install
npx skills add https://github.com/zircote/aesth --skill aesth
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aesth
Source: https://github.com/zircote/aesth/tree/main/.claude/skills/aesth
Command: npx skills add https://github.com/zircote/aesth --skill aesth

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

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.

Frequently Asked Questions about aesth

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate my interface code against a strict 4px grid system?

You can validate interface code against a 4px grid by running automated checks that detect off-grid spacing values, inconsistent border-radius, and typography anti-patterns to ensure consistent dashboard and SaaS component design.

How does persistent design memory for component patterns work?

Persistent design memory stores design direction, tokens, and component patterns in a namespace under Subcog, allowing project- and user-scoped reuse across sessions for consistent dashboard and admin panel interfaces.

What is the best way to extract and save component patterns from existing code?

The best way to extract component patterns is to analyze existing interface code, identify reusable spacing and depth strategies, and save the extracted tokens and patterns back to persistent memory for future projects.

Can I enforce a single depth strategy across dashboard components?

Yes, you can enforce a single depth strategy across dashboard components by validating styles against consistent depth rules, catching anti-patterns, and applying strict craft-first interface design guidance.

Does this design system validation work for admin panels and SaaS apps?

Yes, this interface design validation is specifically tailored for dashboards, admin panels, and SaaS apps, enforcing strict spacing, depth, and component pattern consistency for data-heavy applications.

Why do my dashboard components have inconsistent spacing and depth?

Dashboard components have inconsistent spacing and depth when interface decisions lack strict craft-first rules, resulting in off-grid values and anti-patterns that automated validation against a 4px grid and single depth strategy can resolve.