Identify existing codebase patterns (naming conventions, architectural patterns, testing patterns) to maintain consistency. Use when generating code, reviewing changes, or understanding established practices. Ensures new code aligns with project conventions.
/plugin marketplace add rsmdt/the-startup/plugin install team@the-startupThis skill inherits all available tools. When active, it can use any tool Claude has access to.
examples/common-patterns.mdDetect and follow the project's file naming style:
| Pattern | Example | Common In |
|---|---|---|
| kebab-case | user-profile.ts | Node.js, Vue, Angular |
| PascalCase | UserProfile.tsx | React components |
| snake_case | user_profile.py | Python |
| camelCase | userProfile.js | Legacy JS, Java |
Identify the project's verb conventions:
Detect pluralization and specificity patterns:
user vs users vs userList)strName, iCount)_private, #private, mPrivate)Recognize how the codebase separates concerns:
COMMON LAYERING PATTERNS:
- MVC: controllers/, models/, views/
- Clean Architecture: domain/, application/, infrastructure/
- Hexagonal: core/, adapters/, ports/
- Feature-based: features/auth/, features/billing/
- Type-based: components/, services/, utils/
Identify import patterns that reveal architecture:
Recognize how state flows through the application:
Identify how tests are structured:
| Pattern | Structure | Example |
|---|---|---|
| Co-located | src/user.ts, src/user.test.ts | Common in modern JS/TS |
| Mirror tree | src/user.ts, tests/src/user.test.ts | Traditional, Java-style |
| Feature-based | src/user/, src/user/__tests__/ | React, organized features |
Detect the project's test description style:
it('should return user when found')test('getUser returns user when id exists')test_get_user_returns_user_when_foundRecognize Arrange-Act-Assert or Given-When-Then patterns:
Identify import ordering and grouping:
COMMON IMPORT PATTERNS:
1. External packages first, internal modules second
2. Grouped by type (React, libraries, local)
3. Alphabetized within groups
4. Absolute imports vs relative imports preference
Recognize module boundary conventions:
Identify documentation conventions:
examples/common-patterns.md - Concrete examples of pattern recognition in actionThis 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.