Menu
Shared configuration patterns for project setup commands. Provides security hooks, Claude framework structure templates, and framework detection patterns used across multiple setup commands.
Initialize Claude Code framework infrastructure for any project
Simplification and readability techniques. Use when writing for broad audiences or simplifying complex content. Covers active voice, short sentences, jargon elimination, and accessibility principles from the Plain Language Movement.
Hierarchical content structure - answer first, then supporting arguments, then details
Narrative structure for complex topics - Situation, Complication, Question, Answer
API authentication patterns including JWT, OAuth 2.0, API keys, and session-based auth. Covers token generation, validation, refresh strategies, security best practices, and when to use each pattern. Use when implementing API authentication, choosing auth strategy, securing endpoints, or debugging auth issues. Prevents common vulnerabilities like token theft, replay attacks, and insecure storage.
Docker image optimization patterns including multi-stage builds, layer caching, security hardening, and size reduction techniques. Use when building Docker images, optimizing container size, improving build performance, or implementing Docker security best practices. Reduces image sizes by 70-90% and build times by 50-80%.
| name | shared-setup-patterns |
| description | Shared configuration patterns for project setup commands. Provides security hooks, Claude framework structure templates, and framework detection patterns used across multiple setup commands. |
Purpose: Common configuration patterns and templates shared across all project setup commands.
Used by: /setup:python, /setup:javascript, /setup:existing, /setup:explore, /setup:user
Token Impact: Provides ~1,700 tokens of shared templates loaded once, avoiding duplication across 5+ commands (saves ~3,200 tokens through reuse).
This skill contains ONLY patterns shared by multiple setup commands:
Language-specific templates (Python, JavaScript, etc.) are kept inline in their respective commands.
Located: templates/security_hooks.json
Comprehensive security and quality hooks configuration:
Used by: ALL setup commands that create projects
Located: templates/claude_framework/
Templates for .claude/ directory structure:
structure.md - Directory layout and purposememory_templates/ - project_state.md, dependencies.md, conventions.md, decisions.mdwork_structure.md - Work directory organizationUsed by: ALL setup commands
Located: templates/framework_detection.md
Patterns for auto-detecting:
Used by: /setup:existing, /setup (if dispatcher exists)
Commands reference this skill in frontmatter:
skills: [shared-setup-patterns]
Then access specific templates:
templates/security_hooks.jsontemplates/claude_framework/ templatestemplates/framework_detection.mdOnly truly shared content lives here. Language-specific templates (Python pyproject.toml, JavaScript package.json) stay inline in their respective commands to avoid skill overhead for single-use templates.
This keeps each command self-contained while sharing common infrastructure patterns.