bootstrap-optimizer
/bootstrap-optimizer
Audytuje i optymalizuje użycie Bootstrap 5.3: pełne importy CSS i JS, duplikację zmiennych Sass, inicjalizację wtyczek, tryb ciemny i migrację do v6.
- 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 i optymalizuje użycie Bootstrap 5.3: pełne importy CSS i JS, duplikację zmiennych Sass, inicjalizację wtyczek, tryb ciemny i migrację do v6.
Wyzwalacze z opisu
Oryginalny opis (EN)
Audit and optimize Bootstrap 5.3 usage (Bootstrap 6 is alpha only) for full CSS/JS imports, Sass variable duplication, data-bs plugin initialization, CSS variables/dark mode, RTL, bundle size, framework conflicts and the v5-to-v6 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 Bootstrap, bootstrap.scss, data-bs-*, Bootstrap modal/dropdown, Bootstrap 6, or "optimize my Bootstrap UI" -- even if they never say audit or optimize.
Jak działa
- Workflow
- Principles
- Docs
Podgląd SKILL.md
--- name: bootstrap-optimizer description: Audit and optimize Bootstrap 5.3 usage (Bootstrap 6 is alpha only) for full CSS/JS imports, Sass variable duplication, data-bs plugin initialization, CSS variables/dark mode, RTL, bundle size, framework conflicts and the v5-to-v6 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 Bootstrap, bootstrap.scss, data-bs-*, Bootstrap modal/dropdown, Bootstrap 6, or "optimize my Bootstrap UI" -- even if they never say audit or optimize. --- # Bootstrap Optimizer Bootstrap 5.3 is a CSS framework plus small JS plugins. The cost is the full CSS/JS bundle, custom Sass duplication and plugin initialization; Bootstrap 6 is an alpha and not the production target. Optimize imports, Sass variables and which plugins load per page. ## Workflow ### 1. Scope (quick) - Find the app root and detect Bootstrap usage: `Bootstrap 5.3.8 (6 alpha)`. 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, full CSS/JS imports, Sass variable duplication, uninitialized data-bs plugins, dark-mode flash, framework conflicts and v6 migration risk, 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 how Bootstrap is imported (full CSS vs Sass modules), whether the JS bundle is global, and whether a second CSS framework is fighting its reset. ### 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 `BOOTSTRAP_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 - **One CSS framework.** Resets fight. - **Import modules, not the bundle.** - **Plugins are per page.** Initialize what exists. ## Docs - https://getbootstrap.com/docs/5.3/getting-started/introduction/
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 bootstrap-optimizer.
Migawka bazy z 13.11.2026 · wersja paczki 1148783a7792 (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
- 85sass-scss-optimizer
Audytuje i optymalizuje Sass i SCSS: migrację z @import do @use, przestarzałe funkcje kolorów, rozmiar wyjścia i map źródłowych, z pomiarami. - 100bootstrap-vite
Włącza CSS i JavaScript Bootstrap 6 do projektu w Vite, bundlując Sass i JS przez Vite. - 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. - 100bootstrap-color-system
Obsługuje system kolorów Bootstrap 6 w Sass i CSS: skale kolorów, tokeny semantyczne i tryby motywu przy zmianie barw. - 100css-modules-and-sass
Utrzymuje zakresowe style komponentów, miksiny Sass, zagnieżdżone reguły i zmienne w CSS Modules i Sass/SCSS. - 90fe-sass
Pisze i przegląda kod Sass dla Dart Sass, z systemem modułów @use i @forward, i wskazuje, kiedy wystarczy zwykły CSS.