These examples conform to the Hacky v0.1.2 core and carrier contract.
Ready-to-use Hacky files. Copy a .hacky.json into an AI chat, or
attach the matching .hacky.pdf where file attachments are
supported.
The JSON file is the canonical source. It is compact UTF-8 with exactly four keys and one terminal line feed:
Install the reviewed Python writer directly from the public source tree, then use its command-line executable:
git clone https://github.com/openhacky/hacky.git
python3 -m pip install ./hacky/packages/python
hacky render leo.hacky.json
hacky pdf leo.hacky.jsonThe prepared Python distribution is hackyformat and its import is
hacky. Registry publication is separate from this GitHub release:
from hacky import load, render
pack = load("leo.hacky.json")
print(render(pack))Every file carries a finite 1–99 reply lifetime. The host AI's rules and later explicit user instructions remain higher priority.
| File | Character | Language | Replies | Style |
|---|---|---|---|---|
| leo.hacky.pdf | Leo — quiet, loyal companion | Japanese | 8 | concise |
| vera.hacky.pdf | Vera — dry, precise colleague | English | 12 | analytical |
| rin.hacky.pdf | Rin — quiet, poetic stranger | Japanese | 6 | reflective |
| max.hacky.pdf | Max — energetic idea partner | English | 4 | inventive |
The .hacky.json and .hacky.pdf for each character
contain the same canonical JSON bytes. The PDF is a one-page 1800 × 1800 dot
carrier with only an invisible text payload, so it has no active document
features.
Start with the Hacky v0.1 specification: https://github.com/openhacky/hacky/blob/main/spec/v0.1.md
The public file boundary is intentionally small:
{"hacky":"0.1","name":"Example","turns":4,"instructions":"[HACKY ACTIVATION v0.1]\n...\n\n[HACKY EFFECT]\nWrite one useful reply."}Use the canonical writers in the @openhacky/core JavaScript package or the hackyformat Python package. Pull requests with new, self-contained examples are welcome: https://github.com/openhacky/examples