Claude Code Project Setup Pack · Free · v5

Answer three questions,

and the folder is a project

Use Claude Code's own native mechanisms to turn a folder into a project that knows your working conventions, has clear sections, and ships with one reusable procedure. Set up in one pass.

What's inside
  • CLAUDE.md A working-conventions block (language, work type, explanation style + 2 ground rules), appended after your existing content — never overwritten
  • Skill One reusable procedure — code-review or decision-record, pick one, written to the official .claude/skills/ — ready to use
  • Folders Five working folders: work / archive / library / log / inbox — plain descriptive names, no number prefixes
  • Interview 3 questions via AskUserQuestion (language / work type / explanation style) — click, no free-typing
  • No symlink The procedure lives in the in-repo official skills dir and travels with the repo — never touches ~/.claude/
  • Official All native Claude Code mechanisms — no memory system, no takeover of your global setup
  • Updates Version updates pushed to the GitHub repo — no sales pitches
How it works

Paste, say one line, set up in one pass

Paste cc/init.md into a fresh Claude Code chat, say "Run LUCE setup", and it walks you through:

  1. 01/
    Environment check

    Reads your environment first (OS, existing CLAUDE.md, git repo) and prints what it found — touches nothing

  2. 02/
    Three questions

    Conversation language / what this folder is for / your preferred explanation style, via AskUserQuestion — click, no typing

  3. 03/
    Write conventions + add a procedure

    Appends working conventions to CLAUDE.md (existing content untouched), then writes one reusable procedure into the official .claude/skills/ — no symlink

  4. 04/
    Create folders, wrap up

    Creates work / archive / library / log / inbox, prints a wrap-up, done

Set up in one pass. Open a new chat, type your chosen procedure name, or just tell Claude what you want — it already knows this folder's conventions.

Not for you if

Three honest misfits

  1. 01/ People expecting a no-prompt magic stack — you still need to make judgments
  2. 02/ Heavy users with a mature workspace setup — this will feel too basic
  3. 03/ Teams wanting enterprise configuration — see Studio
FAQ

Design, safety, exits

  1. 01/ How is this different from the paid Starter Pack?

    The paid Starter Pack ($49) is a stack-agnostic workflow template collection (30+ prompts, 7 SOPs). The Claude Code Project Setup Pack is the tool-setup layer: it uses native mechanisms to turn a folder into a project with working conventions. Two different layers.

  2. 02/ Will running this lock me into anything?

    No. The output is plain markdown plus your own folders and skill — all native Claude Code mechanisms. Take it anywhere, modify it, or throw it away.

  3. 03/ I already have a CLAUDE.md — will it be overwritten?

    No. On install it reads your existing CLAUDE.md first and appends a dated working-conventions block at the end. Existing content is untouched. Re-running just appends another dated section.

  4. 04/ Does it touch my ~/.claude/ hidden setup?

    No. The reusable procedure is written straight into the in-repo .claude/skills/ (Claude Code's official location for project skills); it travels with the repo, needs no symlink, and touches no hidden config.

  5. 05/ Why Claude Code? What if I use CodeX?

    There is a separate CodeX Project Setup Pack. Same folder structure; the difference is the conventions file (AGENTS.md) and CodeX's own native mechanisms.