Automated summary
Manage and customize UI themes (light/dark/custom) for a trading platform using Tailwind CSS and next-themes.
Strengths
- Supports creating, editing, and switching themes
- integrates with next-themes and Radix UI
- includes trading-specific considerations like color blindness and eye strain.
Limitations
- Only works within the trading platform's UI
- theme creation requires familiarity with CSS variables
- limited to pre-defined color variables.
Use when you need to switch between themes or customize the appearance of the trading platform.
Avoid using for non-theme related UI changes, or if you need to modify component layouts beyond colors.
Security analysis
SafeThe skill only modifies client-side theme preferences (CSS variables, localStorage) using a UI framework. There are no shell executions, network requests, or destructive operations.
No concerns found
How this analysis is madeExamples
Switch to dark theme on the trading platform.Create a new theme named 'my-theme' based on the dark theme.List all available themes.name: theme description: Switch and customize UI themes (light/dark/custom) argument-hint: "[light|dark|--list|--create|--edit]"
Theme Manager
Manage UI themes for the trading platform.
Usage
/theme- Show current theme/theme light- Switch to light theme/theme dark- Switch to dark theme/theme --list- List all available themes/theme --create trading-dark- Create new theme/theme --edit dark- Edit existing theme/theme --export- Export theme as JSON
Theme System
- Framework: Tailwind CSS + CSS variables
- Provider: next-themes (ThemeProvider)
- Storage: localStorage
- Components: Radix UI primitives
Theme Files
services/ui/
├── src/
│ ├── contexts/ThemeContext.tsx
│ ├── components/theme-provider.tsx
│ ├── components/mode-toggle.tsx
│ └── styles/
│ ├── globals.css # CSS variables
│ └── themes/
│ ├── light.css
│ ├── dark.css
│ └── trading-dark.css
└── tailwind.config.js
Instructions
When this skill is invoked:
-
Parse arguments:
- No args: Show current theme info
- Theme name: Switch to that theme
--list: List all available themes--create <name>: Create new theme--edit <name>: Edit theme variables--export: Export current theme
-
Show current theme:
Current Theme ═══════════════════════════════════════════════════════════ Active: dark System preference: dark Colors: ───────────────────────────────────────────────────────── --background: hsl(222.2 84% 4.9%) ████ --foreground: hsl(210 40% 98%) ████ --primary: hsl(217.2 91.2% 59.8%) ████ --secondary: hsl(217.2 32.6% 17.5%) ████ --accent: hsl(217.2 32.6% 17.5%) ████ --destructive: hsl(0 62.8% 30.6%) ████ --muted: hsl(217.2 32.6% 17.5%) ████ Chart colors: ───────────────────────────────────────────────────────── --chart-up: hsl(142 76% 36%) ████ (green) --chart-down: hsl(0 84% 60%) ████ (red) --chart-grid: hsl(217 32% 25%) ████ -
For
--list:Available Themes ───────────────────────────────────────────────────────── • light System light theme • dark System dark theme (active) • trading-dark Dark theme optimized for trading • bloomberg Bloomberg terminal style -
For
--create:- Create new theme CSS file
- Copy from base theme
- Guide through customization
- Register in theme provider
-
For
--edit:- Open theme CSS variables
- Show color picker suggestions
- Preview changes
- Validate contrast ratios
-
Theme CSS structure:
/* themes/trading-dark.css */ [data-theme="trading-dark"] { --background: 222.2 84% 4.9%; --foreground: 210 40% 98%; --card: 222.2 84% 4.9%; --primary: 217.2 91.2% 59.8%; /* Chart-specific */ --chart-up: 142 76% 36%; --chart-down: 0 84% 60%; --chart-volume: 217 91% 60%; } -
Trading-specific considerations:
- Contrast: Ensure readability for numbers
- Color blindness: Avoid red/green only
- Eye strain: Dark themes for long sessions
- Chart colors: Clear up/down distinction
- Alert colors: Warning/error visibility
-
Apply theme programmatically:
import { useTheme } from 'next-themes'; function ThemeSwitch() { const { theme, setTheme } = useTheme(); return ( <button onClick={() => setTheme('dark')}> Dark Mode </button> ); }
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/theme-manager-mmh8qr3e/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/theme-manager-mmh8qr3e' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/theme-manager-mmh8qr3e/download' --output '.skill-downloads/theme-manager-mmh8qr3e/SKILL.md.part' && mv '.skill-downloads/theme-manager-mmh8qr3e/SKILL.md.part' '.skill-downloads/theme-manager-mmh8qr3e/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/theme-manager-mmh8qr3e/SKILL.md' && test -s '.skill-downloads/theme-manager-mmh8qr3e/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/theme' && cp -R '.skill-downloads/theme-manager-mmh8qr3e' '.claude/skills/theme'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/theme-manager-mmh8qr3e'openskills read 'theme-manager-mmh8qr3e'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/theme-manager-mmh8qr3e/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.