legioncodeinc
- 599 skills
- 0 followers
- 96 repo stars
- 2 days ago last updated
- ▌ Client Health Radar 2 · legioncodeinc bundlePer-client health rollup for agencies, consultancies and freelancers. Trigger on "which client is about to churn", "client health check", "am I losing this client", "weekly client review", "is this account at risk", "scope creep on this client", "which client is eating my margin", "client went quiet". Builds a ranked risk view per client from meetings, message threads and captured dashboards: unmet promises in both directions, silence gaps against that client's own cadence baseline, scope creep with the transcript quote where the ask happened, room and register changes, and payment or renewal signals. Bands with named evidence, never a score. Internal view only, nothing goes to the client.
- ▌ Brand Voice Guardian 2 · legioncodeinc bundleQuality assurance pass for anything shipping under the user's name. Trigger on 'does this sound like me', 'check this draft', 'run this past my voice', 'does this read as AI', 'fix the tone on this', 'my teammate wrote this, make it sound like me', 'de-AI this', or when the user pastes a draft and asks whether it is publishable. Runs a supplied draft, theirs or a teammate's or one an AI produced, against their installed personal voice skill. Returns a marked-up draft with every flagged span, a counted tell inventory, a clean rewrite in their voice, a separate fact-check pass on claims it could not corroborate against their own record, and a short why-each-change section. Tone-corrects only and never invents facts. Does not promise to defeat AI detectors, because nobody honestly can.
- ▌ Comment To Crm Piper 2 · legioncodeinc bundleNew hand-raisers into the CRM, daily. Trigger on 'who engaged with my post today', 'pipe my new comments into the CRM', 'add today's leads to GoHighLevel', 'anyone new since yesterday', 'get these commenters into my CRM', 'daily lead drip', 'tag my new leads by campaign'. Watches the user's own posts for new public engagement since the last run, dedupes each person against the CRM, upserts or produces a correctly shaped import file, tags by campaign, and queues a drafted first message. Drafts only. Never sends, and never writes private message contents into a CRM.
- ▌ Research Synthesizer 2 · legioncodeinc bundleResearch a topic and get the delta, not another wall of reading. Trigger on 'research this topic', 'what do I already know about', 'catch me up on', 'synthesize what I have read', 'is what I think about this still true', 'deep dive on a topic', 'what did I miss on', 'brief me on'. Pulls what the user has already encountered on screen and in messages about the topic, layers a fresh external sweep over it, and returns a synthesis split into what they already had, what is new since then, where the sources disagree, what they appear to believe based on what they actually said, and what is still open. Every external claim carries a URL. Optional recurring mode watches a standing topic and reports only what is new.
- ▌ Combined Voice Creator 2 · legioncodeinc bundleThe full-pipeline personal voice skill builder for Littlebird users. Combines BOTH data sources: mines the user's Littlebird memory via the Littlebird MCP (captured writing, messages, meeting speech, background context) AND ingests their Facebook data export (posts, messages, profile info, with a screenshot-guided export walkthrough). Produces one calibrated voice skill that writes exactly like the user and reads 100% human. Use this skill whenever a user says "build my voice skill", "make Claude write like me", "clone my voice", "create my writing style skill", or wants the most complete version of their voice from every source available. If the user only has ONE source, use facebook-voice-creator or littlebird-voice-creator instead.
- ▌ Runbook Writing Stinger 2 · legioncodeinc bundleOperational runbook authorship specialist covering canonical templates (break-fix, scheduled operation, diagnostic), the no-implied-context audit protocol, exact-command discipline, escalation path architecture, rollback procedure standards, runbook-as-test (game day) methodology, and postmortem-to-runbook linkage. Activate when the user says \\\"write a runbook\\\", \\\"audit this runbook\\\", \\\"our runbooks are out of date\\\", \\\"we need a runbook for this alert\\\", \\\"turn this postmortem into a runbook\\\", \\\"schedule a game day\\\", \\\"our on-call docs are weak\\\", or when `runbook-writing-worker-bee` is invoked. Do NOT activate for incident management tooling setup (PagerDuty/OpsGenie, route to ci-release-worker-bee), infrastructure provisioning decisions (route to ci-release-worker-bee), or documentation culture/process design beyond the runbook format (route to library-worker-bee).
- ▌ Typescript Node Stinger 2 · legioncodeinc bundleModern TypeScript/Node practice for this Hive's stack. SvelteKit (Svelte 5) on Vercel as the primary case: tsconfig (bundler resolution, verbatimModuleSyntax), typed load functions/form actions/+server.ts, Drizzle type inference, zod vs valibot at boundaries, Vitest plus Playwright, Biome vs ESLint, pnpm and monorepo choice, Node-on-Vercel policy. Also fully supports the legacy npm library/CLI publishing case (Hivemind stack: strict ESM on Node16 resolution, esbuild bundling, zod v3/v4 MCP split, jscpd, no ESLint/Prettier). Use when reviewing, refactoring, or authoring TypeScript or Node code in either context.
- ▌ Typography Font Stinger 2 · legioncodeinc bundleTypography and font-loading specialist for web products: variable fonts, Google Fonts vs Fontsource vs self-host, the FOIT/FOUT/FOFT loading story, font-display semantics, fluid type scales via clamp(), vertical rhythm, and the type-token architecture. Use when the user says \\\\\\\"set up fonts\\\\\\\", \\\\\\\"audit our typography\\\\\\\", \\\\\\\"fix FOIT/FOUT\\\\\\\", \\\\\\\"build a type scale\\\\\\\", \\\\\\\"migrate to next/font\\\\\\\", \\\\\\\"self-host fonts\\\\\\\", \\\\\\\"fluid type\\\\\\\", \\\\\\\"variable fonts\\\\\\\", \\\\\\\"font performance\\\\\\\", or when typography-font-worker-bee is invoked. Do NOT use for typeface selection or brand identity decisions (design-system-worker-bee), per-component application of type tokens (ux-ui-svelte-worker-bee), build pipeline font optimization (devops-worker-bee), or persisted user font preferences (db-worker-bee).
- ▌ Deeplake Dataset Stinger 2 · legioncodeinc bundleDesigns, 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).
- ▌ Dependency Audit Stinger 2 · legioncodeinc bundlenpm supply-chain hygiene specialist: dependency updates, lockfile discipline, audit triage, SBOM, and provenance. Use when auditing dependencies, fixing lockfile noise, or checking publish safety.
- ▌ Okr Goal Setting Stinger 2 · legioncodeinc bundleOKR methodology specialist for writing, grading, and iterating on Objectives and Key Results. Enforces the output-vs-input discipline, diagnoses sandbagged vs. ambitious goal-setting, calibrates quarterly cadence and check-in rituals, contextualizes OKRs against KPIs and MBOs, and adapts the framework for small teams and startups. Activate when the user says "write OKRs", "audit our OKRs", "are these KRs measurable?", "set up a quarterly goal cycle", "OKR vs KPI", "OKR for small team", "grade our OKRs", or when configuring OKR fields in Lattice, 15Five, Weekdone, or Notion. Do NOT activate for company strategy authorship (executives own that), engineering roadmap planning (domain Angels own that), or project management tooling beyond OKR-specific configuration.
- ▌ AI Tools Platform Stinger 2 · legioncodeinc bundleThe 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).
- ▌ Alt Ads Platforms Stinger 2 · legioncodeinc bundlePaid 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 Angel — handle inline), Google Search Ads (no peer Angel — handle inline), or organic social strategy (route to social-media-marketing-organic-worker-bee).
- ▌ Dark Mode Theming Stinger 2 · legioncodeinc bundleAudits and implements dark mode for React/Next.js: CSS tokens, next-themes wiring, FOWT prevention, SSR hydration, Tailwind v4 config, multi-brand theming. Use for dark mode setup or flashing bugs.
- ▌ Live Chat Support Stinger 2 · legioncodeinc bundleCustomer support surface specialist — Intercom, Crisp, Plain, Pylon, Help Scout — widget integration, HMAC/JWT identity verification, conversation routing, AI deflection (Fin 2.0, Ari, Crisp Bot), and the data-export discipline. Use when the user says "integrate live chat", "set up Intercom", "add a support widget", "wire HMAC identity verification", "configure AI deflection", "design conversation routing", or "set up customer support for our SaaS". DO NOT use for managing deployments (devops-worker-bee), application authentication (auth-worker-bee), or security audits of the resulting integration (security-worker-bee).
- ▌ Review Funnels G2 Stinger 2 · legioncodeinc bundleReview collection and online-reputation specialist for SaaS products -- G2, Capterra (now G2-owned), Trustpilot, Product Hunt, AppSumo, and Software Advice. Covers platform selection, profile setup, in-product review-request UX (timing, two-step pattern, copy), G2 incentive compliance (2026 rules + FTC Consumer Reviews Rule), Product Hunt launch-day playbook (00:01 PT, first-6-hours intensity, hunter sourcing), negative-review response templates, and earned-badge-as-conversion-asset deployment. Use when the user says "set up G2", "get more reviews", "Product Hunt launch", "is this incentive compliant", "respond to a negative review", "deploy G2 badges", "Capterra strategy", or asks anything about online review platforms for a SaaS product. Do NOT use for SEO structured data (seo-aeo-worker-bee), outbound cold-email infrastructure beyond a review-request drip (cold-outreach-worker-bee), or social amplification of reviews (social-media-marketing-organic-worker-bee).
- ▌ Branching Strategy Stinger 2 · legioncodeinc bundleBranching 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`).
- ▌ Browser Automation Stinger 2 · legioncodeinc bundlePlaywright and Puppeteer automation for deterministic browser tests, debugging, downloads, screenshots, and browser lifecycle control. Use for browser automation work.
- ▌ Discovery Research Stinger 2 · legioncodeinc bundleContinuous 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.
- ▌ Embeddings Runtime Stinger 2 · legioncodeinc bundlePicks and runs embedding models: hosted (OpenAI, Cohere, Voyage) vs self-hosted, cost tradeoffs, batching, caching. Use when choosing, swapping, or debugging an embedding model.
- ▌ Github Repo Health Stinger 2 · legioncodeinc bundleRepository 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 (vector-store-worker-bee).
- ▌ Image Optimization Stinger 2 · legioncodeinc bundleImage optimization specialist for React/Next.js and HTML contexts: AVIF/WebP format selection (AVIF is the 2026 production default), responsive srcset/sizes calculus, blur placeholders (LQIP via Sharp, BlurHash-as-CSS-gradient, ThumbHash), next/image remote patterns and the Next.js 16 priority→preload shift, and CLI tooling (Sharp Node API, Squoosh CLI for one-offs). Use when the user says \\\"optimize my images\\\", \\\"convert to AVIF\\\", \\\"set up srcset\\\", \\\"add blur placeholders\\\", \\\"next/image remote patterns\\\", \\\"LCP image is slow\\\", \\\"fix layout shift from images\\\", \\\"AVIF vs WebP\\\", or when auditing a codebase for unoptimized image delivery. Do NOT use for SVG icon systems (icon-system-worker-bee), general Lighthouse audits beyond image-specific findings (lighthouse-pagespeed-worker-bee), CDN/caching architecture beyond image Cache-Control (devops-worker-bee), or CSS animation performance (ux-ui-svelte-worker-bee).
- ▌ Investor Cap Table Stinger 2 · legioncodeinc bundleCap-table management and fundraising paperwork specialist for startup founders -- Carta, Pulley, Cake Equity, Capdesk (AngelList Stack sunset August 2026), SAFEs (YC post-money standard), priced rounds (Series A+ term sheets), 409A valuations, option pool sizing and refresh, vesting schedules (4-year/1-year cliff, double-trigger), and investor data-room preparation. Use when the user says "set up a cap table", "Carta vs Pulley", "SAFE mechanics", "409A valuation", "option pool", "vesting schedule", "data room for Series A", "term sheet provisions", or "fundraising paperwork". Do NOT use for company formation (incorporation-startup-stack-worker-bee), ongoing bookkeeping (out of scope), securities law advice (always defer to counsel), or Stripe billing (payments-worker-bee).
- ▌ Modal Toast Dialog Stinger 2 · legioncodeinc bundleAccessible overlay specialist for React: primitive selection (Radix Dialog, AlertDialog, Vaul Drawer, Sonner toast, cmdk command menu, Headless UI), the six-point accessible-modal contract (focus trap, escape, scroll lock, aria-modal, aria-labelledby, focus return), and the four-tier toast-vs-notification taxonomy. Use when choosing an overlay primitive, debugging focus trap regressions, implementing a drawer/sheet, wiring Sonner toasts into a React app, building a command palette, or auditing overlay stacking behavior. Paired with `modal-toast-dialog-worker-bee`.
- ▌ Harness Integration Stinger 2 · legioncodeinc bundleCross-harness capability integration for The Hive's four harnesses (Claude Code, Cursor, ChatGPT Codex, Claude Cowork). Covers per-harness component placement (rules, commands, agents, skills, plugins), the wiring-mechanism decision (hooks vs MCP vs native extension vs plain instruction file), hook/lifecycle events per harness, MCP registration per harness (JSON vs TOML, Cowork connector reachability), capability detection/graceful degradation, and portability (spec-six frontmatter, AGENTS.md baseline, plugin manifests). Includes a worked six-host case study. Use for \\\"wire this into Claude Code and Cursor\\\", \\\"add a hook event\\\", \\\"register an MCP server across harnesses\\\", \\\"audit a harness adapter\\\", \\\"will this work in Cowork\\\", or when harness-integration-worker-bee is invoked. Do NOT use for vector-store schema (vector-store-stinger), embeddings runtime (embeddings-runtime-stinger), MCP protocol internals (mcp-protocol-stinger), or CI/CD topology (ci-release-stinger).
- ▌ Highlevel AI Studio Stinger 2 · legioncodeinc bundleHighLevel AI Studio specialist for Vibe sites, Content AI, Funnel & Website AI, and WordPress AI pages. Use for HighLevel AI content, site building, publishing, or troubleshooting.
- ▌ Natural Photography Stinger 2 · legioncodeinc bundlePhotographic generation and editing for consented model work using gpt-image-2 or Nano Banana Pro. Supports capture-backed references and explicitly acknowledged visual-only references, with capability-gated editing, imperfection-led realism prompting, and honest EXIF handling.
- ▌ Newsletter Platform Stinger 2 · legioncodeinc bundleNewsletter-as-channel specialist for product builders — Beehiiv, ConvertKit (Kit), Loops, Substack, Resend Audiences, Ghost, the embedded-newsletter-page pattern, deliverability vs platform tradeoffs, and monetization options (ad network, paid subscriptions, sponsorships, referrals). Use when the user says "which newsletter platform should I use", "set up Beehiiv", "embed a newsletter signup", "migrate from Substack to Beehiiv", "how do I monetize my newsletter", "Loops vs Kit for my SaaS", "self-hosted newsletter deliverability", or when `newsletter-platform-worker-bee` is invoked. Do NOT use for transactional email sending infrastructure (route to `resend` tooling), SPF/DKIM/DMARC DNS setup at the infrastructure level (route to `devops-worker-bee`), Stripe subscription billing for custom paid tiers (route to `payments-worker-bee`), or SEO content strategy (route to `seo-aeo-worker-bee`).
- ▌ App Store Submission Stinger 2 · legioncodeinc bundleApp 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-svelte-worker-bee), client-side StoreKit / billing implementation code (react-worker-bee / python-worker-bee), or app security audits (security-worker-bee).
- ▌ Competitive Research Stinger 2 · legioncodeinc bundleBuilds an XLSX competitor-landscape workbook and a brand-matched PDF report from scratch: research sweep, category taxonomy, feature-gap analysis, computed market-pattern insights, and sales battlecards. Invoke on phrases like build a competitor comparison spreadsheet, research our competitors, make a battlecard deck, competitive landscape report, or feature gap analysis against competitors.
- ▌ Lighthouse Pagespeed Stinger 2 · legioncodeinc bundleRuns Lighthouse and PageSpeed Insights for React/Next.js: CI setup (LHCI), audit categories, performance budgets, lab-vs-CrUX gap. Use when setting up or debugging Lighthouse CI.
- ▌ CSV XLSX Import Export Stinger 2 · legioncodeinc bundleThe \\\"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-svelte-worker-bee), database bulk-insert tuning (db-worker-bee), or upload endpoint security audit (security-worker-bee).
- ▌ HTTP REST Fundamentals Stinger 2 · legioncodeinc bundle'HTTP and REST protocol authority: audits HTTP method safety/idempotency contracts, status-code honesty, header correctness (Cache-Control, ETag, Vary, CORS), conditional and range requests, HTTP/2 + HTTP/3 readiness, and REST architectural-style compliance. Activate when the user says \\\"audit this API\\\", \\\"is this status code correct?\\\", \\\"why is CORS failing?\\\", \\\"explain preflight\\\", \\\"PUT vs PATCH\\\", \\\"HTTP/3 ready?\\\", or when reviewing any route handler, OpenAPI spec, or HTTP trace. Do NOT activate for TLS/cipher config (devops-worker-bee), auth token semantics (auth-worker-bee), or crawler-facing metadata (seo-aeo-worker-bee).'
- ▌ Changelog Release Notes Stinger 2 · legioncodeinc bundleWrites 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 Hive).
- ▌ Technical Writing Craft Stinger 2 · legioncodeinc bundleWriting docs well -- the Diataxis framework (tutorial / how-to / reference / explanation), inverted-pyramid prose structure, scannable headings, code-example discipline, the \\\"what does the reader already know?\\\" reader-lens, ghostwriting vs voice consistency, and the docs-as-code review workflow. Distinct from library-worker-bee (which owns docs-site architecture and where a doc lives); this stinger owns the craft of writing. Use when the user says \\\"review this document\\\", \\\"is this doc well-written\\\", \\\"audit this page\\\", \\\"write a tutorial for X\\\", \\\"apply Diataxis\\\", \\\"ghostwrite this guide\\\", \\\"my docs PR needs a writing review\\\", or any request about documentation quality rather than documentation tooling.
- ▌ Customer Support Tooling Stinger 2 · legioncodeinc bundleSupport 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).
- ▌ Product Feedback Roadmap Stinger 2 · legioncodeinc bundleCustomer-feedback-to-roadmap loop specialist — Userback, Canny, Featurebase, Productboard, Frill, Productlane — platform selection decision tree, in-app-widget vs portal vs voting-board taxonomy, de-duplication discipline, RICE/ICE prioritization, status-transition policy, public vs private roadmap playbook, and CRM/issue-tracker integration wiring. Use when the user says "set up a feedback system", "which feedback tool should I use", "Canny vs Featurebase", "our feature requests are a mess", "set up a public roadmap", "RICE scoring for our backlog", "Productlane + Linear", "voting board for our SaaS", or when product-feedback-roadmap-worker-bee is invoked. Do NOT use for the React UI of an embedded widget (react-worker-bee), the database schema for a custom-built feedback store (db-worker-bee), marketing copy on the public roadmap page (seo-aeo-worker-bee), or billing integration for premium feedback tiers (payments-worker-bee).
- ▌ Blogging Content Strategy Stinger 2 · legioncodeinc bundleEditorial 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.
- ▌ Affiliate Referral Program Stinger 2 · legioncodeinc bundleAffiliate 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).
- ▌ Knowledge Base Help Center Stinger 2 · legioncodeinc bundleCustomer-facing knowledge bases — Intercom Articles, Help Scout Docs, ReadMe.com, Document360, HelpJuice, Zendesk Guide — search-first design, AI deflection (chat-with-your-docs), versioning, multi-language, the analytics-driven content-gap loop. Use when the user says "pick a KB platform", "set up a help center", "migrate Zendesk Guide", "add AI deflection to our docs", "fix our search no-results", "localize our KB", or invokes `knowledge-base-help-center-worker-bee`. Do NOT use for support inbox/ticketing (customer-support-tooling-worker-bee), live chat widget wiring (live-chat-support-worker-bee), organic SEO keyword strategy (seo-aeo-worker-bee), or RAG/embedding pipeline implementation (mind-worker-bee).
- ▌ Product Tour Onboarding UI Stinger 2 · legioncodeinc bundleIn-app product tour and onboarding UI specialist. Selects the right tour tool (Userpilot, Appcues, Userflow, Pendo Guides, Driver.js, Shepherd.js, Intro.js), implements tooltip/modal/hotspot/checklist components, wires segment-based trigger logic, and establishes a tour maintenance protocol that survives iterative UI changes. Invoke when the user says \\\"set up a product tour\\\", \\\"build an onboarding checklist\\\", \\\"compare Driver.js vs Shepherd.js\\\", \\\"our tours keep breaking after deploys\\\", \\\"which product tour tool should we use\\\", \\\"add segment-based tour triggers\\\", or \\\"our tour is showing to the wrong users\\\". Do NOT invoke for broader onboarding email sequences (lifecycle-email Bee), user-auth flows (auth-worker-bee), design token work (ux-ui-svelte-worker-bee), or analytics instrumentation (posthog/mixpanel Bees).
- ▌ Incorporation Startup Stack Stinger 2 · legioncodeinc bundleCompany formation decision toolkit for software startup founders. Covers formation platform selection (Stripe Atlas, Clerky, Doola, Firstbase), entity type advice (Delaware C-Corp vs LLC vs international), EIN workflow, startup banking (Mercury, Brex, Relay), bookkeeping (Pilot, Bench), and the minimum founder-paperwork checklist including the 83(b) election. Activate when the user says "incorporate my startup", "which formation platform should I use", "Stripe Atlas vs Clerky", "set up Mercury or Brex", "EIN for my LLC", "83(b) election deadline", "Delaware C-Corp vs LLC", or asks about the minimum paperwork to form a company. Do NOT activate for ongoing tax compliance, cap-table management (Carta/Pulley), fundraising mechanics (SAFEs, priced rounds), or post-formation state filings — those exceed this stinger's scope.
- ▌ Markdown Mdx Content Pipeline Stinger 2 · legioncodeinc bundleMarkdown/MDX processing specialist - MDX 3/compiler selection, remark/rehype plugin pipelines, Shiki v4/expressive-code/starry-night syntax highlighting, GFM, AST manipulation, custom directive plugins, math/Mermaid diagram embedding, and XSS sanitization. Use when building or auditing any content processing pipeline that takes .md/.mdx source to HTML/JSX output.
- ▌ Social Media Marketing Organic Stinger 2 · legioncodeinc bundleGenuine organic social strategy for solo developers, founders, and teams up to ~10 people. No AI-generated posts, no cross-post automation slop, no bought followers. Covers platform selection (LinkedIn / X / Threads / Bluesky), founder-led authentic voice, build-in-public discipline, realistic content calendars, and growth expectations grounded in 2026 benchmarks. Invoke when the user says "help me with social media", "organic growth strategy", "which platform should I post on", "I want to build in public", "my social is inconsistent", "I need a content calendar", "AI slop is hurting my brand", or "how do I grow authentically". Do NOT invoke for paid advertising (no Angel yet), email newsletter strategy (newsletter-platform-worker-bee), SEO content strategy (seo-aeo-worker-bee), or Discord/Slack community management (out of scope).
- ▌ Electron Dissection Stinger 2 · legioncodeinc bundleDissect and reverse engineer Electron desktop apps: locate resources/app.asar, read archive metadata, unpack with @electron/asar, decode bundled/minified JavaScript with webcrack, and attach live inspectors over the Chrome DevTools Protocol. Use when asked to unpack app.asar, reverse engineer / dissect / audit an Electron app, find what code a desktop app runs, recover app logic from a bundle, attach devtools via remote debugging, or harden your own Electron app against exactly this.
- ▌ Stinger Name 2 · legioncodeinc bundle{One or two sentences: what this stinger does and exactly when Claude should reach for it. Front-load the trigger words, since Codex and Cursor both judge relevance from this text alone. Keep it under 200 characters if you want the same file to survive Cowork's stricter cap without editing.}
- ▌ Example Stinger 2 · legioncodeincPlaceholder stinger shipped inside the Hive reference plugin skeleton, showing where a real plugin-bundled skill lives. Not a working stinger on its own.
- ▌ DB Stinger 2 · legioncodeinc bundleDesigns, 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 (mind-worker-bee).
- ▌ Go Stinger 2 · legioncodeinc bundleGo specialist for modules, toolchains, vendoring and fork-in-tree freezes, cgo .so plugin ABI, project layout, and builds. Use for go.mod, replace directives, vendoring upstream repos, plugin crashes.
- ▌ Git Stinger 2 · legioncodeinc bundleGit 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).
- ▌ Auth Stinger 2 · legioncodeinc bundleImplements 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).
- ▌ Mind Stinger 2 · legioncodeinc bundleReviews, audits, and extends the AI cognitive layer: coach routing, prompt cascade, RAG, three-tier memory, observability, evaluation. Use when reviewing AI code or tuning retrieval.
- ▌ Rust Stinger 2 · legioncodeinc bundleRust development specialist for Cargo, async services, persistence, CLI/TUI, tests, upgrades, and current toolchains. Use for Rust implementation, review, migration, or release guidance.
- ▌ Wiki Stinger 2 · legioncodeinc bundleEquips wiki-worker-bee with the 13-type code entity catalog, tree-sitter AST extraction patterns (the repo's own src/graph approach), ADR detection from commit messages, the active four-artifact contradiction protocol, and canonical knowledge-page templates with code-aware frontmatter. Use when wiki-worker-bee is invoked to extract entities and concepts from code chunks plus git context into library/knowledge/, or to lint the existing knowledge area for orphans, dead links, and stale claims. Not for module narrative authorship (use library-stinger) or QA report authorship (use quality-stinger).
- ▌ Asset Stinger 2 · legioncodeinc bundleEquips 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-svelte-stinger), or security audits of the registry tables (use security-stinger).
- ▌ React Stinger 2 · legioncodeinc bundleReviews, refactors, and authors React 18/19 codebases using the bulletproof-react architectural pillars and the curated 2025-2026 React ecosystem. Use when the user says \\\"review this React code\\\", \\\"react architecture review\\\", \\\"audit our React app\\\", \\\"state management decision\\\", \\\"what's the bleeding-edge React pattern for X\\\", \\\"propose a React refactor\\\", \\\"is this React anti-pattern\\\", or when `react-worker-bee` is invoked. Do NOT use for visual design (ux-ui-svelte-worker-bee), SEO/Next.js metadata strategy (seo-aeo-worker-bee), security audits (security-worker-bee), or PRD authoring (library-worker-bee).
- ▌ Tauri Stinger 2 · legioncodeinc bundleTauri 2 engineering for desktop and mobile: updates, migration, IPC, capabilities, sidecars, AI runtimes, persistence, signing, updater, testing, and distribution. Use for Tauri-specific work.
- ▌ UX UI Stinger 2 · legioncodeinc bundleEnforces a product's design system end-to-end — opens the source-of-truth folder first, cites governing sections, specifies pixel-perfect deltas in token-named terms, and applies per-library integration rules for shadcn/ui, Mantine, Lucide-react, and Framer Motion. Use when reviewing UI pull requests, authoring component or screen specs, wrapping an external component library, auditing a screen for token/utility/motion violations, or when the user says "is this on-brief?", "review this screen", "should we use shadcn for this?", "wrap this Mantine component", or "the brief doesn't cover this — extend it." Do NOT use for system-wide aesthetic overhauls (route to `design-system-worker-bee`) or for asset registration (route to `asset-worker-bee`).
- ▌ Beekeeper Suit 2 · legioncodeinc bundleRoutes a request to the right Bee in The Hive for this repo (SvelteKit, Payload, Neon, WorkOS, Stripe, Vercel), arms it with its paired Stinger, and enforces the Ship Gate before anything ships.
- ▌ Devops Stinger 2 · legioncodeinc bundleDesigns, 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).
- ▌ Preact Stinger 2 · legioncodeinc bundlePreact 11 specialist skill: signals-based reactivity (v2 API with createModel/useModel), preact/compat migration from React, third-party embed widgets (shadow DOM isolation, IIFE bundles), Astro island integration (client:* directives, 5.0.1 or newer useId fix), and Fresh 2.x framework (Deno-native, islands + serializable props). Use when building Preact components, evaluating Preact vs React, migrating from React to Preact, embedding a widget on third-party pages, or working with Astro or Fresh projects. Do NOT use for React architecture in general (react-worker-bee), Next.js App Router configuration (react-worker-bee), or Deno infrastructure beyond Fresh (devops-worker-bee).
- ▌ Python Stinger 2 · legioncodeinc bundlePython code specialist for Django, FastAPI, Celery, Channels, pytest, uv, and Ruff. Use when reviewing, refactoring, or authoring Python code, or migrating DRF to Ninja.
- ▌ Sentry Stinger 2 · legioncodeinc bundleSentry error tracking for SvelteKit on Vercel - client/server hooks, source maps and releases, tracing sampling, session replay, PII scrubbing, alert tuning, and cost control.
- ▌ Svelte Stinger 2 · legioncodeinc bundleSvelte 5 specialist for runes, snippets, lifecycle, universal reactivity, SvelteKit 2 load/actions/remote functions, and Svelte 4 migration. Use for any .svelte, .svelte.js, or .svelte.ts work.
- ▌ Vercel Stinger 2 · legioncodeinc bundleVercel deployment for SvelteKit (Svelte 5) + Neon - adapter-vercel config, runtimes, ISR/caching, env vars, cron, image optimization, middleware, WAF/rate limiting, cost control, rollbacks.
- ▌ Workos Stinger 2 · legioncodeinc bundleWorkOS AuthKit for SvelteKit - hosted/headless flows, sealed sessions, JWT verification, orgs, RBAC, SSO/SCIM, MFA/passkeys/Magic Auth, webhooks, and staging-to-prod cutover.
- ▌ Bifrost Stinger 2 · legioncodeinc bundleBifrost AI gateway specialist: maximhq/bifrost architecture, admin and inference API surface, virtual keys, semantic cache, .so plugins, tags, fork freeze and upgrade policy. Use for any Bifrost work.
- ▌ Doppler Stinger 2 · legioncodeinc bundleDoppler secrets manager for SvelteKit on Vercel - doppler run/secrets CLI, project/config model, Vercel sync, service tokens, rotation, audit logs, GitHub Actions CI, replacing .env files.
- ▌ Library Stinger 2 · legioncodeinc bundleEquips library-worker-bee with the documentation lifecycle - knowledge-base authoring (public vs private audience split), feature PRD authoring (prd-{###}-{slug}/ with index + sub-PRDs + qa/), issue IRD authoring (ird-{###}-{slug}/ with index + qa/), backwards-PRD generation, sync audits / drift detection, and lifecycle moves (backlog/in-work/completed) against this repo's schema v2 library/. Use when initializing a library/, ingesting issues, planning features, writing knowledge docs, running drift audits, or moving a completed PRD/IRD to its completed/ tier. Not for QA report authorship (use quality-stinger) or narrative knowledge docs (use knowledge-stinger).
- ▌ Posthog Stinger 2 · legioncodeinc bundlePostHog for SvelteKit: install, pageview tracking, autocapture vs manual events, identify/alias, feature flags, experiments, replay, surveys, groups, Vercel proxy, EU/US residency, cost control.
- ▌ Quality Stinger 2 · legioncodeinc bundleAudits a completed implementation against its source plan document and produces a structured findings report. The report goes in the source plan's `reports/` subfolder (e.g., `library/requirements/{lifecycle}/prd-{###}-{title}/reports/{date}-qa-report.md` or `library/issues/{lifecycle}/ird-{###}-{title}/reports/{date}-qa-report.md`); standalone audits go to `library/requirements/reports/{domain}/{date}-qa-report.md`. Use when the user says \\\"QA this\\\", \\\"audit the implementation\\\", \\\"check the plan against the code\\\", \\\"run quality-worker-bee\\\", \\\"verify the PRD was built\\\", or when `security-worker-bee` has just finished and the loop ends with a QA pass before merge. Produces a markdown findings report with scorecard, severity-tagged findings, and a plan-item traceability table. Does not write code, fix issues, or author plans.
- ▌ SEO Aeo Stinger 2 · legioncodeinc bundleSEO and AEO for SvelteKit (Svelte 5) + Payload CMS + Vercel. Covers metadata, sitemap/robots, JSON-LD, Payload SEO fields, Core Web Vitals, llms.txt/AI citation, E-E-A-T, and indexation playbooks.
- ▌ Website Stinger 2 · legioncodeinc bundleBuilds production-grade SvelteKit (Svelte 5) + Payload CMS + Supabase websites end-to-end from a brief, applying a 12-phase playbook. Default CMS mode is Payload 3.x (self-hosted Next.js on Vercel, consumed via REST from SvelteKit). Fallback CMS mode is TypeScript-as-CMS for one-page lead-gen sites that skip Payload. Trigger on phrases like \\\"build a website\\\", \\\"scaffold a SvelteKit site\\\", \\\"spin up a marketing site\\\", \\\"build me a lead-gen site\\\", \\\"ship a website from scratch\\\", \\\"create a SvelteKit + Supabase site\\\", or whenever the paired `website-worker-bee` Bee is invoked. Do not trigger for one-off page tweaks, copy edits, or deploy-only tasks.
- ▌ API Docs Stinger 2 · legioncodeinc bundle'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).'
- ▌ Payments Stinger 2 · legioncodeinc bundleStripe for SvelteKit. Defaults to custom checkout with Elements (Payment/Address/Express Checkout, Appearance API) over hosted Checkout. Covers Payment Intents, subscriptions, webhooks, PCI scope.
- ▌ Security Stinger 2 · legioncodeinc bundleSecurity audit for SvelteKit, Neon/Drizzle, WorkOS, Stripe, Vercel, Doppler, and GoHighLevel. First gate of the Ship Gate - scans, triages, and remediates vulnerabilities before quality-stinger.
- ▌ Tailwind Stinger 2 · legioncodeinc bundleTailwind CSS v4 the framework itself, CSS-first config, @theme, the Vite plugin, v3-to-v4 migration, dark mode, container queries, class ordering. Generic, any codebase, not OSPRY-specific.
- ▌ Tanstack Stinger 2 · legioncodeinc bundleTanStack libraries in SvelteKit (Svelte 5) - Query SSR/caching/mutations, Table runes state, Form snippet validation, Virtual; states plainly that Router and Start have no official Svelte support.
- ▌ Archivist Stinger 2 · legioncodeinc bundlePrepares an acquired repository for archival: provenance intake, attribution and PII scrub, docs merge into library/, knowledge-base fleet, identifier rename, verification. Any language or license.
- ▌ Docs Site Stinger 2 · legioncodeinc bundleDocumentation-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).
- ▌ Knowledge Stinger 2 · legioncodeinc bundleAuthors narrative knowledge documentation for any repository - the human-readable, technically deep domain docs that live in `library/knowledge/private/{domain}/`. Covers system overviews, architecture narratives, data schemas, API patterns, security models, coding standards, and operational runbooks. Works from ADRs and PRDs as source material; produces Mermaid diagrams, SQL DDL, TypeScript samples, and sequence diagrams. Distinct from library-stinger: library-stinger owns PRDs and IRDs; knowledge-stinger owns the knowledge/ domain. Use when the user says \\\"document the hybrid recall pipeline\\\", \\\"write a system overview\\\", \\\"create knowledge docs for this repo\\\", \\\"document how the embeddings daemon works\\\", or \\\"build out the knowledge base\\\".
- ▌ Queen Bee Stinger 2 · legioncodeinc bundleForge new rules, plugins, commands, agents (Bees), and skills (Stingers) for The Hive across Claude Code, Cursor, Codex, and Cowork. Use when creating, updating, or validating any Hive component.
- ▌ Retrieval Stinger 2 · legioncodeinc bundleDesigns and audits retrieval: full-text search, pgvector recall, hybrid RRF fusion, reranking, chunking, recall quality eval. Use when tuning recall or a search query misses.
- ▌ Slack App Stinger 2 · legioncodeinc bundleSlack app development specialist for Bolt SDK (JS/Python/Java), slash commands, Block Kit UI composition, modals, Events API, OAuth multi-workspace install, and App Directory submission. Use when the user says \\\"build a Slack app\\\", \\\"add a slash command\\\", \\\"create a Slack modal\\\", \\\"set up Slack Events API\\\", \\\"OAuth multi-workspace\\\", \\\"submit to Slack Marketplace\\\", or when slack-app-worker-bee is invoked. Do NOT use for CI/CD pipeline topology (devops-worker-bee), secrets vault configuration (security-worker-bee), Django/FastAPI backend patterns beyond Bolt integration (python-worker-bee), or Slack Connect / Enterprise Grid administration.
- ▌ Tailscale Stinger 2 · legioncodeinc bundleTailscale for SvelteKit/Vercel/Neon - tailnets, MagicDNS, ACLs/tags, SSH, subnet routers, exit nodes, private database access, Funnel/Serve, OAuth clients, auth keys, ephemeral CI nodes, key expiry.
- ▌ CI Release Stinger 2 · legioncodeinc bundleCI and release engineering for GitHub Actions + SvelteKit on Vercel: job design, Vercel/Actions interaction, environment promotion, Neon/Drizzle migration gating, Doppler/OIDC secrets, caching, required checks, release automation. Also covers npm-package publishing (legacy case).
- ▌ Cursor Ide Stinger 2 · legioncodeinc bundleEquips 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/ colony 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 colony'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).
- ▌ Estimation Stinger 2 · legioncodeinc bundleSoftware 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.
- ▌ Heygen API Stinger 2 · legioncodeinc bundleHeyGen API integration for video generation, avatars, assets, webhooks, limits, and safe asynchronous delivery. Use for HeyGen API implementation or debugging.
- ▌ Hiring Ats Stinger 2 · legioncodeinc bundleApplicant Tracking Systems specialist -- Ashby, Greenhouse, Workable, Lever, Rippling Recruiting, Pinpoint -- platform selection decision matrix, pipeline-stage design, scorecard calibration (BARS, debrief-before-submit), D&I/EEOC reporting, take-home-test ethics (the 2-hour paid threshold, anonymous grading), sourcing-tool integrations (Gem, hireEZ, LinkedIn RSC), and the ATS-to-HRIS handoff (especially Rippling). Invoke when the user says "which ATS should we use", "audit our scorecards", "set up our hiring pipeline", "take-home test paid or unpaid", "Gem vs hireEZ", "ATS to Rippling handoff", "D&I funnel reporting", or when hiring-ats-worker-bee is invoked. Do NOT invoke for job description writing (out of scope), compensation benchmarking (no Angel yet), or deep HRIS configuration beyond the ATS handoff interface (future hris-worker-bee).
- ▌ Hr Payroll Stinger 2 · legioncodeinc bundleHR + payroll + EOR decision specialist for early-stage to growth-stage software companies. Owns domestic payroll platform selection (Gusto, Rippling, Justworks), international contractor management and EOR (Deel, Remote.com, Oyster, Rippling Global), the W-2/1099/EOR/PEO classification matrix, equity admin handoff (Carta), and benefits brokerage. Invoke when the user says "Gusto vs Rippling", "set up payroll", "EOR for international hire", "contractor vs employee", "W-2 or 1099?", "Deel vs Remote", "set up Justworks", "benefits for my startup", or "equity admin and payroll". Do NOT invoke for general HRIS/performance tools (Lattice, Culture Amp), recruiting/ATS platforms, immigration/visa law, or accounting software beyond the payroll integration surface (db-worker-bee owns HR data schema).
- ▌ Impeccable Stinger 2 · legioncodeinc bundleOperates the entire Impeccable design system (pbakaus/impeccable, Apache-2.0) for the Bee Army: the four-phase loop (Start to Iterate to Polish to Maintain), the context contract (PRODUCT.md + DESIGN.md + surface briefs), the 23-command vocabulary, the deterministic 59-rule anti-slop detector gate, hooks, live mode, and native playbooks. Use when impeccable-worker-bee is invoked, or for ANY frontend UI/UX/design implementation, redesign, refinement, new surface, component work, or design-system capture that must stay cohesive and free of AI-slop tells. Do NOT use for backend-only or non-UI tasks, or for product-specific design-system token enforcement (that is design-system-stinger / ux-ui-svelte-stinger).
- ▌ Legal Docs Stinger 2 · legioncodeinc bundleSaaS legal document generation and maintenance specialist. Covers Terms of Service, Privacy Policy, DPA, MSA, and Cookie Notice using the template+lawyer-review path. Anchored in Termly/Iubenda generators and GDPR/CCPA/Quebec Law 25/LGPD compliance postures. Use when the user says "generate a privacy policy", "draft a DPA", "set up our Terms of Service", "review a customer DPA redline", "which legal doc generator should I use", "GDPR compliance for SaaS", or when legal-docs-worker-bee is invoked. Do NOT use for technical data-protection controls (security-worker-bee), database schema for personal-data fields (db-worker-bee), or contract negotiation strategy beyond the DPA (legal team).
- ▌ Adr Writing Stinger 2 · legioncodeinc bundleArchitecture 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).
- ▌ Agile Scrum Stinger 2 · legioncodeinc bundle'Scrum methodology specialist: sprints, ceremonies (Sprint Planning, Daily Scrum, Sprint Review, Retrospective, Backlog Refinement), roles (Scrum Master, PO, Developers), estimation (Fibonacci, Planning Poker, #NoEstimates), Definition of Done templates by maturity, anti-pattern catalog (Scrum-but, Zombie Scrum, HiPPO PO, velocity gaming), framework selection (Scrum vs ScrumBan vs Kanban vs Shape Up), and the \\\"is this actually Scrum?\\\" honesty audit. Use when the user says \\\"audit our Scrum process\\\", \\\"is this Scrum?\\\", \\\"Sprint Planning help\\\", \\\"write our DoD\\\", \\\"retrospective format\\\", \\\"should we switch to Kanban\\\", \\\"Scrum anti-patterns\\\", or when `agile-scrum-worker-bee` is invoked. Do NOT use for project management tooling configuration (Jira, ClickUp), code review (security-worker-bee, react-worker-bee), or general project management without a Scrum context.'
- ▌ Discord Bot Stinger 2 · legioncodeinc bundleDiscord 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).
- ▌ Get Started Stinger 2 · legioncodeinc bundleInitializes a repo to a healthy baseline: library/ docs, GitHub CI, README, .gitignore, CODEOWNERS, SECURITY.md, CHANGELOG.md. Use when bootstrapping a repo or auditing one for missing hygiene files.
- ▌ Gohighlevel Stinger 2 · legioncodeinc bundleGoHighLevel API authority - OAuth vs Private Integration Tokens, contacts/opportunities/calendars, inbound/outbound webhooks, rate limits, Marketplace apps. Use for GoHighLevel/HighLevel integration.
- ▌ Icon System Stinger 2 · legioncodeinc bundleIcon-system specialist for React/Next.js: library selection (Lucide, Heroicons, Tabler, Phosphor, Iconify), tree-shake-vs-SVG-sprite trade-off, dynamic-import-by-name pattern, custom SVG component authoring, and the accessibility contract (aria-hidden for decorative icons, aria-label for semantic icons, accessible name for icon buttons). Use when choosing an icon library, debugging bundle-size regressions from icon imports, wiring a dynamic icon loader, building a custom SVG wrapper, or auditing icon accessibility. Paired with `icon-system-worker-bee`.
- ▌ Kanban Flow Stinger 2 · legioncodeinc bundleKanban method specialist: WIP limit design and enforcement, flow-metric calculation (cycle time, lead time, throughput, flow efficiency), Little's Law diagnostics, visual-board design, class-of-service policies, cumulative-flow-diagram interpretation, and tool-specific implementation (Linear, Jira, GitHub Projects). Use when the user says \\\\\\\"set up WIP limits\\\\\\\", \\\\\\\"calculate cycle time\\\\\\\", \\\\\\\"apply Little's Law\\\\\\\", \\\\\\\"design our Kanban board\\\\\\\", \\\\\\\"Kanban vs Scrum\\\\\\\", \\\\\\\"our WIP is always exceeded\\\\\\\", \\\\\\\"why is our cycle time so long\\\\\\\", or when `kanban-flow-worker-bee` is invoked. Do NOT use for sprint ceremonies / velocity (Scrum domain, no peer Bee yet), CI/CD pipeline design (devops-worker-bee), database schema for a custom metrics store (db-worker-bee), or building custom Kanban tooling in code (react-worker-bee / python-worker-bee).