using-hackinatorlisted

# Using Hackinator ## Overview Hacking in the *original* sense: not breaking in, but **building for the joy of it** and **making the result beautiful**. A hack is a clever, playful, well-crafted solution. This suite has two moods and the techniques behind them. **Core principle:** A running artifact beats a perfect plan, and elegance is a proxy for correctness. Build first, then reveal the simple thing hiding inside what you built. ## The Ethic (what these skills assume) - **Hands-on imperative.** You understand a system by building with it, not by reading about it. - **Beauty is functional.** Elegant code is easier to trust, change, and love. Ugliness is a smell. - **Subtraction is progress.** The best hack removes more than it adds. - **Ship something that runs.** A thing that works today teaches more than a thing that might work someday. - **Delegate, don't drown.** Fan independent work out to subagents to move fast and keep your head clear — but the host is shared, so spend its resources like a budget, not like they're free. - **Track it in the open.** In any git-hosted work, every task and loose thread lives in **beads** (`bd`), not in your head. A thought you don't file is a thought you'll lose. - **Two heads beat one on hard problems.** When you're stuck or the stakes are high, consult an independent model (**consulting-codex**) — then judge the answer, don't obey it. - **Play.** If it isn't a little bit fun, you're doing it wrong. ## The Workflow (the front door