The idea

✍️ The one page in these docs I wrote by hand — human, not AI.

You’re the architect. cckit is the structural engineer.

You bring the ideas and the shape of the thing. The mechanics that make it stand up — branches, worktrees, PRs, the trail of issues that says why — are what cckit takes care of. The whole idea in one line:

Turn your Git into retrievable, efficient context — using issues, GitHub Projects, and other people’s tools, wired together with a few advanced mechanics.

Where this came from

Over years of building software, the actions cckit automates are the ones I’ve done again and again. They are the development process. I put this toolbelt together while reading about and documenting the process of shipping the very first product of my own — and I wanted to share it.

With the surge of “vibe coders” — people arriving from every background, technical and not — the same problems keep resurfacing, more and more often. cckit is my small answer: pick up some of the discipline of SCRUM-style issue tracking, and carry it into a new era where you can forget the mechanics and become the idea generator, the architect.

Develop software with care. If this gets even a few more people interested in how to build software well, it did its job.

If you’re a vibe coder

Welcome to this world. Be curious, and be kind — that’s how the open-source community works, and it’s how you’ll get the most out of it. To make that easier, every tutorial gives you a “Copy as Markdown” prompt you can paste straight into Claude Code, and each one is labelled Beginner, Intermediate, or Advanced — so you can start exactly where you are and grow from there.

If you already know the mechanics

This should flow for you. Along the way it introduces ideas that are becoming more and more relevant — like parallel agentic development, running a whole wave of issues at once — without getting in your way.

cckit builds cckit

None of this is theoretical. cckit is developed with cckit — every tutorial, feature, and fix on this site went through its own lifecycle: an issue, an isolated worktree, a pull request, a merge. The receipts are public: every issue closed in the repo →. The board is both the plan and the proof.

The invitation

That’s it. You bring the ideas; cckit keeps the memory and runs the machinery. Come in, be interested, and be kind.

---

Built by @jeiemgi · josegtz.com