Claude Skills

This skill provides a quick rollback command for developers who need to revert code changes after a refactoring session. It executes a specific git checkout command targeting a pre-module-refactor branch with a date stamp. Use this when you need to undo recent refactoring work and restore the previous code state.

This skill refactors Python packages by restructuring them into a modular architecture with organized `modules/` directories. It transforms flat package structures into nested modules with mirrored test and documentation layouts. Use it when you need to organize growing Python packages into maintainable, feature-based modules.

This skill validates a module-based refactoring by checking structure, imports, tests, and documentation. It generates a validation report and provides rollback instructions if failures occur. Use it to ensure your refactored codebase maintains integrity before finalizing changes.

This skill executes the third phase of module-based refactoring by creating the new directory structure and moving code according to the migration plan. It handles backup creation via git tagging, sets up discipline-specific module directories across source, tests, docs, and other project areas, and coordinates file relocation with package initialization updates. Use this when you're ready to implement the refactoring plan developed in earlier phases.

This skill creates a structured migration plan for refactoring codebases into modular discipline-based architectures. It generates detailed specifications for reorganizing source code, tests, and documentation into `_core` and discipline-specific modules. Developers use it after Phase 1 analysis to get actionable directory restructuring plans before implementation.

This skill performs the initial analysis phase for discipline-based refactoring by scanning repository structure to identify package names and existing code organization. It spawns an Explore agent to examine directories, domain modules, and functional areas to map current architecture. Use this when beginning a refactoring project to understand existing code organization before restructuring.

This skill orchestrates complex refactoring workflows by delegating execution to specialized sub-skills across analysis, planning, and execution phases. It provides a lean orchestrator that manages the overall refactoring process while keeping implementation details in dedicated skills. Use it when you need a structured, multi-phase approach to code refactoring within Claude Code.

This skill helps developers identify architectural disciplines within a codebase by analyzing key nouns, expertise areas, and logical ownership boundaries. It provides a structured framework using four guiding questions to decompose a monolith into coherent domains. Use it during refactoring to establish consistent naming and organization across source, test, and documentation directories.

This skill defines the core architectural principles for organizing code in a module-based structure. It establishes that all code, documentation, and specifications should be grouped by consistent discipline names within dedicated `modules/` directories. Developers should use this reference when implementing or refactoring a project to ensure a standardized and scalable folder organization.

This skill restructures any codebase into a modular, domain-oriented architecture, organizing code under `src/<pkg>/modules/` and related documents in parallel. It orchestrates subagents like Explore and Plan to analyze, plan, and execute the refactoring autonomously. Use it when you need to systematically reorganize a repository by business discipline for improved maintainability.

This Claude Skill extends mkdocs functionality to include code block titles in documentation. It enables developers to add descriptive titles to code snippets for better organization and readability. Use this sub-skill when you need to present titled code examples in your mkdocs-generated documentation.

This skill adds a warning admonition component to MkDocs documentation, allowing developers to highlight potential issues or important considerations for readers. It creates visually distinct warning boxes with customizable titles and content within markdown files. Use this when you need to alert documentation users about risks, limitations, or critical information in your technical docs.

The mkdocs-tip skill generates "Pro Tip" admonition blocks in MkDocs documentation. It's used to highlight best practices and helpful suggestions for readers within a styled callout format. This is a sub-component of the main mkdocs skill for structuring technical documentation.

This skill enables tabbed code blocks in MkDocs documentation, allowing developers to display multiple code examples in different programming languages within a single collapsible section. It uses a simple markdown syntax with language tabs (like Python, JavaScript, Go) that users can click between. Use this when you need to show equivalent implementations across languages while saving vertical space in your docs.

This skill provides a success notification component for MkDocs documentation, specifically designed to indicate completed actions or successful outcomes. It displays formatted success messages using the `!!! success` directive in documentation. Developers should use it to highlight positive results or confirmations in their MkDocs projects.

This skill provides documentation content for Subsection 1.1 within the mkdocs project structure. It is an internal reference skill used to organize and present specific sections of project documentation. Developers should use it when they need to access or manage this particular subsection of the mkdocs documentation.

This mkdocs sub-skill generates a Mermaid state diagram for documentation. It provides a predefined workflow visualization showing states like Draft, Review, Approved, and Published with their transitions. Use it to quickly embed a standard process diagram into your mkdocs project.

This skill adds sequence diagram generation to MkDocs documentation using Mermaid.js syntax. It enables developers to visualize API interactions, data flows, and system processes directly within their technical documentation. Use it when you need to embed dynamic, maintainable sequence diagrams alongside your MkDocs project code.

This sub-skill provides the reference content for "Section 2" of the mkdocs documentation. It is an internal, read-only module used by the main mkdocs skill to organize its documentation structure. Developers should use the primary mkdocs skill, as this sub-skill is automatically managed and not for direct implementation.

This skill provides curated links to essential MkDocs resources and tools for documentation projects. It includes references to core documentation, popular themes like Material for MkDocs, versioning tools, extensions, and plugin catalogs. Use it when building or maintaining MkDocs-based documentation sites to quickly access key ecosystem resources.

The mkdocs-quote skill enables developers to easily add styled quote blocks to MkDocs documentation using the `!!! quote` syntax. It's used specifically within MkDocs projects to highlight notable quotations with proper formatting. This sub-skill handles the rendering of quote elements as part of the broader mkdocs documentation system.

This skill enables FAQ sections in MkDocs documentation using question admonitions. Developers should use it to create and format frequently asked questions within their project docs. It provides a standardized way to present Q&A content with proper visual styling.

This skill provides a Markdown admonition component for creating highlighted notes in mkdocs documentation. It generates `!!! note` blocks that draw attention to important information readers should notice. Developers should use it when they need to emphasize general information or key points in their technical documentation.

This mkdocs sub-skill automatically adds line numbers to code blocks in documentation. It enables developers to reference specific lines when discussing code examples in their mkdocs projects. The skill activates via the `linenums` attribute in markdown code fences.