Loading...
Loading...
Found 16 Skills
Srcwalk is the agent's code navigator: one tree-sitter CLI for repo maps, token-aware large-file reads, symbol search, callers/callees, deps, impact checks, and precise drill-ins. Use it before raw reads or grep for code-structure work. Run `srcwalk guide` first. Must use! It is the installed binary's source of truth.
Create or modify a konsistent.json configuration file that enforces structural conventions in a TypeScript codebase. Use when the user wants to enforce consistent code structure, validate exports/imports across files, ensure directories contain required files, enforce naming patterns, add/remove/update convention rules, configure case map overrides for acronyms or special casing (kebabToPascalMap, kebabToCamelMap), or troubleshoot why konsistent is reporting violations. Triggers on: "konsistent", "konsistent.json", "enforce conventions", "structural consistency", "consistent exports", "consistent structure", "code conventions config", "add convention", "update convention", "fix konsistent errors", "case map", "case override", "acronym casing".
Clean Architecture + DDD + Hexagonal - Atoll Tourisme. Use when designing architecture or reviewing code structure.
Suggest refactoring opportunities to improve code structure and maintainability. Use when improving code design or reducing complexity.
Analyze an existing codebase with parallel mapper agents, creating codebase documentation, understanding brownfield projects, or mapping code structure. Triggers include "map codebase", "analyze codebase", "create project context", "document codebase", "understand code", and "codebase map".
Structure Python so LLMs can understand it in 50 lines.
Analyze Rust project structure using LSP symbols. Triggers on: /symbols, project structure, list structs, list traits, list functions, 符号分析, 项目结构, 列出所有, 有哪些struct
Expert C4 Code-level documentation specialist. Analyzes code directories to create comprehensive C4 code-level documentation including function signatures, arguments, dependencies, and code structure. Use when documenting code at the lowest C4 level for individual directories and code modules.
Generates project context (code structure + architecture intent). Use when starting sessions, understanding codebase structure, onboarding to a project, after major refactoring, or delegating complex work to agents.
Analyzes code architecture and structure — layer violations, circular dependencies, god objects, anemic domain models, missing boundaries, directory structure issues, and configuration problems. Generates severity-scored findings with fix prompts. Trigger phrases: "architecture review", "structure check", "layer analysis", "god class".
Analyzes file-level import dependencies and generates interactive vis-network HTML report. Use when visualizing dependency graphs, analyzing import structure, checking circular dependencies, or understanding module relationships.
Run an extremely strict maintainability review for abstraction quality, giant files, and spaghetti-condition growth. Use for a thermo-nuclear code quality review, thermonuclear review, deep code quality audit, or especially harsh maintainability review.