theme-consistency

Enforce theme.yaml values and CSS variables across prototype screens.

Updated Feb 14, 2026
One-click install
npx skills add https://github.com/DYAI2025/MOD_shark-engine --skill theme-consistency-dyai2025
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: theme-consistency
Source: https://github.com/DYAI2025/MOD_shark-engine/tree/main/sharkengine/.claude/skills/theme-consistency
Command: npx skills add https://github.com/DYAI2025/MOD_shark-engine --skill theme-consistency-dyai2025

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enforce consistent theming across prototype mockups by loading and validating a central theme, preventing hardcoded values, and ensuring session-to-session visual stability.

Core Features & Use Cases

  • Loads theme.yaml and applies var-based styling across screens
  • Checks for hardcoded colors, spacing, and typography; replaces with theme tokens
  • Locks the theme after first approved screen to preserve consistency

Quick Start

Generate a new prototype screen with the theme loaded and applied to ensure consistency.

Frequently Asked Questions about theme-consistency

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

FAQPage Schema
How do I maintain theme consistency across multiple prototype screens?

To keep prototype visuals consistent, load theme.yaml values and apply var-based styling across screens. This checks for hardcoded colors, spacing, and typography, replacing them with theme tokens.

Why does my HTML mockup have hardcoded colors instead of theme tokens?

HTML mockups get hardcoded colors when theme values are not enforced. Running validation checks detects hardcoded colors, spacing, and typography, replacing them with proper CSS variables.

Can I lock the design system theme after approving the first prototype screen?

Yes, you can lock the theme after the first approved screen to preserve consistency. This prevents new prototype screens from deviating from the established design system tokens.

What is the best way to enforce design system rules during prototype creation?

The best way to enforce design system rules is by applying validation checks during prototype creation. This aligns prototype visuals by enforcing theme.yaml values and CSS variable usage across screens.

Does prototype theme validation work without predefined CSS variables?

No, prototype theme validation requires predefined CSS variables from theme.yaml to function. Without these design tokens, the system cannot replace hardcoded values or enforce visual consistency across mockups.