Load the Context

30 Seconds.

One copy-paste per tool. Loads the full ZABAL Gamez + ZAO ecosystem context (/llms.txt) into your AI harness as the project context. After loading, your tool follows the brand guidelines (no emojis, no em dashes, ZAO palette), knows the tech stack, and can route to the right docs without a fresh fetch.

Pick your tool

Claude Code

project file: CLAUDE.md

curl -L https://zabalgamez.com/llms.txt -o CLAUDE.md

Run in your project root. Next Claude Code session in that folder auto-loads the file. Verify with /skills + /help.

Claude Code skill (alternative - available across all your projects)

user-level skill

mkdir -p ~/.claude/skills/zabal-games && curl -L https://raw.githubusercontent.com/ZAODEVZ/zabalgames/main/.claude/skills/zabal-games/SKILL.md \ -o ~/.claude/skills/zabal-games/SKILL.md

Installs as a Claude Code skill at the user level. Auto-activates whenever Claude detects ZAO / ZABAL Gamez / ecosystem-brand work. Verify with /skill list.

Cursor

project file: .cursorrules

curl -L https://zabalgamez.com/llms.txt -o .cursorrules

Cursor auto-loads .cursorrules on next session in this project. For Cursor's new .cursor/rules/ directory pattern, also drop a copy in .cursor/rules/zabal-games.mdc.

Windsurf

project file: .windsurfrules

curl -L https://zabalgamez.com/llms.txt -o .windsurfrules

Cascade reads .windsurfrules by default for any project that has one.

Aider

conventions file: CONVENTIONS.md + --read flag

curl -L https://zabalgamez.com/llms.txt -o CONVENTIONS.md && aider --read CONVENTIONS.md

The --read flag tells Aider to load the file as read-only context every session. Add to your aider config to make it persistent.

Cline (formerly Claude Dev)

project file: .cline/instructions/zabal-games.md

mkdir -p .cline/instructions && curl -L https://zabalgamez.com/llms.txt -o .cline/instructions/zabal-games.md

Cline auto-loads files in .cline/instructions/ as system context.

Continue.dev

.continue/context-providers config

# Add to ~/.continue/config.json contextProviders: { "name": "url", "params": { "url": "https://zabalgamez.com/llms.txt" } }

Use the URL context provider so Continue auto-fetches the latest. No file to keep in sync.

Any other harness

fetch + paste / save / point

curl -L https://zabalgamez.com/llms.txt -o zabal-games-context.md

Save the file, then point your tool at it however it loads project context. Markdown opens in everything.

After loading - first prompt to send

Drop this into your tool right after loading the context. Confirms it parsed correctly and grounds the agent for your build:

I loaded the ZABAL Gamez / ZAO ecosystem context. Confirm the three brand-guideline rules and one detail you noticed about the WaveWarZ Finals voting protocol. Then ask me what I am building.

If the tool answers correctly (no emojis / no em dashes / naming-glossary rules, plus the WaveWarZ-Base hybrid voting mechanism), the context is loaded and you are ready.

What you just loaded

llms.txt is ~28 KB of dense markdown. It carries:

The ZABAL Gamez format (June workshops / July build / August Finals)
The ZAO ecosystem brand-by-brand (ZAO OS, ZABAL, WaveWarZ, COC Concertz, ZAOstock, ZAO Music, BCZ, FISHBOWLZ, Respect + Fractals)
Tech stack defaults (Next.js 16, Base, Supabase, Farcaster Hubs) + 11 key APIs with auth + cost
Two build paths (adopt a started project or build from scratch) + the 9 adoptable projects
Brand guidelines (non-negotiable): naming glossary, no emojis, no em dashes, color palette, fonts
The submission bar + 4 visibility modes
Voting + judging (WaveWarZ-Base settlement, Respect baseline)
Don't-build-these anti-patterns (8-row table)
Copy-paste code snippets for 9 ZAO rails (Farcaster Hubs, Empire Builder, Hats, Clanker, EAS, Coinflow, Hypersub, Bonfire, Farcaster cast composer)
"What good looks like" quality bar with concrete signals + counter-examples
Links to deeper docs at /research

Read it in browser at /context with per-section copy buttons.

Keep it fresh

The file at zabalgamez.com/llms.txt updates as the canonical state moves. Re-run any of the curl commands above to pull the latest. Snap-shotted into your repo? Cron a weekly re-pull, or use the Continue URL-provider for auto-fresh.