Results for “directory-structure”

Analyzes project folder structures, auto-detects technology stacks, and generates detailed blueprints with naming conventions, file placement patterns, and templates for consistent code organization.

Provides a structured README template for documenting XDG config directories, dotfiles, and script folders, helping users remember the purpose and contents of their local configuration.

Expert C4 Code-level documentation specialist. Analyzes code directories to create comprehensive C4 code-level documentation including function signatures, arguments, dependencies, and code structure.

Analyzes code directories to create comprehensive C4 code-level documentation including function signatures, arguments, dependencies, and code structure.

Creates and manages Architecture Decision Records using the Michael Nygard format, including new ADR creation, retrospective analysis, superseding, deprecating, and index generation.

Enforces system design, project structure, dependency management, error handling, testing, and documentation standards at principal-engineer level.

Expert C4 Code-level documentation specialist. Analyzes code directories to create comprehensive C4 code-level documentation including function signatures, arguments, dependencies, and code structure.

Expert C4 Code-level documentation specialist. Analyzes code directories to create comprehensive C4 code-level documentation including function signatures, arguments, dependencies, and code structure.

Organizes discovered pathway, portal, and theme content into a docs repository by copying new files, resolving duplicates, updating the README, and generating per-portal indexes.

Analyzes code directories to create C4 code-level documentation with function signatures, dependencies, and Mermaid diagrams.

Analyzes code directories to produce C4 code-level documentation with function signatures, dependencies, and structure.

Expert C4 Code-level documentation specialist. Analyzes code directories to create comprehensive C4 code-level documentation including function signatures, arguments, dependencies, and code structure.

Performs deep architectural analysis of a specified module, directory, or feature area by examining structural coupling, data flow, concurrency patterns, risk, and SOLID alignment. Use when the user wants to assess, evaluate, or review the architecture, design quality, dependency structure, coupling, cohesion, or technical debt of an existing part of the codebase. Not for investigating specific bugs, runtime errors, or failures — use investigate. Not for test planning — use automated-test-planning. Not for file-level code review — use code-review. Not for researching open-ended options, prior art, or how something works — use research. Not for designing a new interface or contract — use design-an-api. Not for writing documentation or architectural decision records.