accelint-design-foundation

Style React components with Accelint Design Foundation tokens and CSS modules.

Updated Mar 24, 2026
One-click install
npx skills add https://github.com/Ahnd6474/Jakal-flow --skill accelint-design-foundation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: accelint-design-foundation
Source: https://github.com/Ahnd6474/Jakal-flow/tree/main/.skill-staging/skills/accelint-design-foundation
Command: npx skills add https://github.com/Ahnd6474/Jakal-flow --skill accelint-design-foundation

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

Designing UI with Accelint's opinionated Tailwind system is error‑prone and inconsistent, causing teams to waste time on manual token selection, spacing decisions, and variant handling.

Core Features & Use Cases

  • Semantic Token Guidance: Provides the correct bg-*, fg-*, outline-* classes for automatic theming.
  • Semantic Spacing Scale: Replaces numeric Tailwind spacing with a meaningful, seven‑step scale.
  • @variant System: Enables data‑attribute driven styling without arbitrary Tailwind variants.
  • CSS Module Best Practices: Enforces single @apply per rule, layer hierarchy, and required @reference directives.

Quick Start

Use the skill to style a Button component with semantic tokens and proper CSS module layers.

Frequently Asked Questions about accelint-design-foundation

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

FAQPage Schema
How do I apply semantic design tokens to React components using Tailwind CSS?

Apply semantic design tokens to React components by using prescribed bg-*, fg-*, and outline-* classes for automatic theming. This enforces correct token selection and consistent styling without manual CSS overrides.

What is the semantic spacing scale in Tailwind CSS modules?

The semantic spacing scale in Tailwind CSS modules replaces numeric spacing values with a meaningful, seven-step scale. This provides consistent layout dimensions across UI components instead of arbitrary pixel or rem values.

How do I use data-attribute driven styling with the @variant system?

Use data-attribute driven styling with the @variant system to apply conditional styles without arbitrary Tailwind variants. This enables component state styling directly through HTML data attributes for cleaner CSS modules.

Does this styling approach require a specific PostCSS plugin for Tailwind CSS modules?

Yes, this styling approach requires Tailwind CSS configured with the @accelint/postcss-tailwind-css-modules plugin. It also requires CSS modules adhering to the prescribed layer hierarchy and import of @accelint/design-foundation or @accelint/design-toolkit.

What are the CSS module best practices for single @apply rules and layer hierarchy?

CSS module best practices enforce a single @apply per rule, strict layer hierarchy, and required @reference directives. This structure prevents styling conflicts and maintains predictable cascade behavior across React components.

Why does manual token selection cause inconsistencies in Tailwind UI design?

Manual token selection causes inconsistencies in Tailwind UI design by allowing arbitrary spacing, color, and variant choices. Using an opinionated design foundation solves this by standardizing semantic tokens and spacing scales.