Stop Rebuilding Your Claude Code Setup - Scaffold It Once with Worclaude

Sefa Ertunç — Thu, 16 Apr 2026 20:39:45 +0000

Every time I started a new project with Claude Code, I rebuilt the same .claude/ directory from scratch - agents, commands, skills, hooks, permissions. Copy from the last repo, tweak, fix what broke, repeat.

So I built Worclaude - a CLI that does it in seconds.

One command

npm install -g worclaude
worclaude init

It asks three things: project type, tech stack, which agent categories you want. Then it generates everything.

What you get

26 agents across 6 categories. 6 are universal (plan-reviewer on Opus, test-writer and verify-app on Sonnet, build-validator on Haiku, upstream-watcher for change tracking). 20 more are optional - backend, frontend, DevOps, quality, docs, data/AI. Worclaude recommends agents based on your project type.

18 slash commands covering the full session lifecycle:

/start -> /review-plan -> implement -> /verify -> /commit-push-pr

Plus /upstream-check, /sync, /conflict-resolver, /refactor-clean, /test-coverage, and more.

16 skills with conditional activation. Skills only enter Claude's context when relevant files are touched. A testing skill activates when test files are open, not when you're editing CSS.

8 lifecycle hooks across the full Claude Code event system. SessionStart auto-loads CLAUDE.md, PROGRESS.md, and recent learnings. PostToolUse auto-formats code. PreCompact takes a git snapshot before context compaction. Stop captures [LEARN] blocks from the session. Three profiles: minimal, standard, strict.

Per-stack permissions for 16 languages. Claude stops asking to run npm test or pytest every time.

No runtime dependency

This is the important part. Worclaude generates static markdown and JSON files, then exits. Claude Code reads them natively. There's no daemon, no wrapper, no middleware. Your .claude/ directory is plain files you can read, edit, and commit to git.

Upstream awareness

Claude Code ships updates frequently. Agents, hooks, and commands can break silently when upstream behavior changes. Worclaude includes /upstream-check - a command that fetches live data from 16 Anthropic sources (engineering blog, changelogs, npm releases, GitHub releases, status page) and tells you what changed since your last session.

Built on community patterns

The workflow draws from Boris Cherny's tips (creator of Claude Code at Anthropic), patterns from Affaan Mir's everything-claude-code (Anthropic hackathon winner), Karpathy's coding principles, and community repos like pro-workflow.