@cregis-dev/cckit 0.4.1 → 0.6.1

package/templates/plugins/claude-code-setup/skills/claude-automation-recommender/references/skills-reference.md

@@ -1,408 +0,0 @@
-# Skills Recommendations
-
-Skills are packaged expertise with workflows, reference materials, and best practices. Create them in `.claude/skills/<name>/SKILL.md`. Skills can be invoked by Claude automatically when relevant, or by users directly with `/skill-name`.
-
-Some pre-built skills are available through official plugins (install via `/plugin install`).
-
-**Note**: These are common patterns. Use web search to find skill ideas specific to the codebase's tools and frameworks.
-
----
-
-## Available from Official Plugins
-
-### Plugin Development (plugin-dev)
-
-| Skill | Best For |
-|-------|----------|
-| **skill-development** | Creating new skills with proper structure |
-| **hook-development** | Building hooks for automation |
-| **command-development** | Creating slash commands |
-| **agent-development** | Building specialized subagents |
-| **mcp-integration** | Integrating MCP servers into plugins |
-| **plugin-structure** | Understanding plugin architecture |
-
-### Git Workflows (commit-commands)
-
-| Skill | Best For |
-|-------|----------|
-| **commit** | Creating git commits with proper messages |
-| **commit-push-pr** | Full commit, push, and PR workflow |
-
-### Frontend (frontend-design)
-
-| Skill | Best For |
-|-------|----------|
-| **frontend-design** | Creating polished UI components |
-
-**Value**: Creates distinctive, high-quality UI instead of generic AI aesthetics.
-
-### Automation Rules (hookify)
-
-| Skill | Best For |
-|-------|----------|
-| **writing-rules** | Creating hookify rules for automation |
-
-### Feature Development (feature-dev)
-
-| Skill | Best For |
-|-------|----------|
-| **feature-dev** | End-to-end feature development workflow |
-
----
-
-## Quick Reference: Official Plugin Skills
-
-| Codebase Signal | Skill | Plugin |
-|-----------------|-------|--------|
-| Building plugins | skill-development | plugin-dev |
-| Git commits | commit | commit-commands |
-| React/Vue/Angular | frontend-design | frontend-design |
-| Automation rules | writing-rules | hookify |
-| Feature planning | feature-dev | feature-dev |
-
----
-
-## Custom Project Skills
-
-Create project-specific skills in `.claude/skills/<name>/SKILL.md`.
-
-### Skill Structure
-
-```
-.claude/skills/
-└── my-skill/
-    ├── SKILL.md           # Main instructions (required)
-    ├── template.yaml      # Template to apply
-    ├── scripts/
-    │   └── validate.sh    # Script to run
-    └── examples/          # Reference examples
-```
-
-### Frontmatter Reference
-
-```yaml
----
-name: skill-name
-description: What this skill does and when to use it
-disable-model-invocation: true  # Only user can invoke (for side effects)
-user-invocable: false           # Only Claude can invoke (for background knowledge)
-allowed-tools: Read, Grep, Glob # Restrict tool access
-context: fork                   # Run in isolated subagent
-agent: Explore                  # Which agent type when forked
----
-```
-
-### Invocation Control
-
-| Setting | User | Claude | Use for |
-|---------|------|--------|---------|
-| (default) | ✓ | ✓ | General-purpose skills |
-| `disable-model-invocation: true` | ✓ | ✗ | Side effects (deploy, send) |
-| `user-invocable: false` | ✗ | ✓ | Background knowledge |
-
----
-
-## Custom Skill Examples
-
-### API Documentation with OpenAPI Template
-
-Apply a YAML template to generate consistent API docs:
-
-```
-.claude/skills/api-doc/
-├── SKILL.md
-└── openapi-template.yaml
-```
-
-**SKILL.md:**
-```yaml
----
-name: api-doc
-description: Generate OpenAPI documentation for an endpoint. Use when documenting API routes.
----
-
-Generate OpenAPI documentation for the endpoint at $ARGUMENTS.
-
-Use the template in [openapi-template.yaml](openapi-template.yaml) as the structure.
-
-1. Read the endpoint code
-2. Extract path, method, parameters, request/response schemas
-3. Fill in the template with actual values
-4. Output the completed YAML
-```
-
-**openapi-template.yaml:**
-```yaml
-paths:
-  /{path}:
-    {method}:
-      summary: ""
-      description: ""
-      parameters: []
-      requestBody:
-        content:
-          application/json:
-            schema: {}
-      responses:
-        "200":
-          description: ""
-          content:
-            application/json:
-              schema: {}
-```
-
----
-
-### Database Migration Generator with Script
-
-Generate and validate migrations using a bundled script:
-
-```
-.claude/skills/create-migration/
-├── SKILL.md
-└── scripts/
-    └── validate-migration.sh
-```
-
-**SKILL.md:**
-```yaml
----
-name: create-migration
-description: Create a database migration file
-disable-model-invocation: true
-allowed-tools: Read, Write, Bash
----
-
-Create a migration for: $ARGUMENTS
-
-1. Generate migration file in `migrations/` with timestamp prefix
-2. Include up and down functions
-3. Run validation: `bash ~/.claude/skills/create-migration/scripts/validate-migration.sh`
-4. Report any issues found
-```
-
-**scripts/validate-migration.sh:**
-```bash
-#!/bin/bash
-# Validate migration syntax
-npx prisma validate 2>&1 || echo "Validation failed"
-```
-
----
-
-### Test Generator with Examples
-
-Generate tests following project patterns:
-
-```
-.claude/skills/gen-test/
-├── SKILL.md
-└── examples/
-    ├── unit-test.ts
-    └── integration-test.ts
-```
-
-**SKILL.md:**
-```yaml
----
-name: gen-test
-description: Generate tests for a file following project conventions
-disable-model-invocation: true
----
-
-Generate tests for: $ARGUMENTS
-
-Reference these examples for the expected patterns:
-- Unit tests: [examples/unit-test.ts](examples/unit-test.ts)
-- Integration tests: [examples/integration-test.ts](examples/integration-test.ts)
-
-1. Analyze the source file
-2. Identify functions/methods to test
-3. Generate tests matching project conventions
-4. Place in appropriate test directory
-```
-
----
-
-### Component Generator with Template
-
-Scaffold new components from a template:
-
-```
-.claude/skills/new-component/
-├── SKILL.md
-└── templates/
-    ├── component.tsx.template
-    ├── component.test.tsx.template
-    └── component.stories.tsx.template
-```
-
-**SKILL.md:**
-```yaml
----
-name: new-component
-description: Scaffold a new React component with tests and stories
-disable-model-invocation: true
----
-
-Create component: $ARGUMENTS
-
-Use templates in [templates/](templates/) directory:
-1. Generate component from component.tsx.template
-2. Generate tests from component.test.tsx.template
-3. Generate Storybook story from component.stories.tsx.template
-
-Replace {{ComponentName}} with the PascalCase name.
-Replace {{component-name}} with the kebab-case name.
-```
-
----
-
-### PR Review with Checklist
-
-Review PRs against a project-specific checklist:
-
-```
-.claude/skills/pr-check/
-├── SKILL.md
-└── checklist.md
-```
-
-**SKILL.md:**
-```yaml
----
-name: pr-check
-description: Review PR against project checklist
-disable-model-invocation: true
-context: fork
----
-
-## PR Context
-- Diff: !`gh pr diff`
-- Description: !`gh pr view`
-
-Review against [checklist.md](checklist.md).
-
-For each item, mark ✅ or ❌ with explanation.
-```
-
-**checklist.md:**
-```markdown
-## PR Checklist
-
-- [ ] Tests added for new functionality
-- [ ] No console.log statements
-- [ ] Error handling includes user-facing messages
-- [ ] API changes are backwards compatible
-- [ ] Database migrations are reversible
-```
-
----
-
-### Release Notes Generator
-
-Generate release notes from git history:
-
-**SKILL.md:**
-```yaml
----
-name: release-notes
-description: Generate release notes from commits since last tag
-disable-model-invocation: true
----
-
-## Recent Changes
-- Commits since last tag: !`git log $(git describe --tags --abbrev=0)..HEAD --oneline`
-- Last tag: !`git describe --tags --abbrev=0`
-
-Generate release notes:
-1. Group commits by type (feat, fix, docs, etc.)
-2. Write user-friendly descriptions
-3. Highlight breaking changes
-4. Format as markdown
-```
-
----
-
-### Project Conventions (Claude-only)
-
-Background knowledge Claude applies automatically:
-
-**SKILL.md:**
-```yaml
----
-name: project-conventions
-description: Code style and patterns for this project. Apply when writing or reviewing code.
-user-invocable: false
----
-
-## Naming Conventions
-- React components: PascalCase
-- Utilities: camelCase
-- Constants: UPPER_SNAKE_CASE
-- Files: kebab-case
-
-## Patterns
-- Use `Result<T, E>` for fallible operations, not exceptions
-- Prefer composition over inheritance
-- All API responses use `{ data, error, meta }` shape
-
-## Forbidden
-- No `any` types
-- No `console.log` in production code
-- No synchronous file I/O
-```
-
----
-
-### Environment Setup
-
-Onboard new developers with setup script:
-
-```
-.claude/skills/setup-dev/
-├── SKILL.md
-└── scripts/
-    └── check-prerequisites.sh
-```
-
-**SKILL.md:**
-```yaml
----
-name: setup-dev
-description: Set up development environment for new contributors
-disable-model-invocation: true
----
-
-Set up development environment:
-
-1. Check prerequisites: `bash scripts/check-prerequisites.sh`
-2. Install dependencies: `npm install`
-3. Copy environment template: `cp .env.example .env`
-4. Set up database: `npm run db:setup`
-5. Verify setup: `npm test`
-
-Report any issues encountered.
-```
-
----
-
-## Argument Patterns
-
-| Pattern | Meaning | Example |
-|---------|---------|---------|
-| `$ARGUMENTS` | All args as string | `/deploy staging` → "staging" |
-
-Arguments are appended as `ARGUMENTS: <value>` if `$ARGUMENTS` isn't in the skill.
-
-## Dynamic Context Injection
-
-Use `!`command`` to inject live data before the skill runs:
-
-```yaml
-## Current State
-- Branch: !`git branch --show-current`
-- Status: !`git status --short`
-```
-
-The command output replaces the placeholder before Claude sees the skill content.

package/templates/plugins/claude-code-setup/skills/claude-automation-recommender/references/subagent-templates.md

@@ -1,181 +0,0 @@
-# Subagent Recommendations
-
-Subagents are specialized Claude instances that run in parallel, each with their own context window and tool access. They're ideal for focused reviews, analysis, or generation tasks.
-
-**Note**: These are common patterns. Design custom subagents based on the codebase's specific review and analysis needs.
-
-## Code Review Agents
-
-### code-reviewer
-**Best for**: Automated code quality checks on large codebases
-
-| Recommend When | Detection |
-|----------------|-----------|
-| Large codebase (>500 files) | File count |
-| Frequent code changes | Active development |
-| Team wants consistent review | Quality focus |
-
-**Value**: Runs code review in parallel while you continue working
-**Model**: sonnet (balanced quality/speed)
-**Tools**: Read, Grep, Glob, Bash
-
----
-
-### security-reviewer
-**Best for**: Security-focused code review
-
-| Recommend When | Detection |
-|----------------|-----------|
-| Auth code present | `auth/`, `login`, `session` patterns |
-| Payment processing | `stripe`, `payment`, `billing` patterns |
-| User data handling | `user`, `profile`, `pii` patterns |
-| API keys in code | Environment variable patterns |
-
-**Value**: Catches OWASP vulnerabilities, auth issues, data exposure
-**Model**: sonnet
-**Tools**: Read, Grep, Glob (read-only for safety)
-
----
-
-### test-writer
-**Best for**: Generating comprehensive test coverage
-
-| Recommend When | Detection |
-|----------------|-----------|
-| Low test coverage | Few test files vs source files |
-| Test suite exists | `tests/`, `__tests__/` present |
-| Testing framework configured | jest, pytest, vitest in deps |
-
-**Value**: Generates tests matching project conventions
-**Model**: sonnet
-**Tools**: Read, Write, Grep, Glob
-
----
-
-## Specialized Agents
-
-### api-documenter
-**Best for**: API documentation generation
-
-| Recommend When | Detection |
-|----------------|-----------|
-| REST endpoints | Express routes, FastAPI paths |
-| GraphQL schema | `.graphql` files |
-| OpenAPI exists | `openapi.yaml`, `swagger.json` |
-| Undocumented APIs | Routes without docs |
-
-**Value**: Generates OpenAPI specs, endpoint documentation
-**Model**: sonnet
-**Tools**: Read, Write, Grep, Glob
-
----
-
-### performance-analyzer
-**Best for**: Finding performance bottlenecks
-
-| Recommend When | Detection |
-|----------------|-----------|
-| Database queries | ORM usage, raw SQL |
-| High-traffic code | API endpoints, hot paths |
-| Performance complaints | User reports slowness |
-| Complex algorithms | Nested loops, recursion |
-
-**Value**: Finds N+1 queries, O(n²) algorithms, memory leaks
-**Model**: sonnet
-**Tools**: Read, Grep, Glob, Bash
-
----
-
-### ui-reviewer
-**Best for**: Frontend accessibility and UX review
-
-| Recommend When | Detection |
-|----------------|-----------|
-| React/Vue/Angular | Frontend framework detected |
-| Component library | `components/` directory |
-| User-facing UI | Not just API project |
-
-**Value**: Catches accessibility issues, UX problems, responsive design gaps
-**Model**: sonnet
-**Tools**: Read, Grep, Glob
-
----
-
-## Utility Agents
-
-### dependency-updater
-**Best for**: Safe dependency updates
-
-| Recommend When | Detection |
-|----------------|-----------|
-| Outdated deps | `npm outdated` has results |
-| Security advisories | `npm audit` warnings |
-| Major version behind | Significant version gaps |
-
-**Value**: Updates dependencies incrementally with testing
-**Model**: sonnet
-**Tools**: Read, Write, Bash, Grep
-
----
-
-### migration-helper
-**Best for**: Framework/version migrations
-
-| Recommend When | Detection |
-|----------------|-----------|
-| Major upgrade needed | Framework version very old |
-| Breaking changes coming | Deprecation warnings |
-| Refactoring planned | Architectural changes |
-
-**Value**: Plans and executes migrations incrementally
-**Model**: opus (complex reasoning needed)
-**Tools**: Read, Write, Grep, Glob, Bash
-
----
-
-## Quick Reference: Detection → Recommendation
-
-| If You See | Recommend Subagent |
-|------------|-------------------|
-| Large codebase | code-reviewer |
-| Auth/payment code | security-reviewer |
-| Few tests | test-writer |
-| API routes | api-documenter |
-| Database heavy | performance-analyzer |
-| Frontend components | ui-reviewer |
-| Outdated packages | dependency-updater |
-| Old framework version | migration-helper |
-
----
-
-## Subagent Placement
-
-Subagents go in `.claude/agents/`:
-
-```
-.claude/
-└── agents/
-    ├── code-reviewer.md
-    ├── security-reviewer.md
-    └── test-writer.md
-```
-
----
-
-## Model Selection Guide
-
-| Model | Best For | Trade-off |
-|-------|----------|-----------|
-| **haiku** | Simple, repetitive checks | Fast, cheap, less thorough |
-| **sonnet** | Most review/analysis tasks | Balanced (recommended default) |
-| **opus** | Complex migrations, architecture | Thorough, slower, more expensive |
-
----
-
-## Tool Access Guide
-
-| Access Level | Tools | Use Case |
-|--------------|-------|----------|
-| Read-only | Read, Grep, Glob | Reviews, analysis |
-| Writing | + Write | Code generation, docs |
-| Full | + Bash | Migrations, testing |

package/templates/plugins/claude-md-management/.claude-plugin/plugin.json

@@ -1,9 +0,0 @@
-{
-  "name": "claude-md-management",
-  "description": "Tools to maintain and improve CLAUDE.md files - audit quality, capture session learnings, and keep project memory current.",
-  "version": "1.0.0",
-  "author": {
-    "name": "Anthropic",
-    "email": "support@anthropic.com"
-  }
-}