기법
Workflows — Techniques
10 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.
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 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.
vibe4g 위클리 구독
엄선한 바이브코딩 인사이트를 매주 목요일에 보내드립니다.
스팸 없음. 언제든 구독 해지.
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.