aytordev-theming

Centralize Kanagawa theming data and API for aytordev modules.

1|Updated Jun 2, 2025
One-click install
npx skills add https://github.com/aytordev/system --skill aytordev-theming
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aytordev-theming
Source: https://github.com/aytordev/system/tree/main/modules/common/ai-tools/skills/aytordev/theming
Command: npx skills add https://github.com/aytordev/system --skill aytordev-theming

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

aytordev centralized theme system enables consistent theming across modules by exposing a single Kanagawa theme provider and a centralized API.

Core Features & Use Cases

  • Centralized source of truth for theming data via config.aytordev.theme.
  • Palette access and appTheme helpers to ensure consistent variants and polarity across all modules.
  • Guidance for migrating to a standardized theming approach with Stylix and Catppuccin.

Quick Start

Configure your module to consume the central Kanagawa theme provider by referencing config.aytordev.theme in your module configuration.

Frequently Asked Questions about aytordev-theming

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

FAQPage Schema
How do I centralize Kanagawa theming across multiple Nix modules?

Centralize Kanagawa theming by referencing a unified configuration path at config.aytordev.theme, exposing palette access and appTheme helpers to ensure consistent variants and polarity across all modules.

What is the best way to manage a unified Nix color palette for aytordev modules?

Manage a unified Nix color palette by consuming the central Kanagawa theme provider, which acts as a single source of truth for theming data and supplies standardized appTheme utilities for module configuration.

Can I migrate my existing Stylix and Catppuccin setups to a centralized Kanagawa theme?

Yes, you can migrate Stylix and Catppuccin configurations to the centralized Kanagawa theme approach using provided migration notes and documented example patterns for a standardized theming workflow.

How does the appTheme utility handle consistent variants and polarity?

The appTheme utility handles consistent variants and polarity by accessing centralized palette data through config.aytordev.theme, ensuring all consuming modules apply identical theme attributes.

Do I need specific dependencies to apply a centralized Kanagawa theme in Nix?

No external dependencies are required to apply the centralized Kanagawa theme; it operates by exposing palette access and appTheme helpers directly through the config.aytordev.theme configuration path.

Why should I use a centralized theme provider instead of configuring palettes per module?

Use a centralized theme provider to avoid configuration fragmentation, ensuring that all modules reference identical Kanagawa variants and polarity from a single source of truth rather than maintaining isolated palettes.