도구
MCP 서버, 스킬, CLI, 플러그인, 대시보드
38 articlesguard-skills: Claude Code diff에 catch-all 오류·환각 import·HPOS 패턴을 잡는 5개 리뷰 Skill
guard-skills는 Claude Code, Codex, Cursor가 생성한 코드·테스트·문서에 second-pass 리뷰를 수행하는 5개 Skill 패키지입니다. clean-code-guard는 GitClear·USENIX 연구에 근거한 14가지 AI 실패 패턴을 검사하고, woo-guard는 AI가 반복 생성하는 pre-HPOS WooCommerce 코드 패턴을 직접 겨냥합니다.
baoyu-design: What Changes When You Run claude.ai/design Locally in Claude Code
baoyu-design ports the claude.ai/design methodology to Claude Code by detecting the agent environment at runtime and loading a tool substitution table from `references/claude.md`. The design system pipeline — `compile-design-system.mjs` produces static lint config, `import-design-system.mjs` generates a token allowlist as `_ds_prompt.md` — enforces the same constraint at two layers. Neither is optional if you want session-to-session consistency.
CI Smoke Tests for MCP Servers with k6
A small k6/x/mcp workflow shows how to prove an MCP server starts, lists tools, returns expected JSON, and fails CI before an agent depends on it.
Large MCP Inputs Need an Artifact Boundary
The right lesson is not a token-saving trick. It is an MCP interface pattern: upload large files out of band, validate them server-side, and pass only an artifact ID through the model.
Claude Meter's Windows Quota Loop for Claude Code
Claude Meter is not just a taskbar percentage. It is a small local loop: Claude Code credentials, `/api/oauth/usage`, adaptive polling, Windows UI, and conservative failure handling.
vibe4g 위클리 구독
엄선한 바이브코딩 인사이트를 매주 목요일에 보내드립니다.
스팸 없음. 언제든 구독 해지.
Clawdmeter's Local Claude Code Telemetry Loop
Clawdmeter is worth rescuing as a source-backed tool review because it exposes a concrete boundary: OAuth token access, rate-limit polling, BLE transport, ESP32 firmware, and hardware maintenance.
Foundry Mainnet-Fork Skill for Audit PoCs
The useful article is not about real-time Ethereum testing. It is about using a narrow Claude Code skill to stop agents from writing smart contract PoCs that pass locally but fail to prove the finding.
Red Hat Evaluator for Skill Triage in Claude Code
Red Hat's evaluator is useful when a Claude Code setup has grown enough that weak instructions, duplicate skills, unsafe hooks, and vague triggers need evidence before the team deletes or rewrites them.
CLAUDE.md Architecture Ledger with oop-architect
oop-architect deserves rescue as a practical guide to keeping design intent, implementation status, and Claude Code's working context aligned through CLAUDE.md.
Claude Soul Memory Install and Trust Rules
Claude Soul deserves rescue as a field guide for agent memory: install it as a runtime change, verify hooks, separate facts from behavior, and set conflict rules before memory starts steering Claude Code.
CodeBurn Cost Review for Codex and Claude Logs
CodeBurn is worth rescuing as an operating guide for AI coding teams: separate exact usage from estimates, inspect Codex and Claude parsers, review waste findings, and turn costs into local policy rather than billing theater.
Reviewing Claude Code on Steroids for Runtime Safety
Claude Code on Steroids is worth saving as an adoption audit for serious skill packs: inspect the installer, pinning model, startup hook, token dashboard, test scripts, and rollout path before use.
Runtime Contracts in Codex Skill Catalogs
AI Research Skills is worth saving as a source-backed field guide for building serious Claude Code and Codex skill catalogs, not as a generic research automation story.
Use budget-aware-mcp as a Codex Context Gate
The useful story is not a benchmark headline. It is a local MCP server that helps Codex choose source files before spending context on full reads.
Review Agent Logs with claude-replay
claude-replay is not a code-review engine. It is a practical way to turn messy agent transcripts into a reviewable, redacted artifact.
Read Stacklit Before Your Agent Reads Files
Stacklit is worth saving as a tool review when the article explains the generated index, MCP surface, freshness contract, and adoption boundary.
OpenAPI-to-MCP Without Tool Sprawl
Agentify can turn OpenAPI into runnable MCP code and agent-facing files. The real adoption rule is narrower: parse first, generate a small surface, inspect handlers, prune risky endpoints, and test one safe tool.
Implementing File-Cited Debt Audits with Claude Code
The useful article is not a pitch for AI code review. It is a field guide to a Claude Code skill that forces orientation before judgment, cites every concrete finding, and writes TECH_DEBT_AUDIT.md as a repeatable artifact.
Check Claude Code Cap Windows with claude-usage-dashboard
claude-usage-dashboard deserves a rescue because it gives Claude Code Pro and Max users a nearby cap-window signal. The article should frame it as a side-terminal meter with explicit checks, not a billing dashboard or a stable integration.
Test OpenClaude Portable Before It Touches Your Repo
OpenClaude Portable should not be sold as a magic USB coding agent. The source is stronger as a boundary guide: what lives under data/, which scripts touch provider settings, how the local proxy changes Ollama calls, and why the dashboard workdir matters before any repository work starts.
Audit CCS Before Switching Claude Code Providers
CCS can save repeated edits to Claude Code settings, but the useful article is not a convenience pitch. It is a guide to what the script writes, where API keys live, how 1M context is toggled, and what to check before a provider switch becomes part of an agent workflow.
Route Claude Code Through a Local Model Proxy
Claude Model Proxy can route Claude Code and Claude Desktop gateway calls through local model maps, but the useful article is not a provider-switching pitch. It is a checklist for keys, aliases, health checks, status tools, and the point where OpenAI-compatible adapters stop being Claude Code replacements.
Run a Claude Code Cost Audit with Token-Dashboard
Token-Dashboard should not be framed as another cost-saving dashboard. The useful version is a local Claude Code audit workflow that reads ~/.claude/projects/, dedupes streaming snapshots, shows expensive prompts and repeated tool patterns, then tells you what to verify before changing CLAUDE.md or AGENTS.md.
Before Clauditor Stops Claude Code, Check the Handoff
Clauditor should not be published as a guaranteed 62% savings story. The stronger article is about session rotation: when Claude Code history has grown too expensive to keep carrying, how hooks block at the boundary, and how handoff files preserve enough context for a fresh session.
Ground Claude Code Cloudflare Answers with cf-docs-mcp
cf-docs-mcp gives Claude Code and other MCP clients searchable Cloudflare developer docs with source URLs, glossary matches, HyDE-enriched chunks, and deployment instructions. The useful article is a boundary guide: when to use the public endpoint, when to self-host, and how to test answer grounding.
Add Licensed Wolfram Checks to Claude Code with mma-mcp
mma-mcp gives Claude Code and other MCP clients a path to symbolic math, numerical analysis, and visualization through a local Wolfram kernel. The useful story is the first run: license ownership, stdio config, harmless expressions, blocked operations, source-visible logs, and HTTP restraint.
Run HolyClaude as a Local Claude Code Workstation
HolyClaude deserves a magazine rescue because it solves real setup friction for Claude Code, Codex, Playwright, and browser-based development. The adoption decision is about local binding, mounted credentials, Docker capabilities, and permission modes.
Search Codex and Claude Sessions Locally with Chronicle
Chronicle deserves a magazine rescue because it turns scattered local CLI transcripts into a searchable SQLite-backed session browser. The adoption question is not whether it looks convenient, but whether your workflow needs local evidence, provider separation, and one-click resume enough to accept the macOS permissions and signing tradeoffs.
Use Lore MCP for Read-Only Project Docs in Claude Code
Lore deserves a magazine rescue because it gives Claude Code and Codex a practical retrieval layer: local ingest, BM25 search, CLI verification, and six read-only MCP tools. The adoption question is not whether it is private by default, but what knowledge should be indexed and exposed.
Implement Source-Gated Web Research in Claude Code
web-researcher-mcp should be saved as an MCP integration article because it gives agents a source gate, not just a search box. The adoption question is how to restrict sources, handle raw content, and inspect recovery signals before trusting the result.
Measure Claude Code Session Waste with PRISM
PRISM is worth saving because it gives Claude Code users a way to diagnose real sessions after the work is done. The useful article is not a README tour; it is a playbook for deciding what to change in CLAUDE.md and what to leave alone.
Scoped Security Workflows with src-hunter-skill in Claude Code
src-hunter-skill is worth saving because it turns public bug bounty material into a Claude Code workflow with checkpoints. A good article should explain where that structure helps and where an operator must stop the agent.
Configuration Review Guide for MCP Risk in Cross-Code Organizer
The old Claude Code Organizer post should not be dropped. The source now describes Cross-Code Organizer, a local dashboard for auditing what Claude Code and Codex actually load before an agent starts work.
Run a CCGlass Debug Capture for Claude Code and Codex
CCGlass is worth saving because it gives Claude Code and Codex users a way to inspect the requests their agents actually send. The right article is not a dashboard tour; it is a guide to using that visibility without mistaking it for correctness.
Use Material 3 Skill as a Claude Code UI Review Gate
material-3-skill is worth preserving because it turns UI guidance into a Claude Code Skill with concrete files and commands. The useful article is not a feature tour; it is a guide to when that Skill should shape generation and when a human reviewer must check the result.