tillerhand weekly downloads statistics

<p align="center"> <picture> <source media="(prefers-color-scheme: dark)" srcset="kit/assets/banner-dark.svg"> <img src="kit/assets/banner-light.svg" alt="TillerHand: AI builds. You steer." width="100%"> </picture> </p> <p align="center"> <a href="kit/CHANGELOG.md"><img alt="Version" src="https://img.shields.io/badge/version-3.64.2-2a78d6?style=flat-square"></a> <a href="LICENSE"><img alt="License: MIT" src="https://img.shields.io/badge/license-MIT-2a78d6?style=flat-square"></a> <img alt="Claude Code" src="https://img.shields.io/badge/Claude%20Code-ready-d97757?style=flat-square"> <img alt="Also Codex and Antigravity" src="https://img.shields.io/badge/also-Codex%20%C2%B7%20Antigravity-5b6577?style=flat-square"> <img alt="Node.js 18+" src="https://img.shields.io/badge/Node.js-18%2B-3c873a?style=flat-square"> </p> <p align="center"> <b>English</b> · <a href="README.tr.md">Türkçe</a> · <a href="https://burakdogrul.github.io/TillerHand/kit/guide.html"><b>Read the guide →</b></a> </p> <p align="center"> <a href="#step-by-step-for-beginners">Step by step</a> · <a href="#quick-start">Quick start</a> · <a href="#existing-project-adopt">/adopt</a> · <a href="#how-it-works">How it works</a> · <a href="#expert-board">Board</a> · <a href="#guardrails">Guardrails</a> · <a href="#commands">Commands</a> · <a href="#license">License</a> </p>

---

TillerHand is a starter kit that takes a product from idea to production and maintenance with Claude Code. The AI writes the code; you make the decisions. At every important step it lays out the options, when each one is the better choice, and what it recommends. An expert board reviews the work, guardrails stop dangerous actions before they happen, and the project always stays in a clean folder structure.

Language first. /start and /adopt open with one question: which language should the AI talk to you in? Turkish, English or any other. From then on questions, answers, reports, the dashboard and the status line come in that language; /language changes it later. Everything the kit ships (commands, rules, agents, hooks, document templates) is written in English, the Turkey add-on included. Turkish interface texts ship in .claude/i18n/tr.json; labels and keys in project files stay English in every language, because the tools read them.

Question-driven	Product, technical, design, data, security and cost decisions come as reasoned options. Design questions come with visual previews.
In your language	The first question is the language. Questions, answers, documents, the dashboard and the status line then come in that language; /language changes it.
Expert board	Product, Architect, Security, UX, Privacy, QA and other members review the plan, each task, each commit and each phase.
A separate agent writes the tests	Acceptance and adversarial tests are written before the code by a separate agent, not the one writing the code, and they start red. The coder can't touch test files, and a test changed by indirect means can't get into a commit. Nothing is called done without proof that it works.
Specs and drift checks	Larger tasks and every bug get a spec of current, expected and must-not-change behavior; if a must-not-change behavior has no test, the gate is red.
Findings reports	The top 20 findings for tech, business, security, UX, performance and legal; scored, with how to fix them.
Guardrails	Secrets, destructive commands, unapproved prod deploys, weakened tests and stray files are stopped before they happen.
Live preview	For UI tasks the dev server is started and desktop and mobile screenshots are taken; /qa runs the acceptance criteria in a real browser.
Launch and after	/release first walks you through hosting, domain, backups and rollback, provider by provider. Web and backend projects get a smoke test against the live site every 3 hours.
Turkey add-on	Optional. Signature checks for iyzico and PayTR notifications come with an adversarial test; the KVKK cross-border transfer, e-Invoice/e-Archive and Turkish İ/ı items each link to a primary source.
Dashboard	dashboard.html: status, what needs attention, decisions, board, findings, quality, operations, usage; commands copy with one click.
Usage-aware	Reads the 5-hour and weekly limits and plans work around them. It warns; it never stops the work.
Sourced facts	Anything that changes (versions, prices, regulations) is checked against a primary source, with link and date.
Rollback	/rollback returns to the last working state; history is kept, unfinished work is saved.
Narrator mode	Optionally explains every change in plain language, as if to someone who doesn't code.
Learns how you work	Picks up how you like to work (tone, questions, reports, code style). Preferences you approve apply to all your projects and stay on your computer.
Model per role	You pick the model and effort for planning, coding, testing, review and docs in a local panel (/models), and for any single job if you want. The panel also shows your usage, with your Claude plan and external models kept apart. Commands no longer stop to ask; each run shows the model in one line. Tests come from a separate agent; for security, payment or data-deleting work, Opus is suggested so they do not share the coding model's blind spots.
Learns from bugs	When the same kind of bug comes back, it proposes one rule to prevent it; the rule is added only if you approve.

Step by step for beginners

You don't need to know how to code. Claude handles git, the terminal and installs; you describe what you want and make the choices.…