frontend-governance

Enforce semantic tokens and Anti-Slop protocols across frontend UI generation.

30|10|Updated Jan 15, 2026
One-click install
npx skills add https://github.com/dinesh-git17/claudehome --skill frontend-governance
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: frontend-governance
Source: https://github.com/dinesh-git17/claudehome/tree/main/.claude/skills/frontend-development
Command: npx skills add https://github.com/dinesh-git17/claudehome --skill frontend-governance

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures frontend UI work adheres to a contemplative design system, eliminating ad-hoc styling and visual drift across projects.

Core Features & Use Cases

  • Enforces a disciplined design system across UI generation to ensure consistency and accessibility.
  • Implements Anti-Slop protocols to minimize decoration, over-styling, and inconsistent components.
  • Provides design guidelines for semantic tokens, component governance, and design intent validation in modern frontend work.

Quick Start

Use the frontend-governance skill to audit a UI component for semantic token usage and visual consistency.

Frequently Asked Questions about frontend-governance

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

FAQPage Schema
How do I enforce semantic tokens and UI consistency across my frontend components?

To enforce semantic tokens and UI consistency, you need a design system governance protocol that audits frontend codebases during development. This ensures component libraries use restrained aesthetics and eliminates visual drift by validating design intent.

What are Anti-Slop protocols for frontend UI generation?

Anti-Slop protocols for frontend UI generation are rules that minimize decoration, over-styling, and inconsistent components. They enforce a disciplined design system to ensure visual consistency and accessibility across modern frontend projects.

How do I audit a UI component for semantic token usage and visual consistency?

You audit a UI component by applying a contemplative design system that checks for semantic token usage and visual consistency. This process eliminates ad-hoc styling by validating design intent and enforcing forbidden pattern constraints.

Does this design system governance work with server components?

Yes, design system governance works with server components by providing specific guidance for them within its frontmatter-driven instructions. It ensures semantic tokens and component governance are maintained across server-rendered UI codebases.

What is the best way to prevent visual drift in a frontend component library?

The best way to prevent visual drift in a frontend component library is to implement a design intent protocol. This validates design decisions, enforces restrained aesthetics, and applies component governance during development and refactors.

When should I apply frontend governance protocols during development?

You should apply frontend governance protocols during UI generation, development, and refactors. This ensures semantic tokens and consistent design decisions are enforced continuously, preventing ad-hoc styling and maintaining accessibility.