tinklisted

# Tink Tink helps Claude cast the smallest useful harness, materialize it as run state, and start the work. It keeps the active harness/tool set small because too many tools can hurt performance, and it can suggest small habit-aware calibrations from observed signals. ## Core philosophy Tink is one self-growing skill, not a pile of commands and not a skill recommendation list. It should: 1. understand the task, 2. write a small task contract, 3. choose the smallest effective harness/tool set, 4. replace heavy harnesses when the current stage or token budget makes them harmful, 5. build or synthesize a narrow harness when none fits, 6. apply it only after approval, 7. create `.tink/current/` run state before deeper work, 8. execute the first safe step after approval, 9. verify the promised checks, 10. avoid repeating the same mistake, 11. remember reusable lessons only after approval, 12. keep the harness set small by purging or honing it over time. ## Command surface Use only these commands: - `/tink:setup`: configure language, scope, git tracking, and hook policy. - `/tink:cast`: main path. Quick-triage the request first (simple and safe tasks start immediately without ceremony); otherwise choose/build/synthesize a harness, run Stitch, create run state, start work, and propose reusable learning. Long plans (3+ steps) end every response with a progress bar block. - `/tink:verify`: run the checks promised in `.tink/current/contract.json` and record evidence. - `/tink:list