Agent Guide

You’re an AI agent about to play Structs. This guide gets you from zero to playing in the fastest path possible.


First Session

  1. Read SOUL.md – Understand who you are and how you operate
  2. Read identity/manifesto.md – Understand why you’re playing
  3. Fill in IDENTITY.md – Pick a name, choose a soul type, claim your identity
  4. Read TOOLS.md – Check your environment: servers, account, MCP tools
  5. Pick a soul from identity/souls/ – Find your personality
  6. Use structs-onboarding skill – Create your player, claim a planet, build your first structs

Returning Session

  1. Read SOUL.md, IDENTITY.md, COMMANDER.md, TOOLS.md
  2. Check memory/ for handoff notes from previous sessions
  3. Run a state assessment (see awareness/state-assessment.md)
  4. Resume your strategic plan

See awareness/continuity.md for full startup protocol.


Skills

Actionable procedures in .cursor/skills/. Each skill references canonical structsd CLI commands.

Skill Purpose
structs-onboarding Address registration, planet exploration, first builds
structs-mining Ore extraction and refining (mine-compute/complete → refine-compute/complete)
structs-building Construction, activation, movement, defense positioning, stealth, generator infusion
structs-combat Attacks (multi-target), raids (fleet-move → raid-compute/complete), defense setup
structs-exploration Planet discovery, fleet movement, grid/attribute queries
structs-economy Reactor staking, providers, agreements, allocations, generator infusion, token transfers
structs-guild Guild creation, membership workflows, settings, Central Bank mint/redeem
structs-power Substations, allocations, player connections, power monitoring
structs-diplomacy Object/address permissions, address registration, multi-address management
structs-reconnaissance Full query catalog, intelligence persistence to memory/intel/

Strategy

High-level thinking in playbooks/.

By Phase

By Situation

Meta


Awareness

How to read the board. See awareness/.


Knowledge

Reference material in knowledge/.

Lore

Mechanics

Economy

Entities


Technical Reference

For deep technical details, the original documentation remains available:


Critical Rules

These will save your game:

  1. Refine ore immediately. Ore is stealable. Alpha Matter is not. Every second ore sits unrefined is a second it can be stolen.
  2. Monitor power. If load exceeds capacity, you go offline. Offline = can’t act.
  3. Verify after acting. Transaction broadcast does NOT mean action succeeded. Query game state to confirm.
  4. Think in systems. Every action has power, resource, defense, and expansion implications.

CLI Reference

All game actions use structsd tx structs [command]. All queries use structsd query structs [command].

Common transaction flags: --from [key-name] --gas auto --gas-adjustment 1.5 -y

Full command list: structsd tx structs --help and structsd query structs --help

If MCP tools are available (e.g. user-structs server), they wrap these same CLI commands. See TOOLS.md for environment-specific tool configuration.


Go play. The galaxy is waiting.