topcat

Provides deep architectural insights into Topcat's implementation including module structure, DAG algorithms, layer system, analysis capabilities, and schema operations. Use when exploring Topcat internals, understanding algorithms, extending functionality, or debugging complex issues.

Guides graph export and visualization in multiple formats. Use when visualizing dependencies, generating documentation, integrating with analysis tools, or creating diagrams for reports.

Guides schema-based organization and analysis for multi-schema database projects. Use when working with multiple schemas, analyzing cross-schema dependencies, or filtering operations by schema.

Guides dependency analysis and safe cleanup operations in Topcat. Use when analyzing dead branches, finding orphans, detecting cycles, cleaning unused files, or integrating with CI/CD pipelines.

Guides testing and debugging of Topcat including running tests, writing new test cases, and debugging issues. Use when working with Topcat's test suite, testing analysis commands, debugging dependency problems, analyzing performance, or setting up continuous integration.

Systematically runs clippy and fixes linting issues following project patterns. Use when running lints, addressing clippy warnings, or improving code quality before commits.

Guides test creation in Topcat following existing patterns for unit tests, integration tests, and test utilities. Use when writing new tests, debugging test failures, or improving test coverage.

Guides writing Rust code in Topcat following project conventions for modules, error handling, documentation, and idioms. Use when implementing new features, adding modules, or refactoring existing code.

Analyzes SQL files to automatically extract and manage dependencies, eliminating manual header maintenance. Use when working with SQL dependency discovery, configuring automatic extraction patterns, or migrating from manual to automatic dependency management in Topcat.

Guides holistic updates to CLAUDE.md maintaining conciseness and clarity. Use when adding project documentation, updating workflows, modifying Claude's behavior, or reorganizing project guidance. Remember CLAUDE.md loads for every interaction.

Guides holistic skill updates through refactoring rather than patching, maintaining quality and conciseness. Use when adding features to existing skills, fixing skill issues, restructuring for clarity, or incorporating user feedback.

Guides the creation of effective Claude Code skills with proper structure, metadata, and progressive disclosure. Use when creating new skills, refactoring existing skills, or reviewing skill effectiveness for Claude Code projects.