PROACTIVELY load this skill when starting work on a new codebase, onboarding, debugging complex issues, auditing/synchronizing AI rule files, or when asked "how does this project work?". Analyzes project structure, tech stack, patterns, and conventions.
Proactively analyzes project structure, tech stack, and architectural patterns when starting work on a new codebase or debugging complex issues. Triggers on new project onboarding, debugging sessions, or when asked "how does this project work?
/plugin marketplace add Git-Fg/thecattoolkit/plugin install git-fg-thecattoolkit@Git-Fg/thecattoolkitThis skill inherits all available tools. When active, it can use any tool Claude has access to.
references/tech-stack-signatures.mdworkflows/architecture-map.mdworkflows/dependency-audit.mdworkflows/quick-scan.mdworkflows/sync-rules.mdAlways establish the high-level structure (directories, entry points, configuration) before diving into implementation details of specific files.
Don't guess the tech stack. Verify it by checking configuration files (package.json, go.mod, pyproject.toml, Dockerfile, etc.).
Look for naming conventions (Controllers, Services, Hooks) and structural patterns (Monorepo, Clean Architecture) to infer intent.
workflows/quick-scan.mdworkflows/architecture-map.mdworkflows/dependency-audit.mdworkflows/sync-rules.mdreferences/tech-stack-signatures.md - Heuristics for identifying languages and frameworksPhase 1: Project Structure
Phase 2: Technology Stack
Phase 3: Architecture Patterns
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.