Find the perfect capability for your agent.
Token-efficient codebase navigation through intelligent symbol loading and querying. Use this skill when implementing new features (find existing patterns), exploring codebase structure, searching for components/functions/types, or understanding architectural layers. Reduces token usage by 60-95% compared to loading full files. Layer split enables 50-80% additional backend efficiency.
Gentoo overlay maintenance tools. Use /check-updates to find outdated packages, /update-ebuild to bump versions.
Synchronizes CLAUDE.md navigation indexes and README.md architecture docs across a repository. Use when asked to "sync docs", "update CLAUDE.md files", "ensure documentation is in sync", "audit documentation", or when documentation maintenance is needed after code changes.
Enhanced documentation unified validation (2 UV scripts migrated to builder-skill-uvscript, 3 workflow scripts retained)
Generates Babel configuration for JavaScript transpilation in tests. Creates babel.config.js file.
Execute self-correcting validation workflow. Use when validation fails, tests fail, or build breaks.
Write or update repository devops scripts with this project's conventions. Use when creating or modifying shell scripts in scripts/ or packages/*/scripts.
Analyze and reorganize project file structures, identify dependencies, clean technical debt, and establish architectural patterns. Use when users need to: organize messy codebases, understand file dependencies and import chains, refactor folder hierarchies, identify unused files or circular dependencies, detect cross-file connections, or establish consistent naming conventions and module boundaries for any programming language project.
Guides systematic file refactoring following @j0kz/mcp-agents modular architecture pattern to maintain files under 300 LOC through constants/, helpers/, utils/ extraction with proven results from 2...
[52] EXECUTE. Three-stage refactoring workflow: (1) iterative research of refactor/modularization options, (2) plan + risk/edge-case analysis + Scope150 validation, then implement with tests after user confirmation, and (3) apply Scout105 cleanup protocol. Use when asked to refactor, modularize, or restructure code safely.
Systematic code refactoring skill that transforms complex, hard-to-understand code into clear, well-documented, maintainable code while preserving correctness. Use when users request "readable", "maintainable", or "clean" code, during code reviews flagging comprehension issues, for legacy code modernization, or in educational/onboarding contexts. Applies structured refactoring patterns with validation.
Scan repos for privacy/security risks before making public. Detects PII (emails, names, paths), company-specific terms, and secrets in code and git history. Triggers on 'scan for sharing', 'check before making public', 'privacy review', 'can I share this repo'. Run the scanner, triage findings, guide remediation. (user)
Update .brain/ context files after completing tasks. Use when: updating project context, documenting changes, maintaining activeContext.md, updating systemPatterns.md, tracking session progress, documenting decisions.
Build and update Rainze code using the PRD, tech stack, and module sub-PRDs. Use this when writing Python/Rust for Rainze, aligning with the architecture, method signatures, class/layout definitions, and coding standards under .github/references.
This skill should be used when the user asks to "refactor code", "rename function", "extract method", "reduce complexity", "migrate code", "code migration", "modernize code", "split class", "move code", or mentions code restructuring and refactoring operations.
Validate changes against .agentignore before commit.
This skill should be used when the user asks about "prompt_toolkit Buffer", "Document", "cursor position", "text manipulation", "BufferControl", "text editing", "undo/redo", "selection", "copy paste", or needs to handle text input and manipulation in prompt_toolkit applications.
Create new demo or utility modules following CLY project patterns. Use when adding TUI demonstration modules to modules/demo/ or utility modules to modules/, following Bubbletea/Bubbles conventions with proper Cobra CLI integration.
