shiftinbits/constellation

This skill should be used when the user asks for a high-level overview of the codebase, "explain the architecture", "what does this codebase look like", "how is this project structured", "what languages are used", or wants a quick mental model of a project's structure and size.

This skill should be used when the user asks "is Constellation working", "check Constellation status", "run a health check", "is the project indexed", "test the connection", or before troubleshooting to confirm whether MCP connectivity, API authentication, and project indexing are healthy.

This skill should be used when the user asks about "Constellation errors", "fix Constellation", "debug Constellation", "Constellation not working", "API connection issues", "indexing problems", "MCP server", "Failed to reconnect", mentions any Constellation error codes (AUTH_ERROR, PROJECT_NOT_INDEXED, etc.), or when Constellation queries fail.

This skill should be used when the user asks to find dead code, unused code, orphaned exports, "what code is never used", "find unused functions/classes/types", or wants to clean up code that is exported but never imported.

This skill should be used when the user asks about a file's dependencies, "what does X import", "what depends on X", "show me the dependency graph", "are there circular dependencies", or wants to map imports/dependents before working on a file.

This skill should be used before any non-trivial code modification to assess the blast radius and risk of the change. Trigger when the user discusses renaming, refactoring, deleting, moving, restructuring, or modifying code. Also trigger when the user asks "what would break if...", "is X safe to remove", or wants to estimate risk before a refactor.