claude-ctrl and claude-code-settings
These tools are complements, as the control plane for deterministic Claude code (A) would benefit from best practices for Claude code configuration (B) to ensure optimal setup and management.
About claude-ctrl
juanandresgs/claude-ctrl
The Systems Thinker's Deterministic Claude Code Control Plane
# Technical Summary Enforces deterministic governance over Claude Code through shell-script hooks that intercept every tool call (bash commands, file writes, agent dispatches) and mechanically deny unsafe operations—write-on-main attempts, untested code, undocumented changes—regardless of model context drift. Four specialized agents (Planner, Implementer, Tester, Guardian) divide responsibilities across a self-correcting pipeline, with unified SQLite state (WAL mode) eliminating race conditions in concurrent worktrees. v4.0 reduces token-per-success by 1.4% while maintaining 100% task completion through environment-tiered database safety gates, pre/post-write interception hooks, and compaction-free prompt design.
About claude-code-settings
nokonoko1203/claude-code-settings
Best Practices for Claude Code Configuration
Provides curated configuration templates and workflow guidelines for Claude Code, emphasizing high-impact settings over complexity. Features skills for token-efficient browser automation (Playwright CLI vs. MCP) and defines structured agent team workflows with role separation (design, review, implementation, testing). Includes LSP plugin configurations for accurate code navigation and centralizes MCP server management through symlinked config files for multi-environment deployment.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work