Joycraft: Claude Code 하네스를 업그레이드하세요

The craft of AI development. With joy, not darkness. Joycraft is a CLI tool and Claude Code plugin that upgrades your AI development workflow. It installs skills, behavioral boundaries, templates, and documentation structure into any project, taking you from unstructured prompting to autonomous spec-driven development. If you've been using Claude Code (or any AI coding tool) and your workflow looks like this: Prompt → wait → read output → "no, not that" → re-prompt → fix hallucination → re-prompt → manually fix → "ok close enough" → commit ...then Joycraft is for you. This project started as a personal exploration by @maksutovic. I was working across multiple client projects, spending more time wrestling with prompts than building software. I knew Claude Code was capable of extraordinary work, but my process was holding it back. I was vibe coding - and vibe coding doesn't scale. The spark was Nate B Jones' video on the 5 Levels of Vibe Coding. It mapped out a progression I hadn't seen articulated before - from "spicy autocomplete" to fully autonomous development - and lit my brain up to the potential of what Claude Code could do with the right harness around it. Joycraft is the result of that exploration: a tool that encodes the patterns, boundaries, and workflows that make AI-assisted development actually deterministic. Joycraft is simple. It's a set of skills (slash commands for Claude Code) and instructions (CLAUDE.md boundaries) that guide you and your agent through a structured development process: - Levels 1-4: Skills like /joycraft-tune ,/joycraft-new-feature , and/joycraft-interview replace unstructured prompting with spec-driven development. You interview, you write specs, the agent executes. No back-and-forth. - Level 5: The /joycraft-implement-level5 skill sets up the autonomous loop where specs go in and validated software comes out, with holdout scenario testing that prevents the agent from gaming its own tests. StrongDM calls their Level 5 fully autonomous loop a "Dark Factory" - which, albeit a cool name, the world has so much darkness in it right now. I wanted a name that extolled more of what I believe tools like this can provide: joy and craftsmanship. Hence "Joycraft." Dan Shapiro's 5 Levels of Vibe Coding provides the framework: | Level | Name | What it looks like | Joycraft's role | |---|---|---|---| | 1 | Autocomplete | Tab-complete suggestions | - | | 2 | Junior Developer | Prompt → iterate → fix → repeat | /joycraft-tune assesses where you are | | 3 | Developer as Manager | Your life is reviewing diffs | Behavioral boundaries in CLAUDE.md | | 4 | Developer as PM | You write specs, agent writes code | /joycraft-new-feature + /joycraft-decompose | | 5 | Software Factory | Specs in, validated software out | /joycraft-implement-level5 sets up the autonomous loop | Most developers plateau at Level 2. Joycraft's job is to move you up. Joycraft is currently focused on making the Claude Code experience state-of-the-art. Better Codex support is coming. AGENTS.md generation is already included, and deeper integration is on the roadmap. First, install the CLI: npm install -g joycraft Then navigate to your project's root directory and initialize: cd /path/to/your/project npx joycraft init Joycraft auto-detects your tech stack and creates: - CLAUDE.md with behavioral boundaries (Always / Ask First / Never) and correct build/test/lint commands - AGENTS.md for Codex compatibility - Claude Code skills installed to .claude/skills/ :/joycraft-tune Assess your harness, apply upgrades, see your path to Level 5/joycraft-new-feature Interview → Feature Brief → Atomic Specs/joycraft-interview Lightweight brainstorm. Yap about ideas, get a structured summary/joycraft-research Objective codebase research — subagent sees only questions, never the brief/joycraft-design Design discussion checkpoint — ~200-line artifact for human review before decompose/joycraft-decompose Break a brief into small, testable specs/joycraft-add-fact Capture project knowledge on the fly -- routes to the right context doc/joycraft-lockdown Generate constrained execution boundaries (read-only tests, deny patterns)/joycraft-verify Spawn a separate subagent to independently verify implementation against spec/joycraft-session-end Capture discoveries, verify, commit, push/joycraft-implement-level5 Set up Level 5 (autofix loop, holdout scenarios, scenario evolution) - docs/ structure: briefs/ ,specs/ ,discoveries/ ,contracts/ ,decisions/ ,context/ - Context documents in docs/context/ : production map, dangerous assumptions, decision log, institutional knowledge, and troubleshooting guide - Templates including atomic spec, feature brief, implementation plan, boundary framework, and workflow templates for scenario generation and autofix loops Once you reach Level 4, you can set up the autonomous loop with /joycraft-implement-level5 . See Level 5: The Autonomous Loop below. Node.js (npm/pnpm/yarn/bun), Python (poetry/pip/uv), Rust, Go, Swift,