Skip to content

harelix/Klotz

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

1 Commit
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Klotz

Claude Code is powerful out of the box — but it's dramatically better when it knows your project. Most people never set that up because the configuration is scattered across files they've never heard of.

Klotz fixes that. Type /klotz, answer one question, and your project is configured. Come back later with /klotz-practices and it'll suggest the next improvement. Over time you build up a setup that makes Claude genuinely better at helping you — without ever reading a docs page.

Install

curl -fsSL https://raw.githubusercontent.com/harelix/klotz/main/install.sh | bash
Manual install
git clone https://github.com/harelix/klotz.git ~/.claude/claude-code-bootstrap
ln -s ~/.claude/claude-code-bootstrap/skills/klotz ~/.claude/skills/klotz
ln -s ~/.claude/claude-code-bootstrap/skills/klotz-practices ~/.claude/skills/klotz-practices

Usage

/klotz — first-time setup

Open Claude Code in any project and type /klotz.

Klotz scans your project — language, framework, test runner, directory structure — and asks you one question: "What does this project do?"

From your answer and what it detected, it creates two files:

  • CLAUDE.md — tells Claude what your project is, how to run it, how to test it, and what the key directories are. This loads automatically every time you start a conversation.
  • .claude/settings.json — controls what Claude can do without asking. Read files? Freely. Run your tests? Freely. Delete things or push to git? It'll ask first.

That's it. Two files, two minutes. Claude Code now understands your project.

/klotz-practices — ongoing improvement

Run this whenever you're ready to go further. Klotz looks at what's configured, compares it to your project, and suggests one thing to improve — then stops.

The progression it walks you through, one step at a time:

Step What it suggests What it creates
1 A coding rule specific to your language .claude/rules/*.md — rules Claude follows when writing code
2 A specialist agent for your project type .claude/agents/*.md — a code reviewer, security checker, or debugger Claude can call on
3 A workflow shortcut for something you do often .claude/skills/*/SKILL.md — a slash command you can run anytime
4 A refinement to an existing config file Sharpens vague rules, updates stale info, tightens permissions

Each run teaches one concept by doing it with you. Run it again when you're ready for the next one.

Update

~/.claude/claude-code-bootstrap/install.sh

How it works

There is no application code. Klotz is a pair of Claude Code skills — markdown files that tell Claude what to do. A shell script handles fast project detection. Claude does the thinking.

Both skills use context: fork, which means they run in an isolated conversation and don't add to the context of your working session. When the skill finishes, the files it created stay on disk but the conversation cost disappears.

Requirements

  • Claude Code installed and working
  • A project directory (can be empty, works best with existing code)

Contributing

Issues and PRs welcome. See CONTRIBUTING.md.

License

MIT

About

Stop chatting with Claude Code and start engineering with it. Progressive setup, one step at a time.

Resources

License

Contributing

Stars

0 stars

Watchers

0 watching

Forks

Releases

No releases published

Packages

 
 
 

Contributors

Languages