skills.rest
MithrilMan
MithrilManCOMMUNITY
Explore all skills by this author →
𝕏@MithrilManGitHub

neomithril-component-authoring

Classify UI component work in neomithril-ui to enforce design-system compliance.

Updated Mar 12, 2026
Search Tags:#storybook#tokens#design-system#ui-patterns#css-modules#neumorphism#component-authoring
One-click install
npx skills add https://github.com/MithrilMan/neomithril-ui --skill neomithril-component-authoring
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: neomithril-component-authoring
Source: https://github.com/MithrilMan/neomithril-ui/tree/main/.codex/skills/neomithril-component-authoring
Command: npx skills add https://github.com/MithrilMan/neomithril-ui --skill neomithril-component-authoring

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill helps teams ensure neomithril-ui components adhere to the repository's design system, neumorphic rules, token contracts, CSS module patterns, and proper docs/story/manifest updates during development and refactors.

Core Features & Use Cases

  • Standardizes component authoring with design-system alignment, token-driven styling, and auto-generated documentation scaffolds.
  • Guides classification, API surface decisions, and story/manifest updates to maintain consistency across the library.
  • Use Case: when adding or refactoring shared UI components to ensure consistency and maintainability across surfaces, tokens, and docs.

Quick Start

Create or update a component in neomithril-ui following the design-system rules, token contracts, and documentation checks.

Frequently Asked Questions about neomithril-component-authoring

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

FAQPage Schema
How do I enforce design-system compliance when authoring UI components?▼

Enforce design-system compliance by classifying and standardizing UI component work with token-driven styling, CSS module patterns, and documentation scaffolds. This ensures consistency across shared component libraries during development and refactoring.

What is the best way to standardize neumorphic UI components across a design system?▼

Standardize neumorphic UI components by applying design principles, token usage rules, and auto-generated documentation scaffolds. This maintains consistency across surfaces, tokens, CSS modules, stories, and manifests throughout the component lifecycle.

How do I keep Storybook stories and manifests updated when refactoring shared UI components?▼

Keep Storybook stories and manifests updated during refactoring by enforcing documentation checks and public-facing contract validation as part of the component authoring workflow. This guides API surface decisions and maintains library consistency across updates.

Can I use CSS modules with token-driven styling for shared component libraries?▼

Yes, CSS modules work with token-driven styling for shared component libraries. The component authoring process enforces token contracts and neumorphic rules to maintain strict design-system alignment across all component surfaces.

When do I need to run design-system contract checks during component development?▼

Run design-system contract checks during component development whenever adding or refactoring public UI components. This ensures token usage, API surface decisions, and story or manifest updates maintain consistency and maintainability across the library.

Related Skills

Explore More Design & Creative Skills→
jangtrinhjangtrinh

design-init

Automates design system setup with token extraction, component inventory, and Storybook scaffolding.

Community
Advanced
leboncoinleboncoin
92

create-storybook-docs

Generate and update Storybook stories and MDX docs for Spark UI components.

Official
Basic
saajunaidsaajunaid

design-system-tokens

Generate and validate design tokens as CSS variables across three-layer architectures.

Community
Intermediate
AshesOfTheUndeadAshesOfTheUndead

neumorphism

Generate neumorphic design system guidelines with WCAG 2.2 AA accessibility.

Community
Intermediate