A specialist skill that analyses a codebase to understand its structure, dependencies, and architecture. This skill should be used at the start of a new project or when onboarding to an existing codebase.
Analyzes codebase structure, dependencies, and architecture using read-only commands. Used at project start or onboarding to map out the codebase before making changes.
/plugin marketplace add nicholasgriffintn/claude-code/plugin install ng-workflow@claude-codeThis skill is limited to using the following tools:
This skill should only use read-only commands and avoid modifying files.
Copy this checklist and use it to track your progress through the analysis process:
Project Analysis Checklist
- [ ] Gather a quick overview of the project by reading the README.md or equivalent documentation.
- [ ] Identify the main programming languages and frameworks used in the codebase.
- [ ] Map out the project structure, including key directories and files.
- [ ] Analyze dependencies by reviewing package management files (e.g., package.json, requirements.txt).
- [ ] Identify core modules and components of the application.
- [ ] Understand the data flow and architecture patterns used in the project.
- [ ] Review any existing tests to understand the testing strategy and coverage.
- [ ] Document any areas of the codebase that may require further investigation or clarification.
Here are some useful commands to help you analyze the codebase:
# List the main files and directories in the project
ls -R
# Check for package management files to identify dependencies
ls | grep -E 'package\.json|requirements\.txt|Pipfile|Gemfile'
# Display the contents of a package management file
cat package.json
cat requirements.txt
# Search for key architecture patterns or components
grep -r 'MVC\|Microservices\|Singleton\|Factory' .
# Identify test files and directories
find . -type f -name '*test*' -o -name '*spec*'
After completing the analysis, document your findings in a structured format. Include sections such as:
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.