Claude-native multi-model routing — dispatch each task to the right Claude model tier (Fable judgment · Opus orchestrate/review + hard build · Sonnet build · Haiku volume) via model-pinned subagents. Use when routing a Claude task by model or reasoning effort, consulting the advisor at a commitment boundary, or…
Highest-intelligence read-only advisor (Fable 5). Consult at commitment boundaries — before an architecture / migration / API-contract / large-refactor decision, or when a problem has resisted two attempts. Returns a verdict, not a survey. Never writes code.
Fast read-only search/exploration lane (Haiku 4.5). Use for broad fan-out — locate code, map naming conventions, gather files across a large tree, summarize or classify at volume. Returns conclusions, not file dumps. Never writes.
Hard-build lane (Opus 5) — the write lane for escalated, uncertain, or reasoning-heavy implementation and root-cause debugging. Use when a change is hard as code (gnarly logic, a non-trivial algorithm, a stubborn bug) or when the implementer (Sonnet) lane has failed the same task twice. Writes code and proves it.…
Standard implementation worker (Sonnet 5) — the build lane. Use for normal feature/bugfix implementation and moderate-reasoning multi-file changes where the approach is already decided. Writes code and proves it with tests.
Strong read-only reviewer / synthesizer (Opus 5). Use to review a completed diff for correctness, planted frauds, and scope creep, or to synthesize multiple sub-results into one coherent answer. Cites file:line. Returns a VERIFIED / VERIFIED WITH CAVEATS / REFUTED verdict. Never writes code.
Skills and agents for Claude Code — visual verification, shareable HTML artifacts, arXiv research intake, model routing, deck and theme systems, and specialist advisor agents.
Highest-intelligence read-only advisor (Fable 5). Consult at commitment boundaries — before an architecture / migration / API-contract / large-refactor decision, or when a problem has resisted two attempts. Returns a verdict, not a survey. Never writes code.
Brand strategist for identity systems, visual/voice consistency, and positioning. Use when reviewing or defining brand expression across landing pages, decks, and docs — advisory + brand-guideline deliverables.
Multi-platform content strategist: editorial calendars, campaign copy, brand storytelling, SEO-aware content. Use for blog posts, release announcements, social copy, and content plans.
Postgres-focused query and schema tuning advisor: EXPLAIN analysis, indexing strategy, N+1 elimination, partitioning, connection pooling. Use for fleet DB work — slow queries, migration index decisions, schema design reviews.
Developer advocate for DX audits, technical content, community engagement, and adoption narratives. Use for developer-facing announcements, tutorials with adoption framing, DX reviews of onboarding flows, and conference/demo material.
Fast read-only search/exploration lane (Haiku 4.5). Use for broad fan-out — locate code, map naming conventions, gather files across a large tree, summarize or classify at volume. Returns conclusions, not file dumps. Never writes.
Hard-build lane (Opus 5) — the write lane for escalated, uncertain, or reasoning-heavy implementation and root-cause debugging. Use when a change is hard as code (gnarly logic, a non-trivial algorithm, a stubborn bug) or when the implementer (Sonnet) lane has failed the same task twice. Writes code and proves it.…
Identity and access domain advisor: OAuth2/OIDC, SSO, SCIM, WebAuthn, multi-tenant RBAC, session and token design. Use for multi-tenant SaaS authz work — reviewing authorization flows, token lifecycles, or tenant-scoping designs.
Standard implementation worker (Sonnet 5) — the build lane. Use for normal feature/bugfix implementation and moderate-reasoning multi-file changes where the approach is already decided. Writes code and proves it with tests.
Advisor for production multi-agent system design: topology selection, context management across agents, inter-agent trust, failure recovery, HITL gating, agent observability. Use when designing or reviewing autonomous agent lanes, orchestration scripts, or agent-team patterns.
Read-only research analyst — deep-reads ONE arXiv paper's LaTeX source and returns a typed relevance verdict against the current project. Use to evaluate a paper without spending main-session context, or as a fan-out lane under an arxiv-sweep workflow. Cites file:line for every claim about the codebase and never…
Simulated-user cognitive walkthrough reviewer: steps through a UI/page as defined personas, applying CRO and usability frameworks to find friction. Use to review specs-dashboard views, landing pages, or docs flows against the reading-UX north star.
Creation-side orchestrator for anything you have to present. Takes "I need to present X to Y (at Z, in N minutes)" and delivers the finished piece — picks the surface (house deck / HTML artifact / pptx / HyperFrames video / slideshow), applies the design-kit theme the context calls for and asks which font pairing…
Strong read-only reviewer / synthesizer (Opus 5). Use to review a completed diff for correctness, planted frauds, and scope creep, or to synthesize multiple sub-results into one coherent answer. Cites file:line. Returns a VERIFIED / VERIFIED WITH CAVEATS / REFUTED verdict. Never writes code.
Search relevance advisor for Elasticsearch/OpenSearch: index/analyzer design, BM25 tuning, query DSL, relevance evaluation. Use for fleet OpenSearch work — index mappings, search quality, analyzer choices.