fakoli-crew

Show available fakoli-crew agents and team compositions

Use this agent when you need a thorough code review — line-by-line analysis of code quality, naming, safety, and TypeScript correctness. Reviews as a Staff Engineer at a FAANG company would. Critics report; they don't fix. <example> Context: You've finished implementing a new provider module. user: "Review this code before I merge it." assistant: "I'll use the critic agent to do a full code review of the implementation." </example> <example> Context: You want a senior perspective on a new module. user: "Review this code for TypeScript best practices." assistant: "I'll use the critic agent to evaluate the code against TypeScript best practices." </example> <example> Context: You're checking overall code quality before a release. user: "Do a code review of the fakoli-crew plugin." assistant: "I'll use the critic agent to review the full plugin for code quality issues." </example>

Use this agent when you need design guidance for TypeScript, Python, or Rust — interface design, type system patterns, project structure, error handling, or naming conventions. Auto-detects the project language and applies the matching battle-tested style guide. <example> Context: You're designing a TTS abstraction layer. user: "How should I design an interface for multiple TTS providers?" assistant: "I'll use the guido agent to design a clean, well-typed interface for your TTS providers." </example> <example> Context: You're unsure about your error handling approach. user: "What's the right way to structure errors for this project?" assistant: "I'll use the guido agent to design a proper error hierarchy following idiomatic conventions." </example> <example> Context: You have a package with several modules and need structure advice. user: "How should I structure this package so it's easy to import from?" assistant: "I'll use the guido agent to recommend a clean package structure with proper public API control." </example>

Use this agent when you need documentation that makes people actually want to use a project. Triggers include "improve the README", "rewrite descriptions", "make this appealing", or "better branding". <example> Context: A new plugin was just shipped with a minimal placeholder README. user: Make this README appealing to first-time visitors. assistant: I'll read the plugin source, commands, and existing README, then rewrite it starting with a concrete value proposition, add CI/license badges, and include a copy-paste Quick Start section. </example> <example> Context: The plugin marketplace listing has a generic one-liner description. user: Rewrite the description for the marketplace entry. assistant: Let me read what the plugin actually does — its commands, outputs, and use cases — then write a specific description that tells a developer exactly what problem this solves and what they get, not just "A tool for X". </example> <example> Context: A project has grown and its README still reads like draft notes. user: Better branding for the project. assistant: I'll read all source files, the current README, and any existing docs, then restructure: title with tagline, badges row, 3-line value proposition, install block, features table, commands reference, config section, requirements, and author footer. </example>

Use this agent when you need to maintain or update repository infrastructure. Triggers include "update CLAUDE.md", "fix CI workflows", "update contributor docs", or "sync the registry". <example> Context: Three new agents were added to the plugin and CLAUDE.md still lists only the original five. user: Update CLAUDE.md to reflect the new agents. assistant: I'll read CLAUDE.md, read the new agent files, then update the agent table and any checklists that reference them. I'll also check whether the registry and marketplace.json are in sync. </example> <example> Context: A new required field was added to plugin.json but the contributor checklist doesn't mention it. user: Update contributor docs with the new plugin.json requirement. assistant: I'll read the current contributor docs, the plugin.json schema, and the CI workflow that validates it, then add the new field to the checklist and update the validation step description. </example> <example> Context: The project was restructured and the CI workflow references paths that no longer exist. user: Fix CI workflows after the restructure. assistant: I'll read the current workflow files, map the old paths to new ones using Glob, then update only the paths that actually changed — not a wholesale rewrite. </example>

Use this agent when you need to research an API or service and produce a structured reference document — endpoints, auth, schemas, pricing, rate limits, and code examples. <example> Context: You're adding ElevenLabs TTS support to the plugin. user: "Research the ElevenLabs API for text-to-speech." assistant: "I'll use the scout agent to gather full documentation for the ElevenLabs TTS API." </example> <example> Context: You need to understand what endpoints a service exposes. user: "What endpoints does the OpenAI audio API have?" assistant: "I'll use the scout agent to document the OpenAI audio API endpoints and their schemas." </example> <example> Context: You want structured docs before writing an integration. user: "Document the Google Cloud TTS service before we build the provider." assistant: "I'll use the scout agent to research and write a reference file for the Google Cloud TTS API." </example>

Orchestrate fakoli-crew agents as coordinated teams for complex multi-step projects

Systematic 4-phase debugging for root cause analysis — investigate, analyze patterns, form hypothesis, fix with test