Claude-kit: Configuration Management System for Claude Code Projects

What claude-kit does
Claude-kit is a configuration management system for Claude Code that handles the entire .claude/ directory lifecycle. It's not a one-time bootstrap tool or static CLAUDE.md generator, but a system that evolves with your projects.
Commands and functionality
The tool provides several commands:
/forge init— Auto-detects your tech stack (15 supported) and generates a complete .claude/ setup including CLAUDE.md, settings.json with deny lists, contextual rules with glob patterns, hooks (block destructive commands, lint on save), 7 specialized subagents, and error tracking./forge audit— Scores your config on a 10-point scale using a 12-item checklist covering security (deny lists, destructive command blocking), quality (rules, lint hooks, agents), and completeness. Missing security items cap your score at 6.0./forge status— Registry dashboard tracking scores across all your projects with trend sparklines./forge bootstrap— Full interactive setup with preview and confirmation for when you want more control./forge sync— Updates configurations without overwriting your custom content, using<!-- forge:section -->markers to separate managed sections from customizations.
Key features
- Stack layering — Multi-stack projects get all matching configs merged automatically (e.g., Python + Docker + Redis + Supabase = 4 layers combined)
- Template sync — Uses markers to separate managed sections from customizations, allowing updates without overwriting your content
- Practices pipeline — Continuous improvement system that captures patterns from sessions, upstream docs, and audits with lifecycle stages: inbox → evaluating → active → deprecated
- 7 subagents — researcher, architect, implementer, code-reviewer, security-auditor, test-runner, session-reviewer — with model routing (haiku/sonnet/opus by task type)
- MCP server templates — Ready-to-use configs for GitHub, Postgres, Supabase, Redis, Slack
- Cross-project registry — Tracks audit scores with history across all managed projects
What it's not
- Not application code — it's all markdown + shell scripts, consumed directly by Claude Code
- Not a CLAUDE.md generator — it manages the entire .claude/ directory lifecycle
- Not a one-shot tool — it bootstraps, syncs, audits, and evolves with your projects
Supported tech stacks
15 stacks are supported: Python/FastAPI, React/Vite/TS, Swift/SwiftUI, Supabase, Docker, GCP Cloud Run, Redis, Node/Express, Java/Spring, AWS Deploy, Go, Data Analysis, DevContainer, Trading, and a hookify framework for custom hooks.
Getting started
git clone https://github.com/luiseiman/claude-kit.git cd claude-kit export CLAUDE_KIT_DIR="$(pwd)" ./global/sync.sh # Then in any project: /forge init
The project is MIT licensed and available on GitHub at https://github.com/luiseiman/claude-kit.
📖 Read the full source: r/ClaudeAI
👀 See Also

Official Kotlin Support for VS Code Now in Alpha — Powered by IntelliJ's Language Server
JetBrains released the official Kotlin extension for VS Code in Alpha, backed by the Kotlin Language Server built on IntelliJ IDEA's code-insight infrastructure. Includes code completion, diagnostics, navigation, quick-fixes, formatting, and project import.

Meta Ads MCP OAuth Works But Most Ad Accounts Not Enabled Yet
Meta Ads MCP OAuth flow works and loads 29 tools, but ads_get_ad_accounts returns is_ads_mcp_enabled: false with a message that the feature is gradually rolling out.

Claude Pulse Browser Extension Surfaces Token Counts, Cache Timers, and Rate Limits on Claude.ai
Claude Pulse is a client-side Chrome extension that adds a real-time dashboard to Claude.ai showing per-message token counts, total context usage, prompt cache expiry timer, and rate limit progress bar. Also includes chat export to Markdown.

LLMs Leak Reasoning into Structured Output Despite Explicit Instructions
A developer building a tool that makes parallel API calls to Claude and parses structured output found that validation models intermittently output reasoning text before corrected content, despite explicit instructions to return only corrected text. The fix involved prompt tightening plus a defensive strip function that runs before parsing.