check

Validate CSS, templates, and docs against FyrsmithLabs Terminal Elegance guidelines.

Updated Jan 7, 2026
One-click install
npx skills add https://github.com/fyrsmithlabs/marketplace --skill check
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: check
Source: https://github.com/fyrsmithlabs/marketplace/tree/main/plugins/fs-design/skills/check
Command: npx skills add https://github.com/fyrsmithlabs/marketplace --skill check

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill helps teams enforce FyrsmithLabs Terminal Elegance design system across CSS, templates, and documentation by detecting violations, accessibility gaps, and design-token misuses.

Core Features & Use Cases

  • Automated system-wide checks: Scans CSS, .templ, .html, and .md files to uncover color, spacing, contrast, and token usage violations.
  • A11y & WCAG compliance: Flags focus states, aria usage, color contrast, and semantic structure issues.
  • Design token validation: Validates token presence and naming and suggests token-based replacements.
  • Use Case: A UI team runs /design-check in CI to ensure new PRs adhere to the design system before merge.

Quick Start

Run the design-check on your repository to generate a human-readable report. For CI, use the --ci flag to emit CI-friendly output.

Frequently Asked Questions about check

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

FAQPage Schema
How do I audit my CSS and templates for design system violations?

Audit CSS and templates for design system violations by running a design-check command that scans static/css folders and template files using Stylelint and axe-core, outputting a human-readable report of token and accessibility issues.

How do I check WCAG compliance and accessibility gaps in my HTML files?

Check WCAG compliance and accessibility gaps in HTML files by running an automated scan with axe-core that flags focus states, aria usage, color contrast, and semantic structure violations.

Can I run design token validation in CI for my design system docs?

Run design token validation in CI for design system docs by executing the design-check command with a --ci flag, which validates token presence and naming in Markdown files and emits CI-friendly output.

What is the best way to enforce consistent spacing and color tokens across a repository?

Enforce consistent spacing and color tokens across a repository by running an automated system-wide check that validates design-token formats and suggests token-based replacements for CSS and template files.

Does the design system audit support Go template files and Markdown documentation?

The design system audit supports Go template files and Markdown documentation, scanning .templ, .html, and .md files to surface style, accessibility, and token-usage violations across the project.

Why does my design token validator not catch certain CSS style violations?

A design token validator may not catch certain CSS style violations because token validation specifically targets token presence and naming, while Stylelint handles the broader CSS rule enforcement separately.