sk-tokens-neomorphism

Convert hardcoded colors and Tailwind shadows to Neomorphism 2.0 CSS token utilities.

Updated May 19, 2026
One-click install
npx skills add https://github.com/TimeKast/AgendaInteligente --skill sk-tokens-neomorphism
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sk-tokens-neomorphism
Source: https://github.com/TimeKast/AgendaInteligente/tree/main/.claude/skills/sk-tokens-neomorphism
Command: npx skills add https://github.com/TimeKast/AgendaInteligente --skill sk-tokens-neomorphism

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents inconsistent styling and theme breakage by enforcing the TimeKast Starter Kit’s Neomorphism 2.0 design-system tokens as the single source of truth.

Core Features & Use Cases

  • Consistent visual language: Guides you to use CSS variables, Tailwind v4 theme aliases, and the provided neo-* elevation utilities for surfaces, shadows, and semantics across the app.
  • Neomorphism-correct components: Ensures shadows define edges (no borders) and directs you to the correct outset/inset/float/pressed tier based on component role (cards, inputs, overlays, active states).
  • Multi-theme safety: Supports Light, Midnight, and Dark/Midnight rendering by requiring semantic classes (bg-background, text-foreground, neo-outset, etc.) instead of hardcoded colors or default Tailwind shadcn overrides.

Quick Start

Use the sk-tokens-neomorphism rules to style your component by replacing any hardcoded colors or Tailwind defaults with the appropriate bg/text semantic aliases and neo-* utilities (for example, use neo-interactive for buttons and neo-inset for inputs).

Frequently Asked Questions about sk-tokens-neomorphism

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

FAQPage Schema
How do I enforce Neomorphism design tokens for consistent UI styling in Tailwind v4?

To enforce Neomorphism design tokens, replace hardcoded colors and default Tailwind shadows with kit-approved CSS variables and semantic aliases like bg-background and neo-outset. This maintains UI consistency and prevents theme drift across components.

Why do my Neomorphism components break in dark and midnight themes?

Neomorphism components break across dark and midnight themes when using hardcoded hex or rgb literals instead of semantic classes. To ensure multi-theme safety, apply semantic bg/text/ring aliases tied to globals.css rather than default Tailwind shadcn overrides.

What is the correct way to style elevated surfaces and recessed inputs without borders?

To style elevated surfaces and recessed inputs without borders, use the provided neo-* elevation utilities to define edges with shadows. Apply neo-outset for cards, neo-inset for inputs, and neo-interactive for buttons based on component role.

Can I use default Tailwind shadow-md and shadow-lg utilities for Neomorphism styling?

You cannot use default Tailwind shadow-md or shadow-lg utilities for Neomorphism styling. The system prohibits default shadow tokens and border-based separation, requiring --neo-* CSS variables and utilities instead to ensure correct outset, inset, float, and pressed shadow tiers.

How do I convert hardcoded CSS colors to semantic design tokens for frontend styling?

To convert hardcoded CSS colors to semantic design tokens, map your hex and rgb literals to the kit-approved semantic aliases defined in src/app/globals.css. Use bg-background, text-foreground, and neo-* utilities to ensure correct light, dark, and midnight theme rendering.

When should I use neo-interactive versus neo-inset utilities for component styling?

Use neo-interactive utilities for interactive buttons and active states, and neo-inset for recessed inputs and pressed elements. These neo-* elevation utilities replace default Tailwind shadows and borders to define correct Neomorphism edges based on component role.