pandacss-optimizer
/pandacss-optimizer
Audytuje użycie Panda CSS w projekcie, mierzy koszt generowanego CSS i przygotowuje plan poprawek do zatwierdzenia przed zmianami w kodzie.
- Autor
- RuneStone-Tech ↗
- Repozytorium
- optimize-anything ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 04.11.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 8
- Skrypty
- 1
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 1
Brak sygnałów. Repozytorium zmienione 04.11.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
- 1 skrypt w paczce. Przejrzyj je przed instalacją, bo Claude może je uruchomić.
Skrypty: scripts/audit.py
Co robi i kiedy
Audytuje użycie Panda CSS w projekcie, mierzy koszt generowanego CSS i przygotowuje plan poprawek do zatwierdzenia przed zmianami w kodzie.
Wyzwalacze z opisu
Oryginalny opis (EN)
Audit and optimize Panda CSS 2.5 usage for missing presets, panda.config and styled-system codegen drift, broad static CSS, runtime css() calls, recipe/token consistency, source transforms, CSS layers, design-system packages and v1-to-v2 migration, with real before/after measurement. Always produces a written findings report and a fix plan for approval before touching code. Use this whenever the user mentions Panda CSS, @pandacss/dev, panda.config, styled-system, Panda recipes/tokens, or "optimize my Panda CSS" -- even if they never say audit or optimize.
Jak działa
- Workflow
- Principles
- Docs
Podgląd SKILL.md
--- name: pandacss-optimizer description: Audit and optimize Panda CSS 2.5 usage for missing presets, panda.config and styled-system codegen drift, broad static CSS, runtime css() calls, recipe/token consistency, source transforms, CSS layers, design-system packages and v1-to-v2 migration, with real before/after measurement. Always produces a written findings report and a fix plan for approval before touching code. Use this whenever the user mentions Panda CSS, @pandacss/dev, panda.config, styled-system, Panda recipes/tokens, or "optimize my Panda CSS" -- even if they never say audit or optimize. --- # Panda CSS Optimizer Panda CSS 2 compiles a Rust engine to atomic CSS at build time. Cost is generated `styled-system` size, broad `staticCss`, runtime `css()` on dense pages, and config/preset drift in v2. Optimize extraction, recipes and layers rather than runtime CSS. ## Workflow ### 1. Scope (quick) - Find the app root and detect Panda CSS usage: `@pandacss/dev 2.x`. Record the version, framework (React/Next/Vue/Svelte/Solid/Angular or HTML), styling system, and whether the library is a package, a CSS-only kit, or copied source. - Run `python <skill-dir>/scripts/audit.py <project-root>` -- static scan of `package.json`, config/CSS files and source for version drift, missing presets, codegen/styled-system drift, broad static CSS, runtime css() calls and v1-to-v2 migration, with file:line evidence. Use `--json` to post-process. - Classify the pain: bundle/import cost, runtime/re-render cost, theming/SSR style flash, accessibility/forms, large tables/lists, or migration/upgrade. Ask which hurts if unclear. - Read `references/tooling.md` once: what can be measured here. - Check `panda.config`, the `styled-system` output, presets (`@pandacss/preset-base`/`preset-panda` are required in v2), and whether source transforms are enabled. ### 2. Audit The script finds cheap leads; you find the rest by reading. Read the install/config, the global CSS/theme file, the provider or plugin setup, and the 3-5 most-used components. Load only what applies: | Area | Reference | |------|-----------| | Install, config, provider/plugin, theming, SSR | `references/setup.md` | | Bundle/imports, runtime, a11y/forms, tables, upgrades | `references/optimizations.md` | | Measurement and honest reporting | `references/tooling.md` | **Measure, never guess.** Build for production and measure the real route/bundle. Inspect SSR HTML for style tags and dark-mode flash; run axe/Playwright on dialogs, menus, forms and tables. Component count, bundle bytes and a11y violations are evidence; "feels heavy" is not. Mark each finding **Confirmed** (build/analyzer/axe/code evidence) or **Suspected** (needs measuring). ### 3. Report Fill `assets/report-template.md`, save it as `PANDA_CSS_OPTIMIZATION_REPORT.md` in the project root, and show the user. Five-line summary, findings table by impact/effort, then per-finding detail (evidence, why it hurts, fix, risk, visual/behavior impact). Group near-duplicates. ### 4. Plan -- then stop for approval Use plan mode: `EnterPlanMode` (load with ToolSearch if deferred), write the plan, present with `ExitPlanMode`; if unavailable show it in chat and wait for an explicit "go". Structure: 1. **Quick wins** -- trim imports, use path imports, add provider/plugin correctly, add missing labels/titles, move heavy components off the initial route, remove per-row overlays, align theme tokens, add SSR style/cache setup. Low risk. 2. **Structural** -- split component boundaries, virtualize tables, lazy-load heavy widgets, consolidate theming, migrate variants/tokens, fix form composition, deduplicate copied components. Name each behavior change. 3. **Heavy** -- major upgrade, primitive-base change, CSS-only to styled kit (or reverse), Tailwind 3 to 4, copy-in registry extraction, SSR architecture. Separately approved. Each step: files touched, expected effect, how to verify, how to roll back. ### 5. Fix Only approved items, in small groups. After each: typecheck, lint, tests, production build, and a visual/axe check on affected components. A break must trace to one change. Do not mix a major migration with optimization edits. If a change alters a public component API, theme tokens or SSR behavior, stop and ask. ### 6. Verify and wrap up Re-measure the same routes/components: route JS/CSS, SSR styles/theme, axe violations, dialog/form keyboard flow, table interaction. State plainly what could not be measured. End with deferred items and one suggested next step. ## Principles - **Extraction is the product.** Keep usage static. - **Presets are required in v2.** - **Codegen is part of the build.** ## Docs - https://panda-css.com/docs/overview
Pliki w paczce (8)
- LICENSE 1 KB
- README.md 1 KB
- SKILL.md 5 KB
- assets/report-template.md 1 KB
- references/optimizations.md 1 KB
- references/setup.md 1 KB
- references/tooling.md 1 KB
- scripts/audit.py 10 KB
Wersje
W bazie nie ma innych skilli o nazwie pandacss-optimizer.
Migawka bazy z 13.11.2026 · wersja paczki 357be896c015 (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
- 85park-ui-optimizer
Audytuje użycie Park UI w projekcie, mierzy koszt importów i renderowania oraz przygotowuje plan poprawek do zatwierdzenia przed zmianami w kodzie. - 100migrate-styled-components-to-panda-css
Prowadzi krok po kroku migrację komponentów w monorepo Sanity ze styled-components do Panda CSS, w tym pliki .css.ts, specyficzność względem @sanity/ui i stylowanie elementów potomnych. - 85tailwindcss-optimizer
Audytuje użycie Tailwind CSS 4.3: konfigurację w CSS, motywy, dynamiczne nazwy klas, dark mode i migrację z v3, z pomiarami przed i po. - 90panda-plan
Tworzy plan implementacji na podstawie wymagań i istniejącego kodu: uporządkowane zadania, zależności, kryteria akceptacji, ryzyka i weryfikację. - 100devup-ui
Pomaga wdrożyć bibliotekę Devup UI, czyli CSS-in-JS bez narzutu w runtime, z konfiguracją motywu i migracją ze styled-components. - 100panda-simplify
Ocenia zbędną złożoność w kodzie, architekturze, dokumentacji i przepływach agentów, gdy trzeba mniej warstw i czytelniejszy podział zadań.