kulmam92

10 mods across 1 repository, 2 stars between them.

cc-best-practices

03

kulmam92/cc-best-practices-marketplace

Plugin Claude Code

Compound engineering: every session leaves your setup smarter. Verify, learn, audit, refactor -- with hooks, rules, and skills that prevent discipline decay.

2 4mo ago A tokens not measured original MIT

bp-audit

06

kulmam92/cc-best-practices-marketplace

Skill Claude CodeCodex

Audit your Claude Code setup health -- CLAUDE.md token budget, rule inventory, duplicate detection, and graduation candidates. Use periodically to keep your setup lean, or before major refactors, after accumulating many rules, or when sessions feel slow or unfocused.

2 4mo ago A 56 tokens original MIT

bp-learn

07

kulmam92/cc-best-practices-marketplace

Skill Claude CodeCodex

Capture a team rule into CLAUDE.md or .claude/rules/. For team knowledge that compounds across the whole team -- use auto-memory for personal learnings instead. Use after code review findings, debugging sessions, incident postmortems, or when Claude makes a repeated mistake that should become a permanent rule.

2 4mo ago A 67 tokens original MIT

bp-refactor

08

kulmam92/cc-best-practices-marketplace

Skill Claude CodeCodex

Safe refactoring protocol with characterization tests. Based on Boris Cherny's 4-step legacy refactoring approach. Use before any refactoring, code migration, API restructuring, or cleanup of legacy code. Always characterize before changing.

2 4mo ago A 49 tokens original MIT

bp-setup

09

kulmam92/cc-best-practices-marketplace

Skill Claude CodeCodex

Interactive setup wizard that configures CLAUDE.md, permissions, hooks, rules, and agents for a new project. Use when adopting the bp- best practices system in a new codebase, setting up Claude Code for a repo for the first time, or when someone asks about configuring hooks, rules, or verification workflows.

2 4mo ago D 69 tokens original MIT

bp-verify

10

kulmam92/cc-best-practices-marketplace

Skill Claude CodeCodex

Run full verification loop after code changes. Verification improves quality 2-3x -- never skip it. Use after implementing a feature, fixing a bug, completing a refactoring chunk, or before committing or creating a PR.

2 4mo ago A 49 tokens original MIT