nk-dev-practices

Cole Kennedy's Claude Code Plugin System

Modular, composable plugins for development workflows across all projects.

Overview

This plugin system provides:

• Personal plugins - Reusable development practices across all projects
• Project-specific plugins - Auto-installed when working in specific repos
• Skill-based activation - Claude automatically uses relevant skills based on context
• Command shortcuts - Quick access to common workflows

Personal Marketplace

Location: ~/claude-plugins/

Available Plugins

nk-dev-practices

Core development philosophy and practices.

Skills:

• critical-thinking - Linus Torvalds mindset, self-skepticism, red-team analysis
• tdd-workflow - Test-Driven Development, Red-Green-Refactor cycle
• tcr-practice - Test && Commit || Revert for baby-step programming
• no-permission-asking - Maintain momentum without unnecessary permission requests

Commands:

• /tcr-setup - Set up TCR for current project

nk-aws-kubernetes

AWS profile and kubectl context management.

Skills:

• aws-judge-setup - Automatic AWS/kubectl configuration for Judge platform

Commands:

• /judge-context - Set up AWS and kubectl context for Judge work

nk-go-development

Go-specific TDD patterns and testing.

Skills:

• go-tdd-patterns - Table-driven tests, testify usage, mock patterns

Commands:

• /go-test-single - Run single Go test by name

nk-devops-tools

Helm, ArgoCD, Vault best practices.

Skills:

• helm-practices - Dependency management, chart development
• argocd-management - GitOps workflows, never manual kubectl
• vault-secrets - Initialization, unsealing, External Secrets Operator

Commands:

• /disk-cleanup - Free 240GB+ from Minikube build cache

Installation

1. Add Personal Marketplace

/plugin marketplace add ~/claude-plugins

2. Install Personal Plugins

/plugin install nk-dev-practices@nkennedy-personal
/plugin install nk-aws-kubernetes@nkennedy-personal
/plugin install nk-go-development@nkennedy-personal
/plugin install nk-devops-tools@nkennedy-personal

3. Project-Specific Plugins

Project plugins (like Judge team plugins) auto-install when you:

1. Have the project repo in your trust list
2. The project has .claude/settings.json configured

Usage

Skills Auto-Activate

Skills automatically activate based on context:

• Working in Go → go-tdd-patterns activates
• Writing GraphQL → Judge graphql-conventions activates
• Using Helm → helm-practices and argocd-management activate
• Always active: critical-thinking, tdd-workflow, no-permission-asking

Commands Are Explicit

Use slash commands when you need them:

• /tcr-setup - Set up Test && Commit || Revert
• /judge-context - Configure AWS/kubectl for Judge
• /go-test-single TestName - Run specific test
• /disk-cleanup - Free Minikube disk space

Project-Specific Plugins

Judge Team Marketplace

Location: ~/proj/judge/.claude-plugins/

Auto-installs when working in Judge repo with these plugins:

judge-platform

• GraphQL conventions (PascalCase operations, make generate)
• Dapr workflow patterns (deterministic orchestrators, idempotent activities)
• Build/test/lint commands

judge-compliance

• Compliance API patterns (frameworks, controls, directives, policies)
• SSP generation with native Dapr activities
• GRC document management

judge-helm-agents

• helm-implementor agent - Make production-ready Helm changes
• helm-reviewer agent - Audit charts for anti-patterns

judge-pair-programming

• Git commit conventions (lowercase, conventional commits)
• XP workflow (Red-Green-Refactor, completion checklist)

Philosophy

Composability

Mix personal + project plugins:

Personal plugins (always active)
  + nk-dev-practices (critical thinking, TDD, TCR)
  + nk-go-development (Go testing patterns)
  + nk-devops-tools (Helm, Vault, ArgoCD)

Project plugins (when in Judge repo)
  + judge-platform (GraphQL, Dapr)
  + judge-compliance (SSP, OSCAL)
  + judge-helm-agents (Helm implementor/reviewer)
  + judge-pair-programming (Git, XP workflow)

Modularity

Each plugin is independent and focused:

• Install only what you need
• Disable plugins per-project
• Version plugins independently

Team Sharing

Project plugins checked into git:

• Team automatically gets same configuration
• Consistent practices across team
• Version-controlled and documented

Directory Structure

~/claude-plugins/                          # Personal marketplace
├── .claude-plugin/
│   └── marketplace.json
├── nk-dev-practices/
│   ├── .claude-plugin/plugin.json
│   ├── skills/
│   │   ├── critical-thinking/SKILL.md
│   │   ├── tdd-workflow/SKILL.md
│   │   ├── tcr-practice/SKILL.md
│   │   └── no-permission-asking/SKILL.md
│   ├── commands/
│   │   └── tcr-setup.md
│   └── README.md
├── nk-aws-kubernetes/
├── nk-go-development/
└── nk-devops-tools/