levnikolaevich

Profiles runtime performance with CPU, memory, and I/O metrics. Use when measuring bottlenecks before optimization.

Creates slash commands from procedural doc sections. Use when transforming documentation prose into executable commands.

Use when accepted findings require bounded repair changes and a structured repair summary.

Verifies claims in .md files (paths, versions, counts, configs, endpoints) against codebase, cross-checks contradictions. Use when auditing docs accuracy.

Use when installing or verifying this marketplace in Claude and Codex, aligning selected plugins, MCP settings, and Codex execution defaults.

Scaffolds new React projects or restructures monoliths to component-based architecture. Use when setting up frontend structure.

Audits whether one implemented architectural pattern fits project needs and best practices. Use when checking pattern fitness.

Finds code that can be safely deleted: unreachable, unused, obsolete compatibility, and commented-out code. Use when pruning dead code.

Creates design_guidelines.md with WCAG 2.1 compliance and design system docs. Use when project has a frontend.

Checks diagnosability through structured logs, metrics, traces, correlation IDs, and useful log levels. Use when auditing incident visibility.

Configures global exception handling middleware. Use when adding centralized error handling to .NET or Python backends.

Analyzes community health and delegates engagement tasks. Use when managing GitHub issues, discussions, and announcements.