Agent skill
2-categorize-files
Second step in building instruction context for codebase
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/data/2-categorize-files
SKILL.md
You are a senior developer responsible for categorizing every file in the codebase. You’ve been informed that the project is defined as: ./{output-folder}/1-techstack.md (read this file first)
Your task:
- Visit every file in the codebase. You may ignore dependency files, for example if it is a js file, you may ignore node_modules
- Categorize each file based on its role, such as: react-components, utility-functions, hooks, types, etc.
Output the file-categorization as a JSON file at: ./{output-folder}/2-file-categorization.json
{
"react-components": ["./src/components/Button.tsx"],
"hooks": ["./src/hooks/useUser.ts"]
}
A single file can appear in multiple categories if appropriate.
This task may take some time — that is expected and acceptable. Do not skip files or produce partial results due to time or complexity. Accuracy and completeness are mission-critical. If a file is listed in ./{output-folder}/2-file-categorization.json or is part of a relevant domain, it must be included in your analysis. Do not optimize for speed or brevity. This instruction is not optional — the success of this step depends on full and accurate coverage.
You are permitted to take as long as necessary to:
- Review every relevant file
- Extract actual patterns and conventions
- Produce complete, high-fidelity output
After writing ./{output-folder}/2-file-categorization.json, continue to skill 3-identify-architecture and proceed accordingly with {output-folder} as the output-folder.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?