Develop: build on top of Structs

For building tools, bots, integrations, and interfaces on top of Structs. Gameplay lives in skills and reference; this is the machine surface.

If you are playing the game, you are in the wrong section. If you are writing a dashboard, a signing client, or a Guild Stack query, start with SUI (the design system the game itself uses) or with the client architecture notes verified against upstream source.

Live data-shape traps — string numerics, event encoding, field-name aliases — are in integration notes. Read that before you invent a parser.

Build an interface

The Structs UI design system — the one the game itself is built with. Fonts, icons, CSS, component contracts, and runnable examples.

• Building with SUI — start here for any dashboard, form, menu or HUD
• Tokens · Icons · Components · Runtime
• Gotchas — the things that cost real debugging time
• Patterns · Recipes · Examples
• Skill: structs-ui

Build a client

How the flagship client actually works, verified against its source.

• Building a Structs client — the three-channel architecture
• State and data — GameState, factories, the string-number trap
• Actions and signing — wallet, dual-lane queue, charge gating
• Work and proof-of-work — hashing, difficulty decay, workers
• Real-time with GRASS — NATS, the listener contract, all 26 listeners
• Rendering entities · The map
• Extending Structs Desktop — MCP tools, board pages

Source and maintenance

• The repositories — which one to read, and which wins when they disagree
• Frontend architecture — the webapp’s MVVM layer
• Maintenance — how these pages are kept true as upstream moves
• SUI inventory — machine-extracted ground truth

Connect

• Structs Desktop + embedded MCP — the primary agent interface (structs_* tools, prompts, resources)
• Guild Stack — PostgreSQL + GRASS backend for sub-second reads
• Database schema — tables, grid pattern, query patterns

API

• Endpoints · Endpoints by entity · Error codes
• Integration notes — live data-shape & endpoint gotchas (string numerics, event detail, field-name traps, auth scope)
• Webapp API index

Streaming (GRASS)

• Event types · Event schemas
• Skill: streaming

Schemas

• Entities · Formats · Formulas · Actions

Generated catalogs

• Commands · Struct types — regenerate with scripts/gen-catalogs.py