Add impeccable-worker-bee and impeccable-stinger to the Bee Army roster - #10
Open
chrisl10 wants to merge 1 commit into
Open
Add impeccable-worker-bee and impeccable-stinger to the Bee Army roster#10chrisl10 wants to merge 1 commit into
chrisl10 wants to merge 1 commit into
Conversation
Port the Impeccable frontend-design operating system (pbakaus/impeccable, Apache-2.0) as a Bee/Stinger pair. Impeccable is the single router for frontend UI/UX/design implementation; design-system-worker-bee and ux-ui-svelte-worker-bee retain product-specific enforcement. The Impeccable engine is installed per machine via 'npx impeccable install --scope=global --providers=codex,claude,cursor' and is not vendored here. The stinger's pre-flight sync check (scripts/sync-check.mjs) verifies the installed engine is current. Regenerates the .agents, .codex, and .cursor harness mirrors and updates the beekeeper-suit roster and pairing audit.
|
Important Review skippedToo many files! This PR contains 179 files, which is 79 over the limit of 100. To get a review, reduce the PR to 100 files or fewer by splitting it into smaller PRs or changing its base branch. Upgrade to a paid plan to raise the limit. This review is too large to run within your organization's remaining usage spending cap. Raise or remove your spending cap in the billing tab, then retry. ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (179)
You can disable this status message by setting the Warning Billing warning: we have not been able to collect payment for this subscription for more than 72 hours. Please update the payment method or pay any pending invoices in Billing to avoid service interruption. Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds the impeccable-worker-bee (the Bee Army's frontend-design operating system operator) and its paired impeccable-stinger to the Bee Army roster, mirrored across the Codex (
.agents), Claude (.claude), and Cursor (.cursor) harnesses.What this Bee does
impeccable-worker-beeis the single router for frontend UI/UX/design implementation, redesign, refinement, new surfaces, component work, and design-system capture. It operates the entire Impeccable design system (pbakaus/impeccable, Apache-2.0) as a four-phase loop:PRODUCT.md+DESIGN.md+ surface briefs), job classification, new-work direction contract, visualization.polish,bolder,quieter,distill,typeset,layout,colorize,animate,delight,overdrive,clarify,adapt,optimize,harden,onboard).audit,clarify,harden) plus the mandatory deterministic 59-rule anti-slop detector gate (npx impeccable detect <target>).extract,document, anddoctor.Routing change: impeccable-worker-bee is now the preferred frontend-design router
This PR updates the beekeeper-suit roster and routing so that
impeccable-worker-beeis the primary router for all frontend UI/UX/design implementation work — the workflow now routes UI/design tasks to it first. The Bees that previously handled frontend UI/UX/design implementation are demoted to product-specific enforcement on established systems, not removed:ux-ui-svelte-worker-bee— now scoped to product-specific SvelteKit token/component-library/accessibility enforcement. Roster note updated: "Impeccable remains the primary router for UI/design implementation."design-system-worker-bee— now scoped to bootstrapping design systems and product-specific token enforcement. Roster note updated: "Impeccable owns frontend UI/UX/design implementation and uses DESIGN.md drift rules plus its detector gate to make enforcement mechanical."A new "Frontend design / UI implementation" sequence in the beekeeper-suit
SKILL.mdmakes the order explicit:impeccable-worker-bee— single router for all frontend UI/UX/design implementation, redesign, refinement, new-surface, component, and design-system-capture work (Start → Iterate → Polish → Maintain, including the pre-flight sync check and deterministicnpx impeccable detect <target>gate).design-system-worker-beeandux-ui-svelte-worker-bee— product-specific token, component-library, and accessibility enforcement on established systems.security-worker-beethenquality-worker-bee— close out under the Plan execution loop.The same routing is reflected in
PAIRING-AUDIT.md: "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."Important: external CLI dependency (not vendored)
This stinger does not vendor the Impeccable engine. It is guidance + procedure that operates an engine installed per machine:
npx impeccable install --scope=global --providers=codex,claude,cursor/impeccablecommands,npx impeccableCLI, per-project hooks) and enforces its gate.scripts/sync-check.mjs) verifies the installed engine is current before any design work; it exits0(in sync),1(not installed → install first), or2(behind upstream →npx impeccable updateand refresh the stinger's guides/templates +scripts/upstream-manifest.json).What's included
impeccable-worker-beeregistered in the beekeeper-suit roster and pairing audit, with a routing guide.impeccable-stinger/with guides (00–11), worked examples (01–04), templates (direction contract, gate report, surface brief, sync report), research notes, the sync-check script, andupstream-manifest.json.Verification
.agents/.claude/.cursormirrors are consistent; internal stinger links resolve.main.