grill-with-docs

Discover and install specialized agent skills from the open ecosystem when users need extended capabilities. Helps identify relevant skills by domain and task when users ask "how do I do X" or "find a skill for X" Provides npx skills find [query] command to search interactively and npx skills add <package> to install from GitHub or other sources Recommends skills based on install count (prefer 1K+), source reputation (official sources like Vercel, Anthropic), and GitHub stars to ensure quality Checks the skills.sh leaderboard first for battle-tested, popular options before running CLI searches

Relentless interviewing skill that stress-tests plans and designs through systematic questioning. Conducts deep-dive questioning across all aspects of a plan, walking through decision trees branch-by-branch until shared understanding is reached Automatically explores the codebase to answer questions where code context is available, reducing redundant back-and-forth Designed for design reviews, architecture validation, and pre-implementation planning where thorough vetting prevents downstream issues

Analyze codebases for architectural friction and propose module-deepening refactors as testability improvements. Explores codebases organically to surface shallow modules, tightly-coupled components, and untested seams rather than following rigid heuristics Applies John Ousterhout's "deep module" principle: small interfaces hiding large implementations for better testability and AI navigability Generates multiple radically different interface designs (minimalist, flexible, caller-optimized, ports & adapters) via parallel sub-agents, then recommends the strongest approach Creates GitHub issue RFCs documenting the problem space, design trade-offs, and refactoring rationale

Test-driven development with vertical slices, behavior-focused tests, and incremental red-green-refactor cycles. Emphasizes integration-style tests that verify behavior through public APIs, not implementation details; tests should survive refactors unchanged Requires vertical slicing (one test → one implementation → repeat) instead of horizontal slicing (all tests first, then all code), preventing brittle, behavior-insensitive test suites Includes planning phase to confirm interface changes, prioritize behaviors to test, and design for testability before writing code Provides refactoring guidelines covering duplication extraction, module deepening, and SOLID principles, applied only after all tests pass