that-git-life

Architecture Decision Records specialist covering Nygard format (Context / Decision / Consequences), MADR extended template, Y-statement framing, supersession and deprecation lifecycle, Log4brains and adr-tools CLI integration, and the "decisions, not docs" philosophy. Use when authoring a new ADR, superseding an existing decision, auditing the ADR log, setting up Log4brains, or onboarding a team to ADR practice. Do NOT use for general knowledge-base authoring (library-worker-bee), code entity extraction (wiki-worker-bee), or security review of the decisions themselves (security-worker-bee).

Affiliate and referral program specialist for SaaS products -- platform selection (Rewardful, FirstPromoter, Tolt, PartnerStack, Impact, Refersion), the affiliate-vs-referral distinction, cookie-based and server-side attribution (post-ITP, post-3PC era), payout automation, fraud detection (self-referral, cookie stuffing, velocity fraud), and EPC/LTV program economics. Invoke when the user says "set up an affiliate program", "which affiliate platform should I use", "Rewardful vs FirstPromoter", "my attribution is broken in Safari", "referral program fraud", "EPC or LTV for our program", "20% recurring commission", "postback tracking setup", or "PartnerStack vs FirstPromoter". Do NOT invoke for Stripe subscription billing mechanics (payments-worker-bee), API key secret management (security-worker-bee), custom attribution DB schema (db-worker-bee), or outbound partner recruitment campaigns (cold-outreach-worker-bee).

Scrum methodology specialist — sprints, ceremonies (Sprint Planning, Daily Scrum, Sprint Review, Retrospective, Backlog Refinement), roles (Scrum Master, PO, Developers), estimation (Fibonacci, Planning Poker,

The vibe-coder's AI coding tool advisor — Cursor, Claude Code, Aider, Cline, Windsurf/Cascade, Continue.dev, Replit Agent, Devin, and Bolt. Covers tool-tier classification, selection rubric (autonomy, context, budget, language), SWE-bench benchmark data, model-routing patterns (including Aider's 3-5x cost-reducing architect/editor split), per-tool prompt and context discipline, and a documented footgun catalog. Use when the user says "which AI coding tool should I use", "Cursor vs Claude Code vs Aider", "set up Aider", "Cline keeps breaking", "is Devin worth it", "which tool for autonomous tasks", "how do I reduce AI coding costs", "prompt discipline for Aider/Claude Code/Cline", or any question comparing or configuring AI-assisted development tools. Cross-links to cursor-ide-worker-bee for deep Cursor IDE config and ai-tools-platform-worker-bee for LLM provider/gateway decisions. Do NOT use for Cursor IDE configuration (cursor-ide-worker-bee owns that), CI/CD pipelines that run agents (devops-worker-bee), or

The vibe coder's AI toolbox — AI gateways (Portkey, OpenRouter), cloud providers (Bedrock, Vertex AI), frontier model selection (Claude, GPT, Gemini), cheap-fallback routes (Haiku, Mini, Flash), local LLMs (Ollama, LM Studio), GPU cloud (Runpod, Modal, Together, Fireworks), and must-have MCPs and IDE plugins. Use when the user says "which AI provider should I use", "set up Portkey", "Ollama for local dev", "Runpod vs Modal", "which MCP servers do I need", or asks to optimize AI spend. Do NOT use for cognitive-layer architecture (mind-worker-bee), API key security (security-worker-bee), or PRD authorship (library-worker-bee).

Paid acquisition specialist for alternative ad platforms beyond Meta and Google Search — LinkedIn Ads (B2B), TikTok Ads + CAPI, Reddit Ads, Microsoft/Bing Ads with LinkedIn Profile Targeting, Pinterest Ads, Quora Ads, YouTube standalone video, Spotify Ad Studio + podcast advertising, and the channel-fit-by-ICP heuristic that selects among them. Invoke when the user says "which ad platform should I use besides Meta/Google", "set up LinkedIn Ads for B2B SaaS", "TikTok CAPI setup", "Reddit Ads for technical buyers", "Microsoft Ads LinkedIn targeting", "podcast advertising Spotify Ad Studio", "channel diversification paid acquisition", or "our CPL on Meta is too high, what else should we try". Do NOT invoke for Meta/Facebook/Instagram Ads (no peer Bee — handle inline), Google Search Ads (no peer Bee — handle inline), or organic social strategy (route to social-media-marketing-organic-worker-bee).

API documentation authority — Swagger UI / Redoc / Scalar / Mintlify / Stoplight / Bump.sh tool selection, OpenAPI spec enrichment with JSON examples, self-hosted and managed hosting, SDK generation (TypeScript / Python / Go via openapi-generator-cli and Fern/Speakeasy), and changelog discipline. Invoke when the user says "set up API docs", "which docs renderer should I use", "generate an SDK from my spec", "deploy my OpenAPI docs", "write an API changelog", "compare Redoc vs Scalar", or "publish API reference to GitHub Pages". Do NOT invoke for general documentation sites (library-worker-bee), API security scheme audits (security-worker-bee), or backend route design (python-worker-bee / react-worker-bee).

App store submission specialist for iOS (App Store Connect + TestFlight) and Android (Google Play Console). Covers App Store Optimization (keywords, screenshots, preview assets), submission workflow, privacy compliance (Apple nutrition labels, PrivacyInfo.xcprivacy, Google data safety forms), rejection diagnosis and remediation, age rating questionnaires, In-App Purchase setup (StoreKit 2, Google Play Billing Library), and realistic timeline expectations. Invoke when the user says "submit my app", "App Store rejection", "ASO strategy", "privacy nutrition label", "set up IAP", "Google Play review", "expedited review", or when preparing any mobile app for store publication. Do NOT invoke for UI design of the app itself (ux-ui-worker-bee), client-side StoreKit / billing implementation code (react-worker-bee / python-worker-bee), or app security audits (security-worker-bee).

Equips asset-worker-bee with the Universal Asset Registry — the 19-asset taxonomy (Features, Pages, Routes, Surfaces, Controls, Displays, Layouts, NavEntries, DesignTokens, Icons, MediaAssets, Fonts, Motion, Breakpoints, ContentEntries, Translations, FeatureFlagBindings, MeterBindings, Entitlements), the registration workflow, the code-vs-DB drift audit, the sync-generator contract, the deprecation/sunset rules, and the canonical Prisma + SQL schema. Use when registering, auditing, deprecating, or generating sync code for any of the 19 asset types, when checking for drift between code and the registry, or when standing up the registry in a new repo. Not for QA report authorship (use quality-stinger), PRD numbering (use library-stinger), UX design decisions (use ux-ui-stinger), or security audits of the registry tables (use security-stinger).

Implements end-to-end authentication — provider selection (Clerk / Better Auth / Auth.js / Supabase Auth / WorkOS / Stack Auth / Kinde / Stytch), Google OAuth flows including the October 2025 unused-client-deletion policy and GIS migration, MFA / passkeys, RBAC, session storage, and B2B SSO. Use when the user says "set up auth", "pick an auth provider", "wire up Google sign-in", "Google OAuth verification", "set up MFA / passkeys", "RBAC for multi-tenant", "migrate from NextAuth to Better Auth / Clerk", or when `auth-worker-bee` is invoked. Do NOT use for security audits of the resulting implementation (security-worker-bee), the React `<SignIn />` UI (react-worker-bee), the user / session schema (db-worker-bee), or the auth PRD (library-worker-bee).

Phase 3 of the Legion AI Tools Factory pipeline. Authors the Cursor IDE subagent (Bee) file from a completed Command Brief and forged Stinger. Writes the YAML frontmatter, composes the body with proper Read-references to every file in the paired Stinger folder, wires the Bee to its guardrails and escalation paths, and declares a proactive/on-demand trigger policy. Use this skill whenever the user asks to "create the Bee", "author the subagent", "build the subagent file", "wire up the Bee", "finish the Bee", or signals that the Stinger is forged and it is time to assemble the subagent. Also trigger when stinger-forge has just announced its handoff or when the user points to a ready-to-use stinger folder and asks for its Bee.

Routing skill for the Cursor IDE Army. When the user makes a request, consult this skill to decide which Bee (subagent) owns the task and should be invoked. Each registered Bee has a guide in `guides/` describing its domain, trigger phrases, required inputs, outputs, and the situations in which it should NOT be invoked. Trigger this skill when the user's request looks like it might match a Bee's domain, when multiple Bees could plausibly handle the work, or when the user asks "who handles X?" / "which Bee does Y?".

Editorial blogging strategy specialist — cluster + pillar topical authority architecture, post length by search intent, title + H1 + meta description craft, keyword research scoping without obsession, AEO/answer-engine formatting (featured snippets, AI Overviews, chatbot citations), CTA copy that converts without begging, the canonical 12-point pre-publish review checklist, and realistic publishing-cadence planning for small teams. Use when the user says "map our blog content", "what should we write about", "review this post before publishing", "set a realistic blog cadence", "optimize this title or meta", "format this post for AI Overviews", "write a better CTA", or when `blogging-content-strategy-worker-bee` is invoked. Do NOT use for technical SEO implementation (schema markup, sitemap, robots.txt — route to `seo-aeo-worker-bee`), CMS setup (route to `website-worker-bee`), analytics dashboards, or social media distribution.

Branching strategy advisor for Git-based teams. Owns model selection (trunk-based development, GitHub Flow, GitFlow), release and hotfix branch patterns, the merge-vs-rebase argument, the long-lived-branch trap, and the feature-flag vs feature-branch decision. Use when the user says "which branching model should we use", "we have too many merge conflicts", "our release process is broken", "GitFlow or trunk-based?", "merge or rebase?", "should I use a feature flag or a branch?", "set up GitHub Merge Queue", or when `branching-strategy-worker-bee` is invoked. Do NOT use for Git mechanics (interactive rebase, conflict resolution, history rewriting - that is `git-worker-bee`), branch protection ruleset configuration (that is `github-repo-health-worker-bee`), or CI/CD pipeline topology (that is `ci-release-worker-bee`).

Writes the CHANGELOG.md and release notes for the @deeplake/hivemind npm package and CLI. Use when the user says "write the changelog entry", "what version bump is this", "draft the release notes", "is this a breaking change", "we just shipped X", or when a release is about to cut and the change needs to be communicated to developers who install via npm and to the six-harness users. Covers Keep-a-Changelog format for a CLI/library, semver discipline (what is patch vs minor vs breaking for an agent-memory tool plus its harness contracts, MCP tool surface, and Deep Lake schema), release-note copy craft (impact-first, honest scope), the sync-versions + release.yaml mechanics, and announcing across GitHub Releases, README, and the Slack community. Do NOT use for managing the build/release pipeline itself (ci-release-worker-bee) or marketing launch campaigns (out of scope for this Army).

Designs, audits, and authors Hivemind's build / CI / npm-release pipeline - the esbuild multi-harness bundle, sync-versions single-sourcing, the tsc+vitest+jscpd quality gate, the GitHub Actions workflow architecture, the Node version matrix + cross-node-install smoke, npm publish discipline (files allowlist, prepack, pack-check secret-scan), and native-dep healing (ensure-tree-sitter). Use when the user says "review our build", "the bundle is wrong", "design our CI", "audit our workflows", "the version is out of sync", "add a CI job", "we leaked a secret on publish", "the npm pack is shipping junk", "tree-sitter broke on install", or when `ci-release-worker-bee` is invoked. Do NOT use for runtime TS/Node code design (typescript-node-worker-bee), Deeplake dataset/retrieval logic (deeplake-dataset / retrieval Bees), security CVE deep audits (security-worker-bee - ci-release-stinger surfaces concerns and hands off), changelog/release-notes prose (changelog-release-notes-worker-bee - this Bee owns the mechanics

Forensic investigation methodology for software-development and agency-services engagements where a client has been overcharged, defrauded, or materially injured by a vendor and possesses a paper trail (invoices, emails, git repo, audit reports). Produces an 11-deliverable evidence packet — master forensic report, agency-services subreport, attorney legal memo, plain-language client report, 51-tab invoice spreadsheet, and a 6-document pre-litigation pack. Trigger whenever the user describes the pattern of paid $100k+ for a half-working product, monthly maintenance retainer with little or no git activity, hosting double-billing, virtual-assistant or social-media charges without delivery, or any sibling pattern. Defendant-agnostic — see defendant-profile-template for plugging in case-specific corporate context. Calibrated against the Example Booking Co. matter ($202K documented spend, $183K-$381K damages range).

Code review culture and PR lifecycle specialist -- PR description templates (six-element structure), review checklists (three-tier taxonomy: blocker/suggestion/nit), async-first review norms for remote teams, the small-PR discipline (400-line threshold backed by DORA 2025 data), rubber-stamp anti-pattern detection, and the review-as-mentorship lens. Use when the user says "audit our PR culture", "write a PR description", "create a review checklist", "coach this review comment", "is this PR too large?", "how do we improve code review on our team?", or when code-review-pr-worker-bee is invoked. Do NOT use for security audit findings (security-worker-bee), implementation correctness (typescript-node-worker-bee), CI/CD pipeline setup (ci-release-worker-bee), or branch protection configuration (github-repo-health-worker-bee).

Outbound sales specialist for founders running cold email. Covers Apollo / Clay / Smartlead / Instantly / Lemlist tool selection, email deliverability and domain warmup, multi-touch sequence design (3-5 steps), AI personalization without slop (Clay Claygent SKIP rule), reply classification and disqualification, and list hygiene. Use when the user says "set up cold outreach", "my cold email is landing in spam", "write a cold email sequence", "set up Clay personalization", "Apollo vs Instantly", "my reply rate is below 2%", "cold email warmup", "build a list in Apollo", or when cold-outreach-worker-bee is invoked. Do NOT use for inbound SDR workflows, CRM architecture (db-worker-bee), AE discovery call scripts, paid acquisition, or LinkedIn content strategy.

Phase 1 of the Legion AI Tools Factory pipeline. Names a new Cursor IDE Bee (subagent) and its Stinger (skill) from the user's requested topic, copies the Command Brief template into the ai-tools command-briefs folder, populates the brief's YAML frontmatter (research_depth and model triplet, sourced from the backlog entry when one exists), and conversationally interviews the user to fill in every section. Use this skill whenever the user asks to "create a new Bee", "create a new subagent", "start a new Bee", "begin an Bee", "forge an Bee", "add a worker-bee", "start a Command Brief", "brief a new agent", "I want a subagent that does X", or any request that kicks off a fresh Bee/Stinger pair. Also trigger when the user names a topic area (security, UX, SEO, observability, etc.) and wants a dedicated agent for it. This is the first skill in the pipeline -- it MUST run before scripture-historian, stinger-forge, or bee-creator.

CRM connectivity specialist for HubSpot, Salesforce, Pipedrive, Attio, Folk, Close, and Copper -- bi-directional sync design, the contact-vs-lead-vs-account taxonomy, merge/dedupe, and the native-vs-Zapier-vs-Merge.dev architecture trade-off. Use when the user says "integrate with HubSpot", "bi-directional CRM sync", "CRM field mapping", "Merge.dev or native API?", "dedup contacts in our CRM", "lead enrichment strategy", "sync conflict resolution", "Salesforce Lead vs Contact", "Attio API production-ready?", or "audit our CRM sync code". Do NOT use for cold email sequence design (cold-outreach-worker-bee), product database schema (db-worker-bee), sync implementation code (python-worker-bee), or frontend CRM widgets (react-worker-bee).

Scheduled-job specialist for cron expression authoring, platform-specific limits (Vercel Cron, Cloudflare Cron Triggers, GitHub Actions schedule), distributed-cron correctness (exactly-once execution, leader election, idempotency), timezone and DST safety, retry-on-failure patterns, and the "did the cron run?" observability loop (Healthchecks.io, Cronitor, self-hosted heartbeat tables). Use when the user says "write a cron expression", "set up Vercel Cron", "my cron job runs twice", "GitHub Actions schedule is drifting", "add monitoring for my scheduled job", "cron and DST issue", "distributed cron", or when `cron-scheduling-worker-bee` is invoked.

The "upload your spreadsheet" implementation arsenal for React/Next.js products. Covers library selection (papaparse, SheetJS, exceljs), streaming-parse for 100MB+ files, the column-mapping UX wizard, managed importers (OneSchema, Flatfile, dromo) vs self-hosted (react-spreadsheet-import), Zod row validation, CSV injection prevention, encoding edge cases, and styled XLSX export. Use when the user says "build a CSV import", "add XLSX upload", "spreadsheet import feature", "column-mapping wizard", "export to Excel", "streaming parse large file", "CSV injection safety", or when csv-xlsx-import-export-worker-bee is invoked. Do NOT use for file drop-zone UI (ux-ui-worker-bee), database bulk-insert tuning (db-worker-bee), or upload endpoint security audit (security-worker-bee).

Equips cursor-ide-worker-bee to own Hivemind's Cursor surface: the Cursor 1.7+ hooks harness (~/.cursor/hooks.json, 6 lifecycle events) wired by src/cli/install-cursor.ts, the first-party VS Code/Cursor extension at harnesses/cursor/extension/, registering the Hivemind MCP server (src/mcp/server.ts) in Cursor, and the .cursor/ Bee Army platform this repo ships (rules .mdc format, agents, skills/Stingers, the-beekeeper/the-smoker commands, model-comparison-matrix). Use when the task touches Cursor hook wiring, .cursor/rules/*.mdc authoring, MCP registration in Cursor, the cursor extension build, or the Army's .cursor/ structure. Do NOT use for code quality of TS source (typescript-node-worker-bee), the MCP protocol internals of server.ts (mcp-protocol-worker-bee), or harness wiring for Claude/Codex/other agents (harness-integration-worker-bee).

Support stack specialist for SaaS products — selects the right tool from Plain, Pylon, Front, Help Scout, and Intercom; configures shared inboxes; designs AI-deflection flows (Fin 2.0, Ari, Crisp Bot); sets SLA tiers; wires integrations to Slack, Linear, and Notion; and provides a founder-as-support playbook for teams of 1-3. Invoke when choosing a support tool, auditing an existing stack, configuring AI deflection, designing SLA policy, or setting up escalation to Linear. Do NOT invoke for chat widget installation code (live-chat-support-worker-bee), auth SSO (auth-worker-bee), or GDPR/retention audits (security-worker-bee).

Audits and implements the full dark-mode theming surface for React/Next.js applications — CSS variable token architecture (semantic vs. primitive), next-themes wiring (ThemeProvider, storageKey, enableSystem), FOWT (flash-of-wrong-theme) prevention via blocking inline script, SSR hydration safety (suppressHydrationWarning, typeof window guards, mounted guard pattern), Tailwind v4 dark-mode configuration (@custom-variant, selector strategy), and multi-brand/white-label runtime theme swapping via CSS variable overrides. Use when the user says "set up dark mode", "next-themes keeps flashing", "dark mode on SSR", "multi-brand theming", "CSS variable token layer", "Tailwind v4 dark mode", "prefers-color-scheme in Next.js", "white-label theme runtime swap", or when dark-mode-theming-worker-bee is invoked. Do NOT use for palette creation or source-of-truth token file authorship (design-system-worker-bee), per-component visual deltas (ux-ui-worker-bee), or persisted-preference schema design (db-worker-bee).

Designs, reviews, and migrates PostgreSQL data layers — schema, indexing, zero-downtime migrations, performance, ORM choice, and serverless DB platform selection. Use when the user says "design this schema", "review this migration", "is this index right?", "should this be jsonb or columns?", "we need a NOT NULL on a 100M-row table", "Drizzle or Prisma?", "Supabase or Neon?", "production query is slow", or when `db-worker-bee` is invoked. Do NOT use for PRD authoring (library-worker-bee), data-layer consumption in components (react-worker-bee), security audits of RLS / PII / encryption-at-rest (security-worker-bee), or RAG / embedding retrieval pipelines (ai-platform-worker-bee).

Designs, reviews, and heals the Hivemind Deep Lake data layer - the 7-table ColumnDef schema, USING deeplake DDL, FLOAT4[] embeddings, additive schema healing, append-only version-bump writes, deeplake_index / vector / hybrid search, DeeplakeApi querying, SQL guards, dataset versioning, and BYOC storage. Use when the user says "design this table", "review this ColumnDef", "is this index right?", "should this be a JSONB column or a tensor?", "we need a new NOT NULL column on the memory table", "how do we heal a missing column?", "vector or hybrid search here?", "which storage backend?", or when `deeplake-dataset-worker-bee` is invoked. Do NOT use for PRD authoring (library-worker-bee), TypeScript data-access consumption (typescript-node-worker-bee), security audits of creds / PII / token handling (security-worker-bee), or recall / embedding retrieval pipelines (retrieval-worker-bee for recall, embeddings-runtime-worker-bee for the embedding model).

npm supply-chain hygiene specialist for the @deeplake/hivemind package. Owns npm dependency update tooling (Renovate vs Dependabot for this repo), package-lock.json lockfile discipline (npm ci, minimumReleaseAge), npm audit triage (noise vs real, direct vs transitive), the optionalDependencies + tree-sitter native ABI risk (ensure-tree-sitter postinstall), SBOM generation for the npm package (Syft / CycloneDX), npm provenance (npm publish --provenance / Sigstore), socket.dev behavioral scanning, and the publish-time guards (files allowlist, pack-check.mjs, audit-openclaw, CodeQL). Use when the user says "audit our dependencies", "set up Renovate", "Renovate vs Dependabot", "socket.dev", "generate an SBOM", "npm audit is noisy", "lockfile hygiene", "npm provenance", "tree-sitter postinstall failing", "is our publish safe", or when dependency-audit-worker-bee is invoked. Do NOT use for application-code vulnerability remediation (security-worker-bee), Docker image scanning pipeline architecture (ci-release-worke

Bootstraps a complete design system from scratch for a product. Produces the seven-artifact folder — master design brief, master tokens CSS, utility layer CSS, per-component specs, per-screen specs, static HTML examples, and a README. Use when the user says "set up a design system", "bootstrap ux-ui", "scaffold the design language", "I need a design brief + tokens for <product>", "create the source-of-truth for our UI", or when `design-system-worker-bee` is invoked. Do NOT use for maintenance, PR review, or incremental token changes — that is `ux-ui-worker-bee`'s job.

Designs, audits, and authors Docker / Docker Compose / GitHub Actions / Depot pipelines for Node / Next.js / TypeScript stacks. Use when the user says "review my Dockerfile", "design our CI pipeline", "audit our workflow security", "migrate to Depot", "add a healthcheck to compose", "this build is slow", "we leaked a secret in CI", or when `devops-worker-bee` is invoked. Do NOT use for cloud provisioning (cloud-platform Bees), DB schema or migrations (db-worker-bee — devops-stinger wires the migration step but does not author it), security CVE deep audits (security-worker-bee — devops-stinger surfaces concerns and hands off), or PRD authoring (library-worker-bee).

Discord bot and application specialist for discord.js (v14/v15), discord.py 2.x, and Serenity (Rust). Covers slash commands, interactive components (buttons, select menus, modals), voice pipeline (Lavalink 4 + DAVE-compliant clients), gateway-vs-HTTP-endpoint architecture, rate-limit handling, shard management, and the bot verification path past 100 servers. Use when building, reviewing, or debugging any Discord bot or application — SDK selection, command registration, component flows, voice queues, scaling, or the bot-verification checklist. Do NOT use for general Python packaging (python-worker-bee), container/CI shapes (devops-worker-bee), credential vault integration (security-worker-bee), or database schema design for bot state (db-worker-bee).

Continuous product discovery coach — Teresa Torres interview cadence, Opportunity Solution Trees, Jobs-to-be-Done interviews, prototype testing, and the "build less, learn more" loop. Use when the user says "run a discovery session", "build an OST", "write an interview script", "map our assumptions", "design a prototype experiment", "weekly discovery summary", or when a team is unsure what to build next and needs to run discovery before planning. Do NOT use for shipped-feature usability testing (quality-worker-bee), UI design decisions (ux-ui-worker-bee), PRD authorship (library-worker-bee), or analytics result interpretation.

Documentation-site infrastructure specialist — platform selection (Docusaurus v3/v4, Mintlify, GitBook, MkDocs Material, Nextra v4, Starlight/Astro, Fern), the Diátaxis content pyramid, docs-as-code CI pipelines, and search setup (Algolia DocSearch, pagefind). Use when the user says "pick a docs platform", "set up Docusaurus", "migrate from GitBook", "add search to our docs", "docs-as-code CI", "Mintlify vs Starlight", or invokes `docs-site-worker-bee`. Do NOT use for OpenAPI spec enrichment or SDK generation (api-docs-worker-bee), internal knowledge-base authoring (library-worker-bee), or marketing website builds (website-worker-bee).

The embeddings runtime for Hivemind - the @huggingface/transformers + nomic-embed-text-v1.5 (768-dim, q8) daemon that generates vectors for Deep Lake recall. Covers daemon lifecycle (warmup, batching, socket IPC, crash recovery), the NDJSON Unix-socket protocol, embedding model and quantization selection scoped to Hivemind, the embeddings-on vs BM25-fallback decision, local-vs-hosted inference tradeoffs, and the dim-must-match-schema constraint (EMBEDDING_DIMS=768 ties to the FLOAT4[] columns). Use when the user says "should I turn embeddings on", "swap the embedding model", "the embed daemon is stuck", "why is recall falling back to BM25", "change the embedding dimension", or "is 600MB worth the semantic lift". Do NOT use for the Deep Lake dataset schema-heal mechanics themselves (deeplake-dataset stinger), API key security (security-worker-bee), or PRD authorship (library-worker-bee).

Software estimation and forecasting specialist. Covers relative-sizing frameworks (story points, Fibonacci, T-shirt sizing, Planning Poker), the NoEstimates movement and its evidence base, the planning-fallacy literature explaining why estimates are systematically wrong, and cycle-time / throughput-based probabilistic forecasting (Monte Carlo simulation, percentile-based delivery predictions). Invoke when the user says "our story points mean nothing", "should we use NoEstimates?", "how do I do T-shirt sizing for a roadmap?", "we need a 90% confidence delivery date", "explain Monte Carlo to my PM", "why are our estimates always wrong", or any question about sizing, forecasting, or the NoEstimates debate. Do NOT invoke for sprint cadence design, Jira/Linear tool configuration, or team-capacity math -- those belong to the team's agile process or tooling domains.

Production-focused font loading strategy specialist for 2026 web performance. Reviews, implements, and audits the web font loading pipeline: font-display descriptor selection (swap/optional/fallback/block/auto) with CLS risk analysis; <link rel="preload"> strategy for critical fonts; variable-font + Unicode-range subsetting pipeline (pyftsubset, glyphhanger, subfont); next/font App Router integration; and CLS-from-font-swap elimination via size-adjust, ascent-override, and metric-matched fallback stacks. Use when the user says "audit font loading", "fix FOIT", "CLS from font swap", "preload fonts", "subset variable font", "next/font config", "font-display strategy", "font performance", or invokes font-loading-worker-bee. Do NOT use for typeface selection or fluid type scales (typography-font-worker-bee), build-pipeline font subsetting in CI (devops-worker-bee), or Core Web Vitals measurement beyond CLS (seo-aeo-worker-bee).

Git mastery specialist - interactive rebase (squash, fixup, reword, drop), conflict resolution, history rewriting (git filter-repo, BFG), reset/reflog recovery, worktrees for parallel branches, hooks (Husky, lefthook), submodules vs subtrees, Git LFS, partial clone, and sparse checkout. Use when the user says "squash my commits", "I pushed a secret", "my repo is huge", "undo that rebase", "work on two branches at once", "set up Git hooks", "submodules vs subtrees", or needs any Git recovery operation. Do NOT use for CI/CD pipeline configuration (ci-release-worker-bee) or credential rotation after a secrets incident (security-worker-bee).

Repository hygiene auditor for GitHub repos - branching strategy, branch protection rulesets, PR culture, commit history (Conventional Commits), CI workflow density, README/docs presence, .gitignore coverage, CODEOWNERS, issue/PR templates, and repo settings (merge strategy, secret scanning, auto-delete). Use when the user says "audit this repo", "repo health check", "review our branching strategy", "check branch protection", "CODEOWNERS audit", "are our CI checks configured correctly", "check PR templates", or "GitHub repo settings review". Do NOT use for deep CI/CD architecture (ci-release-worker-bee), code correctness (security-worker-bee, typescript-node-worker-bee), or Deep Lake dataset schema (deeplake-dataset-worker-bee).

Hivemind multi-harness integration specialist. Covers adding and auditing harness adapters across the six supported coding assistants (Claude Code, Codex, Cursor, Hermes, pi, OpenClaw), capability detection and auto-install (src/cli/install-*.ts), per-host wiring (hooks vs extension vs MCP vs AGENTS.md marker), the capture/recall hook lifecycle, the shared-core + per-harness-bundle build model, MCP server registration (hermes), contracted tools (openclaw), and keeping the tool/hook contract stable across hosts. Use when the user says "wire a new harness", "add a hook event", "register the MCP server in hermes", "audit a harness adapter", "the OpenClaw bundle fails ClawHub scan", "capability detection for install", or when harness-integration-worker-bee is invoked. Do NOT use for Deep Lake dataset schema (deeplake-dataset-stinger), embeddings runtime (embeddings-runtime-stinger), MCP protocol internals beyond registration (mcp-protocol-stinger), or CI/CD pipeline topology (ci-release-stinger).