legioncodeinc
- 175 skills
- 0 followers
- 1 day ago last updated
- ▌ Impeccable Stinger · 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 · 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 · 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 · 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 · 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 · 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 · 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 · 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 · 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).
- ▌ Status Page Stinger · legioncodeinc bundlePublic status page specialist: platform selection, incident communication templates, subscriber notifications, compliance. Use when setting up or auditing a status page.
- ▌ Electron App Stinger · legioncodeinc bundleElectron application engineering for process boundaries, preload APIs, IPC, sandboxing, packaging, updates, and desktop verification. Use for Electron app implementation or review.
- ▌ Font Loading Stinger · legioncodeinc bundleProduction-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; the 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).
- ▌ MCP Protocol Stinger · legioncodeinc bundleMCP protocol authority for The Hive - builds and audits MCP servers and tool contracts against the Model Context Protocol spec and @modelcontextprotocol/sdk. Covers tool vs resource vs prompt design, zod input schemas (incl. the zod v3/v4 SDK trap), stdio vs HTTP transport, JSON-RPC framing and error semantics, capability negotiation, auth for remote/HTTP servers (API keys, bearer, OAuth 2.1), testing, and registering a server in Claude Code, Cursor, Codex, and Cowork. Includes a worked example (the Hivemind server). Activate for \\\"audit this MCP server\\\", \\\"add a tool\\\", \\\"is this schema right?\\\", \\\"stdio or HTTP?\\\", \\\"JSON-RPC error code?\\\", \\\"tool vs resource\\\", \\\"why does zod v4 break the schema?\\\", \\\"add auth to my MCP server\\\", \\\"register this in Claude Code/Cursor/Codex/Cowork\\\". Do NOT activate for credential/OAuth storage (security-worker-bee), process sandboxing/TLS (ci-release-worker-bee), or backend datastore internals (the relevant data-layer worker-bee).
- ▌ Neon Drizzle Stinger · legioncodeinc bundleNeon Postgres and Drizzle ORM on SvelteKit/Vercel: connections, schema, migrations, branching, query patterns, pgvector, RLS, and migrating off Supabase. Use for any Neon or Drizzle task.
- ▌ Telegram Bot Stinger · legioncodeinc bundleTelegram Bot specialist: Bot API (up to 10.0 / May 2026 including guest mode and managed bots), grammY v1.x (TypeScript, recommended) and aiogram 3.x (Python), webhook vs long-polling decision with quantitative thresholds, Telegram Mini Apps initData validation (HMAC-SHA256 + Ed25519), Telegram Stars payments (mandatory for digital goods in 2026), inline mode, and MTProto escalation via Telethon/TDLib. Invoke when building a new bot, debugging webhook delivery, wiring Mini Apps, implementing payments, or deciding between frameworks. Do NOT invoke for the Mini App frontend UI (react-worker-bee), hosting/CI beyond bot-specific concerns (devops-worker-bee), or external payment processor integrations beyond Telegram Payments (payments-worker-bee).
- ▌ UX UI Svelte Stinger · legioncodeinc bundleThe Svelte 5 + SvelteKit UI enforcement and implementation skill for the OSPRY SvelteKit apps (portal, web, wl). Owns shadcn-svelte 1.x (built on Bits UI v2 + Melt UI), Tailwind v4, the @theme token bridge to the existing PRD-071 design tokens, and the white-label brand contract. Use whenever a PR touches a .svelte file's markup or styling, when adding a shadcn-svelte component, when wiring Tailwind v4 utilities, when bridging an existing CSS custom property into @theme, when verifying an agency brand flows through a component, or when the user says \\\"add a Button\\\", \\\"copy in this shadcn-svelte component\\\", \\\"convert this bespoke style to Tailwind\\\", \\\"does the white-label still work\\\", or \\\"is this on-brief\\\". Do NOT use for the React ux-ui-svelte-stinger's domain (apps/cms Payload chrome) or for bootstrapping a brand-new design system from scratch.
- ▌ Vector Store Stinger · legioncodeinc bundleDesigns, reviews, and heals vector and embedding storage - schema/column design, index selection (HNSW vs IVFFlat, distance operators), hybrid lexical+vector search, migrations, dataset versioning. Neon plus pgvector plus Drizzle is the primary option for this stack; Deep Lake and Qdrant / managed services remain documented alternatives with a selection matrix. Use when the user says \\\"design this vector table\\\", \\\"which index should this use\\\", \\\"pgvector or Deep Lake or Qdrant\\\", \\\"is this HNSW config right\\\", \\\"wire pgvector into this Drizzle schema\\\", \\\"we need a new embedding column\\\", \\\"how do we heal a missing column\\\", \\\"vector or hybrid search here\\\", or when `vector-store-worker-bee` is invoked. Do NOT use for PRD authoring (library-worker-bee), TypeScript data-access consumption (typescript-node-worker-bee), security audits (security-worker-bee), or recall / embedding retrieval pipelines (retrieval-worker-bee, embeddings-runtime-worker-bee).
- ▌ Cold Outreach Stinger · legioncodeinc bundleOutbound 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.
- ▌ Design System Stinger · legioncodeinc bundleBootstraps 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-svelte-worker-bee`'s job.
- ▌ MCP Tool Docs Stinger · legioncodeinc bundleDocuments MCP tools, TypeScript APIs, and CLIs honestly: schema, output, side effects, examples, doc-to-code sync. Use when writing or auditing tool/API/CLI docs.
- ▌ Retrospective Stinger · legioncodeinc bundleEquips retrospective-worker-bee to run retrospectives that actually change behavior: format selection (Start/Stop/Continue, 4Ls, sailboat, mad/sad/glad, DAKI, Starfish, and more), psychological safety pre-check (Edmondson scale), facilitation playbooks, async retro design, and action-item follow-through discipline. Use when the user says \\\"run a retro\\\", \\\"plan our retrospective\\\", \\\"which retro format should we use\\\", \\\"our retros produce no change\\\", \\\"help with action items from the retro\\\", \\\"how do we do an async retro\\\", or \\\"our team needs better retrospectives\\\". Do NOT use for incident postmortems (different cadence and audience), sprint planning, OKR-setting, or daily standup facilitation.
- ▌ Shadcn Svelte Stinger · legioncodeinc bundleThe shadcn-svelte library itself for any Svelte project: CLI, copy-in model, anatomy, registry, theming, forms, upgrades. Not OSPRY's design system on portal/web/wl (ux-ui-svelte-stinger owns that).
- ▌ Terminal Bash Stinger · legioncodeinc bundleTerminal productivity specialist - Bash/Zsh/Fish configuration, modern CLI tools (ripgrep, fd, fzf, bat, eza, zoxide), shell scripting best practices, dotfile architecture, tmux/Zellij setup, and just/make task automation. Use when the user says \\\"improve my dotfiles\\\", \\\"review this shell script\\\", \\\"set up tmux\\\", \\\"modern CLI tools\\\", \\\"bash best practices\\\", \\\"just vs make\\\", or \\\"help me with my terminal setup\\\". Do NOT use for CI/CD pipelines running in containers (ci-release-worker-bee) or TypeScript/Node build and packaging (typescript-node-worker-bee).
- ▌ Code Forensics Stinger · legioncodeinc bundleForensic 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 Pr Stinger · legioncodeinc bundleCode 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).
- ▌ Elevenlabs API Stinger · legioncodeinc bundleElevenLabs API integration for speech, voices, streaming, webhooks, usage, and key boundaries. Use for ElevenLabs API implementation, review, or troubleshooting.
- ▌ Readme Writing Stinger · legioncodeinc bundleAuthors, audits, and restructures README files so they convert visitors into users. Apply when the user says \\\"write a README\\\", \\\"audit my README\\\", \\\"make my README better\\\", \\\"README for this project\\\", \\\"README-driven development\\\", or when starting a new project and the README does not exist yet. Also apply when badges are broken or missing, the quickstart is not copy-paste runnable, or the user wants to differentiate between an OSS and an internal tool README. Do NOT apply for full documentation site architecture (library-worker-bee), per-entity code extraction (wiki-worker-bee), or CI badge pipeline wiring (ci-release-worker-bee).
- ▌ AI Coding Tools Stinger · legioncodeinc bundleAI coding tool advisor for Cursor, Claude Code, Aider, Cline, Windsurf, Devin, and Bolt. Use when picking, comparing, or configuring an AI coding tool, or debugging one that misbehaves.
- ▌ Chrome Chromium Stinger · legioncodeinc bundleChrome DevTools Protocol and Chromium development for remote debugging, profiles, protocol inspection, source builds, and browser-engine diagnosis. Use for Chrome or Chromium engineering.
- ▌ Crm Integration Stinger · legioncodeinc bundleCRM 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).
- ▌ Cron Scheduling Stinger · legioncodeinc bundleScheduled-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.
- ▌ Lifecycle Email Stinger · legioncodeinc bundleWrites evidence-grounded hot and warm lead follow-up emails. Use for lead classification, sequences, cadence, suppression, QA, and measurement. Not for cold outreach or support tickets.
- ▌ React To Svelte Stinger · legioncodeinc bundleReact-to-Svelte 5 porting: hooks-to-runes translation, TanStack Router to SvelteKit, RTK Query and Radix conversion, contract-first port waves. Use when porting React components or dashboards.
- ▌ Runbook Writing Stinger · 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 · 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 · 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 · 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 · 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 · 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 · 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 · 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 · 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 · 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 · 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 · 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 · legioncodeinc bundlePlaywright and Puppeteer automation for deterministic browser tests, debugging, downloads, screenshots, and browser lifecycle control. Use for browser automation work.
- ▌ Discovery Research Stinger · 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 · 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 · 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 · 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 · 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 · 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 · 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 · 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 · 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 · 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 · 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 · 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 · 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 · 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 · 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 · 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 · 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 · 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 · 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 · 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 · 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 · 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 · 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 · 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 · 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 · 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 · 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 · 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 · legioncodeincPlaceholder stinger shipped inside the Hive reference plugin skeleton, showing where a real plugin-bundled skill lives. Not a working stinger on its own.