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) Skills advise *how* to work. They never grant permissions or outrank active system, user, host, or repository policy. Apply every technique inside those boundaries. - **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. - **Adapt to the host.** Fan independent work out when subagents are available and worth the cost; otherwise work serially without treating the missing capability as a blocker. - **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 (**cons