themewright
/themewright
Tworzy, stosuje i audytuje premium motywy aplikacji: szkło, soft UI, aurora, chrom i neubrutalizm, z pomiarem komponentów i kontrolą dostępności.
- Autor
- adan35 ↗
- Repozytorium
- themewright ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 03.11.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 28
- Skrypty
- 9
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 03.11.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
- 9 skryptów w paczce. Przejrzyj je przed instalacją, bo Claude może je uruchomić.
Skrypty: bin/themewright.mjs, bin/verify.mjs, lib/checkpoint.mjs, lib/integrate.mjs, lib/integrations.mjs, lib/prefs.mjs, lib/registry.mjs, lib/scaffold.mjs, lib/scope.mjs
Co robi i kiedy
Tworzy, stosuje i audytuje premium motywy aplikacji: szkło, soft UI, aurora, chrom i neubrutalizm, z pomiarem komponentów i kontrolą dostępności.
Wyzwalacze z opisu
Oryginalny opis (EN)
Create, apply, improve, audit or extend premium application themes (Glass, Soft UI / neumorphism, Aurora / mesh gradients, Liquid Metal / chrome, Neubrutalism, or new ones) across an existing app, with measured components, responsive layouts, accessibility and real visual verification. Use when the user says "ThemeWright", asks to add or restyle app themes, make an app look premium with one of these styles, polish forms/tables across themes, audit themes, add a new theme, remember a theme preference, or resume a theme run.
Jak działa
- Non-negotiables
- Commands the user may type
- Pipeline (record each step with TW run update <runId> --step <name> --status done --note "
- Adding or improving a theme
- Taste rules that apply to every theme
Podgląd SKILL.md
---
name: themewright
description: Create, apply, improve, audit or extend premium application themes (Glass, Soft UI / neumorphism, Aurora / mesh gradients, Liquid Metal / chrome, Neubrutalism, or new ones) across an existing app, with measured components, responsive layouts, accessibility and real visual verification. Use when the user says "ThemeWright", asks to add or restyle app themes, make an app look premium with one of these styles, polish forms/tables across themes, audit themes, add a new theme, remember a theme preference, or resume a theme run.
version: 0.1.0
license: MIT
---
# ThemeWright — Crafted themes. Exceptional experiences.
You turn one request into a complete, cohesive theme implementation in a real product. Premium comes from proportion, hierarchy, typography, consistency, responsiveness and interaction detail — not decoration.
`TW` below means `node <this skill's directory>/bin/themewright.mjs` (Node ≥ 20, no dependencies). Run it from the target project root or pass `--project <dir>`.
## Non-negotiables
1. **Scope comes from `TW plan`**, never from your own keyword reading. Run `TW plan "<the user's request, verbatim>"`. If the output looks wrong for what the user plainly meant, write the intent yourself as JSON (fields: `action`, `mode`, `include`, `exclude`, `compare`, `components`, `preserve`, `newTheme`, `preference`) and run `TW resolve --intent <file>`. Both paths apply the same rules; never bypass them. Inspect the parsed intent with `TW plan "<request>" --json`.
Intent schema: `action` ∈ apply | improve | audit | add | remove | remember | forget | resume; `mode` ∈ all | one | named | existing; `include` / `exclude` / `compare` = theme names or aliases; `components` ⊂ forms, tables, charts, buttons, navigation, overlays, cards, states; `preserve` = things not to change (layout, color, typography, spacing…); `newTheme` = `{ "name": "Editorial" }`; `preference` = `{ "key", "value", "level": "project" | "personal", "theme"?, "component"? }`. Unknown values are rejected.
Edge rules: a bare invocation ("ThemeWright, go") means all themes. "One theme" whose default is excluded or only compared falls to the next theme alphabetically — say so and offer the alternative. "Existing themes" with none installed is an error: ask which themes. "Everywhere / all my projects" → personal level; otherwise project level.
2. **Selection rules** (enforced by the resolver): no theme restriction → all registered themes; "one theme" without a name → Neubrutalism (or the project's explicit `selection.defaultSingle`); a named theme → that theme; a subset → only that subset; exclusions respected; a theme named only for comparison or rejection ("like Glass", "instead of Glass", "not like the brutalist one") is **not** implemented.
3. **`readOnly: true` (audit / plan / remember / forget) means you do not modify application code.** Write findings to the report; preferences only via `TW prefs`.
4. Preserve installed themes, unrelated changes, business logic, permissions and user data. Never overwrite a user's saved theme choice; existing apps get `--initial none`, only brand-new apps may start on Neubrutalism.
5. Every integration edit is idempotent: use `TW integrate` for boot script / stylesheet links / CSS imports / manifest, or the same marker-block pattern (`themewright:<name>` markers) when editing by hand. Re-running must not duplicate providers, selectors, styles or config.
6. Never claim a check, skill, model setting or screenshot you did not actually run or see. Say what was not verified.
7. Ask the user only when information is missing that blocks correct work, or an action needs authorization (publishing, production, deleting user data). Routine design decisions are yours.
## Commands the user may type
| Request | What to do |
|---|---|
| `ThemeWright: apply all themes` | full pipeline, all themes |
| `ThemeWright: create one premium theme` | full pipeline, Neubrutalism |
| `ThemeWright: apply Glass and Aurora only` | full pipeline, those two |
| `ThemeWright: improve Neubrutalism without changing layout` | refine that theme; layout files and structure untouched |
| `ThemeWright: audit all themes` | read-only audit → report |
| `ThemeWright: polish forms and tables across existing themes` | improve, components = forms, tables, themes = installed |
| `ThemeWright: add a theme called Editorial` | extension workflow (below) then implement it |
| `ThemeWright: remember smaller corner radii for this project` | `TW prefs set geometry.radius "smaller" --level project` |
| `ThemeWright: resume the previous implementation` | `TW resume`, continue from `nextStep`, re-run listed checks |
Natural phrasings work the same way — always go through `TW plan`.
## Pipeline (record each step with `TW run update <runId> --step <name> --status done --note "..."`)
Start with `TW run start "<request>"` (prints the plan and a run id). Checkpoints live in `<project>/.themewright/runs/`; they are claims, not proof.
1. **interpret** — `TW plan`. Note excluded/compared themes in the run.
2. **inspect** — read project instructions (CLAUDE.md, AGENTS.md, README, contributing), the styling architecture (Tailwind config, CSS variables, CSS-in-JS, component library, existing theming/dark mode), routing/shell, and any existing theme code. Identify the adapter (see `references/adapters.md`). Do not force React/shadcn into a non-React app.
3. **discover** — `TW integrations`. For each capability record `available-used`, `available-unnecessary`, `missing`, or `blocked` with `--integration '{"id":"impeccable","status":"available-used","why":"..."}'`. Use what helps (see `references/integrations.md`); missing optional skills never stop the run.
4. **load-specs** — `TW prefs effective --project .` and `TW show <theme>` for each theme in scope. Only explicit preferences are defaults; inferred ones are hints.
5. **contract** — write `.themewright/runs/<runId>/contract.md`: themes, token mapping (app tokens ↔ `--th-*` vocabulary), scale (type, spacing, control heights, radii, borders, icon sizes, row density), breakpoints chosen from content, what will not change, and acceptance checks pulled from each theme's `acceptance` list and `references/quality-contract.md`.
6. **baseline** — if the app can run, capture before-screenshots with `node <skill>/bin/verify.mjs` (see `references/verification.md`). If it cannot run, say so and continue.
7. **primitives** — improve shared tokens and primitives first (buttons, fields, tables, cards, overlays) so themes restyle through tokens, not per-page overrides. Keep existing component APIs.
8. **implement** — one stylesheet per theme scoped to `[data-tw-theme="<id>"]` (or the app's existing theme mechanism), light and dark. Cover every surface in the quality contract, including portals, toasts, menus, date pickers and third-party widgets. No scattered hard-coded values.
9. **integrate** — theme picker in the app's existing settings/appearance area, persistence, first-paint boot (`TW integrate --html index.html --themes ... --initial none|<id>`), reduced-motion and the persistent motion-pause preference for themes with ambient motion. Respect SSR/hydration (boot script before paint, no mismatch).
10. **verify** — run functional checks (build, type-check, lint, existing tests) and `verify.mjs` across themes × light/dark × 360/390/768/1024/1440/1920 (+ widths where your layout changes). Look at the screenshots yourself.
11. **fix** — fix meaningful defects (broken layout, contrast, invisible focus, overflow, unreadable data, motion that ignores preferences), re-run the affected checks. Bounded: at most 3 fix rounds; stop polishing cosmetics once acceptance checks pass.
12. **report** — `.themewright/runs/<runId>/report.md`: what changed, themes, files, checks actually run with results, screenshots, integrations status, known limits, what was not verified. Then mark `report` done.
## Adding or improving a theme
- New: `TW scaffold "Editorial"` → fill every field of `theme.json` and `spec.md` (design intent, tokens, surfaces, typography, geometry, components, states, appearance, motion, accessibility & fallbacks, performance, anti-patterns, acceptance, evals) → `TW validate .themewright/themes/editorial` → implement like any other theme. No orchestrator or router changes are needed: the registry discovers it. Built-in contributions use `--builtin`.
- Improve: edit the theme's spec, bump its `version` (semver: patch = clarification, minor = new guidance, major = changes that would restyle existing projects), run `TW validate`.
## Taste rules that apply to every theme
Read `references/quality-contract.md` before implementing. In short: measured scale, one dominant accent, quiet dense data, 44px touch targets with intentional 36px compact desktop variants, visible focus everywhere, WCAG AA contrast, reduced motion, forced colors, no layout shift on theme switch. User requirements and the theme's identity beat generic skill advice (e.g. Aurora keeps its gradients).
Pliki w paczce (28)
- SKILL.md 9 KB
- version.json 1 KB
- bin/themewright.mjs 15 KB
- bin/verify.mjs 15 KB
- lib/checkpoint.mjs 3 KB
- lib/integrate.mjs 5 KB
- lib/integrations.mjs 3 KB
- lib/prefs.mjs 6 KB
- lib/registry.mjs 5 KB
- lib/scaffold.mjs 3 KB
- lib/scope.mjs 16 KB
- presets/creator.json 1 KB
- presets/defaults.json 1 KB
- references/adapters.md 3 KB
- references/integrations.md 2 KB
- references/preferences.md 2 KB
- references/quality-contract.md 4 KB
- references/verification.md 2 KB
- themes/aurora/spec.md 2 KB
- themes/aurora/theme.json 5 KB
- themes/glass/spec.md 3 KB
- themes/glass/theme.json 5 KB
- themes/liquid-metal/spec.md 2 KB
- themes/liquid-metal/theme.json 5 KB
- themes/neubrutalism/spec.md 5 KB
- themes/neubrutalism/theme.json 6 KB
- themes/soft-ui/spec.md 2 KB
- themes/soft-ui/theme.json 5 KB
Wersje
W bazie nie ma innych skilli o nazwie themewright.
Migawka bazy z 13.11.2026 · wersja paczki 61d6135b495d (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 90manage-themes
Tworzy, sprawdza i stosuje motywy wizualne workspace'u, pilnując kontrastu, harmonii palety i spójnego wyglądu materiałów. - 100theme-recipes
Dobiera i wdraża motyw wizualny, np. neumorfizm, szkło lub brutalizm, działający poprawnie w jasnym, ciemnym i dostępnym wariancie. - 100manage-themes
Tworzy, audytuje, ulepsza, wybiera i stosuje wizualne motywy projektowe z paczek Claude Design lub wbudowanych presetów, z audytem kontrastu, harmonii palety, doboru krojów i kompletności. - 95liquid-theme-a11y
Wdraża wzorce dostępności WCAG 2.2 w motywach Shopify Liquid: karty produktów, karuzele, koszyk, formularze i modale. - 100theme-factory
Stosuje gotowe motywy kolorów i czcionek do slajdów, dokumentów, raportów i stron HTML oraz tworzy nowe warianty wizualne. - 100create-theme
Tworzy własne motywy kolorystyczne dla Sidecar: wybór motywu bazowego, nadpisania kolorów, gradientowe obramowania, style kart, motywy per projekt i rejestracja programowa.