Tuning Your Project

Tune fits a project out for agentic work. A coding agent studies your source and your issue history, then assembles a Kit of review lenses, tools, skills, and a project guide, so every future fix lands like the agent already knows the codebase.

Open it from the menu bar (Tune Project…) or the Cockpit’s project menu. It’s the most thorough pass nitpin makes. It runs on your XLarge task model, takes a few minutes, and is worth re-running as the project evolves.

The wizard

Tune is one sheet that deepens through five steps:

1. Pre-flight. Checks that a source repo is linked, the analysis agent is ready, and nothing else is running. Then Analyze (or Check for changes on a re-run).
2. Analyzing. The agent studies your stack, conventions, build commands, and the language of your captured issues. You can Hide the sheet and let it run in the background.
3. Review — your Kit. Every proposed piece appears as a row with a toggle, a plain-English description grounded in your repo, and a recommended tag where deserved. Switch off anything you don’t want, and use Add guidance on any row to steer how it’s built: “keep the context doc short”, “the UX reviewer should care about VoiceOver”.
4. Apply. The accepted rows install, top-down, with live per-row status. Tune validates each generated piece before installing it; anything that can’t pass validation is skipped and says why.
5. Receipt. “Your project is tuned”: what was installed, skipped, or failed, and where it all lives.

Re-running Tune reconciles rather than redoes. It proposes only what’s new or changed, and never silently overwrites something you’ve hand-edited since.

What’s in a Kit

• Reviewers (up to three): project-specific review lenses the fixing agent runs over its own work. Always a correctness lens, optionally a stack lens and a UX lens, each derived from what your issue history shows actually goes wrong. Reviews scale with fix size (trivial fixes skip review entirely) and are advisory: an unresolved objection lowers the fix’s confidence rating rather than blocking it.
• Tools: vetted, pinned developer tools wired into your agent (a code index, a memory runtime, language-server wiring), drawn only from nitpin’s curated catalog.
• Skills: pinned skills for your stack from the official skills registry.
• Context: a project guide. What the app is, the architecture in brief, verified build and test commands, conventions, your vocabulary, and known sharp edges.
• Rubric: what S / M / L / XL actually mean in this repo, so triage sizing matches your reality.

An always-on extra rides along: a terse register that trims agents’ scratch output so dispatched runs spend fewer tokens on narration.

Just for you, or the whole team

On first run you pick where the Kit lives:

• Just for you — stays on this machine; nothing is committed.
• Share with your team — nitpin commits the Kit’s files to your repo so teammates (and their agents) get the same setup. The receipt shows which files were committed; review the diff before you push.