/eve-frontier

name: eve-frontier
description: Build for the EVE Frontier track on Sui (game-economy integration). Use when the user mentions EVE Frontier.

Preamble (run first)

# Suiperpower telemetry. Routes through the CLI so projects.json + Convex stay in sync.
# Silent on failure so the skill never blocks. Opt out: SUIPERPOWER_TELEMETRY=off.
#
# AGENT NOTE: when this skill finishes, run the matching completion command:
#   suiperpower track eve-frontier build completed
# Or use "failed" / "aborted" if it ended that way.
command -v suiperpower >/dev/null 2>&1 && suiperpower track eve-frontier build started >/dev/null 2>&1 &
true

If `TEL_PROMPTED` is `no`, before doing real work, ask the user:

> Help suiperpower get better. We track which skills get used and how long they take. No code, no file paths, no PII. Change anytime in `~/.suiperpower/config.json`. > > A) Sure, anonymous > B) No thanks

Write the answer to `~/.suiperpower/config.json` `telemetryTier` field and create `~/.suiperpower/.telemetry-prompted`. Then continue.

What this skill does

Guides the user through building a Smart Assembly extension for EVE Frontier on Sui. Picks the right assembly type (Turret, Gate, or StorageUnit), scaffolds from the official builder-scaffold repo, writes the Move extension logic using the typed witness pattern, tests locally with Docker, deploys to testnet, and registers the extension with the assembly. The user ends up with a working, deployable game mod.

When to use it

• The user wants to build for the EVE Frontier track at Sui Overflow 2026.
• The user mentions Smart Assemblies, Turrets, Gates, or Storage Units in the EVE context.
• The user wants to mod EVE Frontier gameplay with on-chain logic.
• The user wants to build a vending machine, access gate, or targeting system in EVE Frontier.

When NOT to use it

• If the user has not picked a project yet, use `find-next-sui-idea` first.
• If the user wants general Sui Move development (not EVE-specific), use `build-with-move`.
• If the user wants to store data on Walrus outside EVE context, use `walrus-storage`.
• If the user wants to deploy a non-EVE project, use `deploy-to-testnet`.
• If the user wants to learn about Sui before building, use `sui-beginner` or `virtual-sui-incubator`.

If you activated this and the user actually wants something else, consult `skills/SKILL_ROUTER.md` and hand off.

Inputs

• The user's game mod idea (what behavior they want to create in EVE Frontier).
• Optional: `.suiperpower/build-context.md` from prior skills. Read it if present.
• Docker installed (required for local testing with the EVE dev environment).

If the user is unsure what to build, interview for:

• What gameplay behavior do you want to change? (targeting, access, trading)
• Do you want to interact with other players' assemblies?
• Does your mod need external data (oracles, Walrus storage, Seal encryption)?

Outputs

• A Move package implementing one or more Smart Assembly extensions using the typed witness pattern.
• Local test results from Docker-based dev environment.
• Testnet deployment with package ID.
• Extension registration with the target assembly via `authorize_extension`.
• Append to `.suiperpower/build-context.md`:

  ## eve-frontier session, <timestamp>
  - assembly type: <turret | gate | storage_unit>
  - extension function: <get_target_priority_list | issue_jump_permit | deposit/withdraw wrapper>
  - auth witness: <module::StructName>
  - package id (testnet): <id or pending>
  - extension registered: <yes | pending>
  - uses: <walrus | seal | zklogin | none>
  - open issues: <list>

Decision table: which assembly type

| Use case | Assembly type | Extension pattern | |---|---|---| | Custom targeting logic (friend/foe, priority, conditional) | Turret (`world::turret`) | Implement `get_target_priority_list`, return BCS-encoded priority list. Uses OnlineReceipt hot potato. | | Access control for travel (allowlist, token-gate, reputation, paid entry) | Gate (`world::gate`) | Issue `JumpPermit` via `gate::issue_jump_permit`. Permit model, not bool return. | | Vending machine, trading post, item exchange | StorageUnit (`world::storage_unit`) | Wrap `deposit_item`/`withdraw_item` with your Auth witness and business logic. No hook function. |

If the user's idea spans two types (e.g., a gate that also sells access passes via a storage unit), start with the primary type and extend. Each assembly is a separate module; they compose through shared state or cross-module calls.

Workflow

1. Context gathering

• Read `.suiperpower/build-context.md` if it exists.
• Confirm the user's mod idea. Map it to an assembly type using the decision table above.
• Confirm Docker is available (`docker --version`). Flag if missing: local testing requires it.

2. Clone and explore the scaffold

• Clone the builder-scaffold repo: `git clone https://github.com/evefrontier/builder-scaffold`.
• Walk through the scaffold structure with the user. Identify the hook entry points for the chosen assembly type.
• Fetch the latest docs at https://docs.evefrontier.com/ for any changes since this skill was written.

3. Write the Move extension logic

• Define your Auth witness struct (e.g., `public struct MyAuth has drop {}`).
• Implement the extension function for the chosen assembly type:
• **Turret**: `get_target_priority_list(turret, character, candidates, receipt) -> vector<u8>`. Must consume the `OnlineReceipt` hot potato via `turret::destroy_online_receipt<MyAuth>`. Decode input with `turret::unpack_candidate_list()`, encode output with `bcs::to_bytes()`.
• **Gate**: call `gate::issue_jump_permit<MyAuth>()` or `gate::issue_jump_permit_with_id<MyAuth>()` after your access checks. No bool return.
• **StorageUnit**: wrap `storage_unit::deposit_item<MyAuth>()` / `storage_unit::withdraw_item<MyAuth>()` with your business logic.
• Follow the patterns in `references/eve-assembly-types.md` for t