القائمة
Generate color palettes with Tailwind-scale shades. Use when the user asks about color palettes, color schemes, Tailwind colors, or generating colors for a UI theme.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Keep iterating on the next logical step in a project until a clear stop condition is reached. Use when the user says `/continue-loop`, asks to "keep going", "continue iterating", or wants Codex to repeatedly choose the highest-leverage next task, execute it, verify it, and then continue. Good for open-ended cleanup, refactoring, polish, debt burn-down, and project advancement where the next step should be discovered from the current repo state instead of handed over explicitly.
Find and explain churn hotspots and unstable code clusters in a git repo. Goes beyond a flat "most-edited files" list — auto-detects clusters by directory, by filename stem (foo.go + foo_test.go), and by co-change (files that change together) — then classifies each cluster (unstable / under-development / buggy / tightly-coupled / spec-shifting) and explains *why* it's a problem. Trigger whenever the user asks about churn, hotspots, unstable code, files that change a lot, refactoring candidates, technical debt hotspots, "what's a mess", "/hotmess", or any combination of folder + time window where they want insight rather than just numbers. Auto-detects code files when no extension is given.
Scan web pages for UI consistency issues — misalignment, bad contrast, near-miss colors, inconsistent spacing, and more. Requires Chrome DevTools MCP. Use when the user asks to "check the UI", "scan for design issues", "run UXly", or "audit the page".
Systematic debugging techniques for unclear root causes. Use when a bug's origin is unknown, multiple hypotheses need testing, you need to narrow down a failing area, end-to-end tests fail but you can't tell where, or the user says "I don't know why this is broken". Includes test bombs (hypothesis elimination) and layered tests (pipeline stage isolation).
Apply strict .NET/C# coding standards to a project or solution. Adds Roslynator and Meziantou analyzers, a comprehensive .editorconfig with 80+ diagnostic rules, naming conventions, and performance warnings. Use when the user wants to enforce strict code quality, set up analyzers, or add an .editorconfig to a .NET project.
Run C# static analysis, auto-fix code issues, format code, find unused code, and enforce coding standards in .NET projects. Use when the user asks about code quality, linting, static analysis, code cleanup, unused code, or formatting in C# / .NET projects.
| name | palette |
| description | Generate color palettes with Tailwind-scale shades. Use when the user asks about color palettes, color schemes, Tailwind colors, or generating colors for a UI theme. |
| argument-hint | [hex colors] |
Requires Node.js >= 18. No install needed — runs via npx:
npx @asynkron/palette
A zero-dependency CLI that generates complete color palettes with Tailwind-scale shades (50–950). Uses OKLCH color space for perceptually uniform shade ramps. Takes hex colors, a color wheel strategy, and a count, and outputs semantically named colors ready for use in design systems.
All colors are automatically normalized to matching lightness and chroma so the palette looks cohesive regardless of the input colors.
Random 3-color palette (no input needed):
npx @asynkron/palette
From a single anchor color:
npx @asynkron/palette '#aa5420'
Colors can be passed without # to avoid shell quoting:
npx @asynkron/palette aa5420 dc5b40
5 triadic colors from an anchor:
npx @asynkron/palette aa5420 --count 5 --strategy triadic
Two input colors, generate 3 more:
npx @asynkron/palette aa5420 9b2010 --count 5
Vibrant mood (high saturation):
npx @asynkron/palette aa5420 --vibrant
Pastel mood (soft, light):
npx @asynkron/palette aa5420 --pastel
Keep exact input colors (skip normalization):
npx @asynkron/palette aa5420 3366ff --raw
| Flag | Short | Default | Purpose |
|---|---|---|---|
--count N | -c | max(inputs, 3) | Total number of base colors |
--strategy NAME | -s | evenly-spaced | Color wheel strategy |
--raw | -r | off | Skip normalization, keep exact input colors |
--vibrant | — | off | High saturation, punchy colors |
--pastel | — | off | Soft, light, desaturated colors |
--help | -h | — | Show help |
| Strategy | Description |
|---|---|
evenly-spaced | Equal spacing around the wheel (360°/count) — default |
analogous | Adjacent colors (±30°) |
complementary | Opposite colors (180°) |
split-complementary | Split complement (150° and 210°) |
triadic | Three-way split (120°) |
tetradic | Four-way split (90°) |
Each base color produces 11 Tailwind-scale shades. Shade 500 is the base color:
primary-50: #f7eae4
primary-100: #eed6ca
primary-200: #e0b9a5
primary-300: #d0987c
primary-400: #bb724b
primary-500: #aa5420 ← input
primary-600: #8a4113
primary-700: #692d06
primary-800: #4c1c00
primary-900: #2e0b00
primary-950: #180200
Colors are named based on count and position:
| Count | Names |
|---|---|
| 1 | primary |
| 2 | primary, secondary |
| 3 | primary, secondary, accent |
| 4 | primary, secondary, accent, neutral |
| 5 | primary, secondary, tertiary, accent, neutral |
| 6+ | primary, secondary, tertiary, accent, neutral, accent-2, ... |
--count) are generated using the chosen strategy, rotating hue on the color wheel.--raw). Mood presets (--vibrant, --pastel) override the target lightness/chroma.NO_COLOR=1 to disable.# prefix to avoid shell quoting issues--vibrant for marketing/hero sections, --pastel for backgrounds/subtle UI--raw when input colors are from an existing brand and must not be adjusted