Explains codebase architecture and subsystem flows through parallel exploration agents.
npx skills add https://github.com/mmdmcy/fluttAIrbar --skill how-mmdmcy
Please help me install this Agent Skill. Skill: how Source: https://github.com/mmdmcy/fluttAIrbar/tree/main/plugins/pstack/skills/how Command: npx skills add https://github.com/mmdmcy/fluttAIrbar --skill how-mmdmcy
High-intent search queries and answers about installing and using this skill.
Ask a how-style question naming the subsystem, such as how the rate limiter or billing flow works. The skill spawns parallel explorer agents that trace the code paths, then synthesizes their findings into a structured explanation with file references.
Request a critique alongside the explanation. The skill first explains the architecture, then spawns multiple independent critic agents that evaluate it against a rubric covering abstraction fit, data model, boundaries, and evolution readiness.
Yes, placement, ownership, and layering questions are a core use case. The explanation maps where things live and how components connect, giving you the context to decide which package or layer should own new functionality.
No, all explorer, explainer, and critic agents run in read-only mode. They use Glob, Grep, and Read to inspect the code and return findings without making any changes to the codebase.
Simple questions about a single module or narrow function use one agent that explores and explains in a single pass. Complex subsystems spanning multiple files or services trigger 2-4 parallel explorers whose findings are then synthesized.
vvedantbExplore code to produce architectural explanations of codebase subsystems.
adjohnExplains codebase architecture and subsystem flows using parallel explorer and critic agents.
Ramprasad4121Prepare codebases for security review with static analysis and documentation.
videojsWrites concise React component design records documenting non-inferable architectural decisions.
