Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 11 additions & 5 deletions .agents/skills/beekeeper-suit/PAIRING-AUDIT.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,16 +4,22 @@ Ground truth pulled from the filesystem on 2026-08-14, after the repair pass. Th

## Totals

- Bees (`.claude/agents/*.md`): **75**
- Stinger folders (`.claude/skills/*`): **78**
- Bees (`.claude/agents/*.md`): **76**
- Stinger folders (`.claude/skills/*`): **79**
- Orchestrator-level skills with no paired Bee by design: **3** (`beekeeper-suit`, `queen-bee-stinger`, `get-started-stinger`)
- Pairable Stingers: **75**
- Pairable Stingers: **76**

## Pairing integrity

Clean. Every Bee has a matching Stinger and every pairable Stinger has a matching Bee, verified in both directions by naming convention. Zero orphans.

Every Bee also has a routing guide at `guides/<bee-name>.md`. 75 Bees, 75 guides, one-to-one.
Every Bee also has a routing guide at `guides/<bee-name>.md`. 76 Bees, 76 guides, one-to-one.

## New additions

`impeccable-worker-bee` / `impeccable-stinger` was ported in from a prior fork and registered here: it operates the Impeccable design system (pbakaus/impeccable, Apache-2.0) as the frontend-design operating system. The Impeccable engine is installed per machine via `npx impeccable install --scope=global --providers=codex,claude,cursor`; it is not vendored in this repo. The stinger's pre-flight sync check (`scripts/sync-check.mjs`) verifies the installed engine is current.

`impeccable-worker-bee` is the single router for frontend UI/UX/design implementation. `design-system-worker-bee` and `ux-ui-svelte-worker-bee` retain product-specific token, component-library, and accessibility enforcement on established systems.

## Path integrity

Expand Down Expand Up @@ -41,7 +47,7 @@ All routing references to the renamed `deeplake-dataset-worker-bee` were repaire

## Validation

All 78 Stingers pass `per-type-validation.py --type skill --harness all` with zero errors. All 75 Bees pass `--type agent --harness claude-code` with zero errors. Remaining warnings are repo-wide patterns, not defects: descriptions above Cowork's 200 character soft cap on some legacy skills, and the `proactive` frontmatter field, which every Bee in this colony uses.
All 79 Stingers pass `per-type-validation.py --type skill --harness all` with zero errors. All 76 Bees pass `--type agent --harness claude-code` with zero errors. Remaining warnings are repo-wide patterns, not defects: descriptions above Cowork's 200 character soft cap on some legacy skills, and the `proactive` frontmatter field, which every Bee in this colony uses.

## Dead reference repair

Expand Down
15 changes: 11 additions & 4 deletions .agents/skills/beekeeper-suit/SKILL.md
Original file line number Diff line number Diff line change
Expand Up @@ -28,7 +28,7 @@ Three skills sit above the pairing law because they are orchestrator level, not

## Roster

75 Bees registered, sorted into domain groups. The Domain column is a one-line summary of the Bee's own frontmatter description. Trigger keywords are pulled from that same description, not invented.
76 Bees registered, sorted into domain groups. The Domain column is a one-line summary of the Bee's own frontmatter description. Trigger keywords are pulled from that same description, not invented.

### Stack and frameworks

Expand All @@ -42,15 +42,16 @@ Three skills sit above the pairing law because they are orchestrator level, not
| `react-worker-bee` | React 18/19 architecture: bulletproof-react patterns, Server Components, Suspense, Actions, Compiler, state layering | "review React architecture", "state management decision", "Server Components boundary", "React 19 patterns" | `react-stinger` |
| `typescript-node-worker-bee` | TypeScript/Node code review and conventions: strict config, module resolution, test suites, boundary validation (body still cites a legacy package's specifics; see PAIRING-AUDIT.md) | "review this TypeScript code", "audit this Node code", "write a Vitest suite", "tighten the tsconfig" | `typescript-node-stinger` |
| `python-worker-bee` | Python architecture: Django + Django Ninja + FastAPI + Celery + Channels + pytest + uv, ORM discipline, migrations, typed adoption | "review this Django code", "audit ORM patterns", "migrate DRF to Django Ninja", "set up Celery" | `python-stinger` |
| `ux-ui-svelte-worker-bee` | Enforces this repo's SvelteKit UI standard: shadcn-svelte on Bits UI plus Melt UI, Tailwind v4 token bridge, white-label brand contract | "add a Button", "copy in this shadcn-svelte component", "convert this bespoke style to Tailwind", "does the white-label still work" | `ux-ui-svelte-stinger` |
| `ux-ui-svelte-worker-bee` | Enforces this repo's SvelteKit UI standard: shadcn-svelte on Bits UI plus Melt UI, Tailwind v4 token bridge, white-label brand contract. Impeccable remains the primary router for UI/design implementation | "add a Button", "copy in this shadcn-svelte component", "convert this bespoke style to Tailwind", "does the white-label still work" | `ux-ui-svelte-stinger` |
| `dark-mode-theming-worker-bee` | Dark-mode theming: CSS variable token architecture, theme-provider wiring, FOWT prevention, SSR hydration safety, Tailwind v4 dark variant | "set up dark mode", "dark mode on SSR", "multi-brand theming", "FOWT fix" | `dark-mode-theming-stinger` |
| `modal-toast-dialog-worker-bee` | Accessible overlay primitives: dialog, alert dialog, drawer, toast, command menu; focus trap, escape, scroll lock, aria contract | "choosing between overlay primitives", "debugging focus trap regressions", "building a command palette" | `modal-toast-dialog-stinger` |
| `icon-system-worker-bee` | Icon library selection and delivery: tree-shake vs sprite, dynamic-import-by-name, custom SVG components, icon accessibility contract | "choosing an icon library", "bundle-size regressions from icon imports", "icon accessibility" | `icon-system-stinger` |
| `typography-font-worker-bee` | Typography system: variable fonts, font source selection, the FOIT/FOUT/FOFT story, fluid type scales, type-token architecture | "set up fonts", "audit our typography", "fix FOIT/FOUT", "build a type scale" | `typography-font-stinger` |
| `font-loading-worker-bee` | Font loading pipeline: font-display strategy, preload/crossorigin correctness, variable-font subsetting, CLS-from-font-swap elimination | "audit font loading", "fix FOIT", "CLS from font swap", "subset variable font" | `font-loading-stinger` |
| `markdown-mdx-content-pipeline-worker-bee` | Markdown/MDX pipeline: compiler selection, remark/rehype chains, syntax highlighting, AST manipulation, XSS sanitization | "set up MDX", "configure Shiki", "write a remark plugin", "sanitize user markdown" | `markdown-mdx-content-pipeline-stinger` |
| `csv-xlsx-import-export-worker-bee` | Spreadsheet upload and export feature: CSV/XLSX parsing, large-file streaming, column-mapping wizard, row validation, CSV injection prevention | "build a CSV import", "add XLSX upload", "column-mapping wizard", "CSV injection safe" | `csv-xlsx-import-export-stinger` |
| `design-system-worker-bee` | Bootstraps a complete design system from scratch: tokens, utility layer, per-component and per-screen specs, static HTML examples | "build a design system for X", "bootstrap UI for product Y", "create tokens and utilities for this product" | `design-system-stinger` |
| `design-system-worker-bee` | Bootstraps a complete design system from scratch: tokens, utility layer, per-component and per-screen specs, static HTML examples. Impeccable owns frontend UI/UX/design implementation and uses DESIGN.md drift rules plus its detector gate to make enforcement mechanical | "build a design system for X", "bootstrap UI for product Y", "create tokens and utilities for this product" | `design-system-stinger` |
| `impeccable-worker-bee` | Frontend-design operating system for all UI/UX/design implementation, redesign, refinement, new surfaces, components, and design-system capture. Runs Start -> Iterate -> Polish -> Maintain, the context contract, and the deterministic detector gate | "polish the pricing page", "build a dashboard", "redo this hero", "make this not look like AI slop", "design a settings screen", "audit this UI" | `impeccable-stinger` |
| `http-rest-fundamentals-worker-bee` | HTTP/REST protocol correctness: method safety and idempotency, status-code honesty, headers, conditional and range requests | "is this status code correct", "why is CORS failing", "explain preflight", "PUT vs PATCH" | `http-rest-fundamentals-stinger` |
| `image-optimization-worker-bee` | Image delivery: AVIF/WebP format selection, responsive srcset/sizes, blur placeholders, remote image config, CLI tooling | "optimize my images", "convert to AVIF", "fix layout shift from images", "audit our images" | `image-optimization-stinger` |

Expand Down Expand Up @@ -208,6 +209,12 @@ Real sequences for this stack. Every sequence below closes with the Ship Gate; i
5. `seo-aeo-worker-bee` for metadata, JSON-LD, and Core Web Vitals.
6. Ship Gate.

### Frontend design / UI implementation

1. **`impeccable-worker-bee`** is the single router for all frontend UI/UX/design implementation, redesign, refinement, new-surface, component, and design-system-capture work. It runs Start -> Iterate -> Polish -> Maintain, including the pre-flight sync check and deterministic `npx impeccable detect <target>` gate.
2. **`design-system-worker-bee`** and **`ux-ui-svelte-worker-bee`** own product-specific token, component-library, and accessibility enforcement on established systems. Impeccable makes that enforcement mechanical via DESIGN.md drift rules and the detector gate.
3. **`security-worker-bee`** then **`quality-worker-bee`** close out under the Plan execution loop.

### Add auth

1. `workos-worker-bee` wires AuthKit, sessions, and SSO.
Expand Down Expand Up @@ -251,7 +258,7 @@ Don't hand-roll a new Bee. Walk [`../queen-bee-stinger/guides/beekeeper-registra

---

**75 Bees registered.** Every Bee has a spawnable agent in `.claude/agents/` and a paired Stinger in `../`. See [`PAIRING-AUDIT.md`](./PAIRING-AUDIT.md) for the full pairing audit, including the handful of Bees whose body content still needs a rewrite pass to match this repo's actual stack.
**76 Bees registered.** Every Bee has a spawnable agent in `.claude/agents/` and a paired Stinger in `../`. See [`PAIRING-AUDIT.md`](./PAIRING-AUDIT.md) for the full pairing audit, including the handful of Bees whose body content still needs a rewrite pass to match this repo's actual stack.

---

Expand Down
55 changes: 55 additions & 0 deletions .agents/skills/beekeeper-suit/guides/impeccable-worker-bee.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,55 @@
# impeccable-worker-bee

## Domain
This Bee is the frontend-design operating system operator. It owns the entire Impeccable system (pbakaus/impeccable, Apache-2.0) as a closed loop: the context contract (`PRODUCT.md` + `DESIGN.md` + per-surface briefs + `.impeccable/design.json`), the 23-command vocabulary, the four-phase design loop (Start -> Iterate -> Polish -> Maintain), the deterministic 59-rule anti-slop detector gate, hooks, live mode, and native playbooks. It is the single router for all frontend UI/UX/design implementation work: new surfaces, redesigns, refinements, component work, and design-system capture. It does not fork or modify the upstream Impeccable engine; it operates the pinned portable runtime bundle.

**Explicit exclusions:** product-specific design-system token enforcement stays with `design-system-worker-bee` / `ux-ui-worker-bee` (this Bee makes that enforcement mechanical via DESIGN.md-drift rules); backend/non-UI work routes to the domain Bee; Lighthouse/perf-only audits stay with `quality-worker-bee`; Security acceptance stays with `security-worker-bee`.

## Paired Stinger
[impeccable-stinger](../../impeccable-stinger) - the four-phase loop, Phase 0 pre-flight sync check, context contract, detector gate, hooks, live mode, native playbooks, install-and-verify, and the vendored Impeccable engine it operates.

## Trigger phrases
- "polish the pricing page"
- "build a dashboard"
- "redo this hero"
- "make this not look like AI slop"
- "design a settings screen"
- "audit this UI"
- "keep the design cohesive across new pages"

Or route proactively when the assigned work touches any frontend UI/UX/design implementation, redesign, refinement, new surface, component work, or design-system capture, or when the user wants to see the design live during development and point at issues before a PR.

## Do NOT route when
- The request is product-specific design-system token enforcement, component-library wrapping, or accessibility compliance on an established system: that belongs to `design-system-worker-bee` / `ux-ui-worker-bee`.
- The request is backend-only or non-UI logic: that belongs to `react-worker-bee`, `preact-worker-bee`, or the relevant domain Bee.
- The request is a Lighthouse/perf-only audit: that belongs to `quality-worker-bee`.
- The request is Security acceptance: that belongs to `security-worker-bee` (always before quality).

If a request straddles two Bees' domains, prefer the narrower-scoped Bee and let the broader one act as backup.

## Inputs the Bee needs
- The design task: a surface or route to design/redesign/refine, a plain-English request, or a named command intent.
- Repo root and target surface(s); the surface's mode (Persuade / Operate / Read / Experience) or enough context to infer it from the surface, not the product.
- Existing context files if present: `PRODUCT.md`, `DESIGN.md`, `.impeccable/design.json`, `.impeccable/surfaces/*.md`, `.impeccable/config.json`.
- Environment: Node >= 22.18; Impeccable installed per project (`npx impeccable install`) or `npx` network access; hooks approved in Codex (`/hooks`) where applicable.
- Optional: brand kit, anti-references, screenshots, incumbent visual truth (tokens, theme, CSS, components, assets).

## Outputs
- **Context contract files** - `PRODUCT.md`, `DESIGN.md` (Stitch format), `.impeccable/design.json`, `.impeccable/surfaces/*.md`, owned and kept current by this Bee.
- **Implemented UI** - source changes to the target surface(s), with the direction contract comment block (`THESIS / OWN-WORLD / STORY / FIRST VIEWPORT / FORM`) at the top of new artifacts.
- **Detector evidence** - a gate result (0 findings, or resolved findings, or explicit waivers with reasons) attached to the close-out.
- **Design-system updates** - `extract` / `document` outputs that keep the system current.
- **Close-out handoff** - security -> quality verification result, then a summary to the user with what changed and what remains open.

## Commonly sequenced with
- Plan execution loop: `impeccable-worker-bee` is the implementation Bee for frontend UI/UX/design work; it hands the final implemented state to `security-worker-bee`, reruns affected checks after security fixes, and only then hands it to `quality-worker-bee`.
- Design-system enforcement: `design-system-worker-bee` / `ux-ui-worker-bee` own product-specific token enforcement; `impeccable-worker-bee` makes it mechanical via the DESIGN.md-drift rules and the detector gate.

## Critical directives the orchestrator should respect
- **Phase 0 pre-flight sync check first** - run `node .claude/skills/impeccable-stinger/scripts/sync-check.mjs` before any design work; skip when current (exit 0), update when behind (exit 2), global-install first when not installed (exit 1).
- **Never self-grade** - the Bee iterates in bounded rounds; the user is the "happy" gate. A separate reviewer (army `quality-worker-bee` or a fresh reader) audits the build against its direction contract promise-by-promise.
- **The brief wins** - honor pinned aesthetics, eras, materials, fonts, and palettes even when they conflict with a saturated-pattern warning. Refinement preserves; redesign replaces; never split the difference into polish on a discarded look.
- **Single vocabulary** - never mix Impeccable with other design-taste skills in the same session; two design vocabularies collide and cancel each other out.
- **The gate is mandatory** - `npx impeccable detect <target>` runs before any completion claim; exit code 2 fails the close-out until findings are resolved or explicitly waived (narrowest ignore + reason).
- **Never fork or modify the engine** - call the installed system (`/impeccable`, `npx impeccable`); follow the bee-army-update contract (no upstream script execution during install, preserve the ownership manifest, no silent overwrites).
- **Close-out order** - Security before quality, always.
9 changes: 9 additions & 0 deletions .agents/skills/impeccable-stinger/README.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,9 @@
# impeccable-stinger

The paired Stinger for `impeccable-worker-bee`: the Bee Army's frontend-design operating system operator. It encodes the entire Impeccable system (pbakaus/impeccable, Apache-2.0) as a four-phase loop — **Start → Iterate → Polish → Maintain** — with the deterministic 59-rule anti-slop detector gate as a mandatory close-out step.

- Command Brief: `.claude/commands/impeccable-worker-bee-command-brief.md`
- Research: `research/research-summary.md` (repo-primary, commit `aee6ce9`, 2026-08-04)
- License: Apache-2.0 (upstream); this stinger is guidance + procedure, never vendored engine code.

- Bee: `.claude/agents/impeccable-worker-bee.md` (agent file: `.claude/agents/impeccable-worker-bee.toml`)
Loading