워크플로우
설정, 기법, 최적화, 연동
20 articlesWhen a Claude Code File Hook Should Die
The useful story is not a markdown hook that saves tokens. It is a 228-run retraction that teaches Claude Code teams when a hook should be killed, narrowed, or replaced by one instruction.
Audit mcp-token-saver Before It Gates Claude Code
The rescue angle is simple: real 5h and 7d usage can be a better gate than token estimates, but only if the MCP, prompt protocol, credential path, and stale repo docs are checked first.
Audit Kagi Session2API MCP Before Sharing Account Access
The useful article is not that Kagi search can be made free for MCP clients. It is how to test a session-token MCP without mistaking it for a normal API key.
Claude Code Control Surface Audit
A practical audit turns Claude Code commands, memory, MCP, Skills, settings, and hooks into a runbook a team can verify.
agent-dispatch as a Cross-Project Claude Code Router
The useful article is not about generic productivity. It is about when cross-repo delegation gives an agent the right local context, and when it only adds cost, risk, and confusion.
vibe4g 위클리 구독
엄선한 바이브코딩 인사이트를 매주 목요일에 보내드립니다.
스팸 없음. 언제든 구독 해지.
Claude Code Runbooks for Permission and Scope Control
ShipWithAI's Claude Code course is worth rescuing when it becomes a set of local team runbooks, not another list of course modules.
Using gstack for AI Workflow Boundaries in Claude Code
gstack is worth saving as a source-backed field guide for adopting a full Claude Code workflow stack without confusing skill count, productivity claims, or team hooks with proof of fit.
Run AIS-OS as a Claude Code Operating System
AIS-OS is worth saving as a field guide for Claude Code operators who need context, connections, capability planning, and a cadence before they add more agents.
Run Claude Agent Tools in Vercel Sandbox
Vercel Sandbox is useful for Claude Managed Agents when the team reviews the webhook control plane, snapshot runner, network policy, and credential brokering together.
Run Parallel Agents in Git Worktrees
parallel-agent-worktree-skill is worth saving as an operating guide for Codex and Claude Code teams that want multiple agents without letting them trample the same checkout.
Test the Facts Your Agents Read with ctxharness
ctxharness turns selected claims in agent instruction files into repo checks: paths, package scripts, versions, rule globs, hooks, token budgets, and stale context signals.
Use Vibe Coding Security as a Pre-Launch Gate
Vibe Coding Security is worth saving because it gives Claude Code and Codex users concrete pre-launch checks: RLS SQL, NEXT_PUBLIC_ bundle scans, prompt-injection searches, rate-limit review, and React XSS inspection.
Claude Octopus Setup Guide for Read-Only Code Review Agents
Claude Octopus should not be saved as generic multi-agent enthusiasm. The practical version is a safe setup guide: create one read-only reviewer MCP tool, prove tool limits and timeline evidence, then add reports, budgets, test writers, and only later a coordinator.
Audit CLAUDE.md Hierarchies Before Cutting Context
please-optimize-my-claude deserves a magazine rescue because it is not another generic token tip. It audits the CLAUDE.md hierarchy, shows what Claude actually sees, and gives teams a safer path before deleting standing instructions.
Use GodModeSkill for Lineage-Gated Code Review
GodModeSkill should not be published as generic AI review hype. The useful article is a field guide to lineage-gated review: when Claude Code should fan work out to Codex, Gemini, and OpenCode, how quorum works, and where the orchestration cost is justified.
Run a CLAUDE.md Break-Even Test for Claude Code
claude-token-efficient deserves a magazine rescue because it frames CLAUDE.md as a small operating surface for output control. The right article is not a savings headline; it is a guide to when concise rules beat their own input-token overhead.
Set Claude Code Memory Boundaries with Mnemo
Mnemo deserves a real article because it gives Claude Code recall, write, delete, and procedure tools. The adoption question is what should become memory, what should stay in CLAUDE.md, and what must never be captured.