Mekyra

PRODUCT

Your rules as a model
the engine can run.

Mekyra is a rules engineering platform organized around one thing: a formal model of your game’s rules. Importing, checking, testing and playing all read from that model or write to it. That’s what keeps the rulebook, the tests and the running game in agreement.

  • WorkingRuns in the private prototype
  • In developmentBeing built
  • PlannedNot started
01

AUTHOR

Get the rules into a form a machine can check.

You start from the rules as people wrote them. You end with a model where every mechanic uses the same small vocabulary.

  • Rules import

    Planned

    Rulebooks, card spreadsheets, FAQ and errata. Each formal rule links back to the text it came from, so the model and the rulebook can be compared line by line.

  • Claude-assisted modelling

    In development

    Claude proposes a structured version of each mechanic and lists ambiguous wording as questions. You approve or correct; nothing is guessed silently.

  • Game Rules DSL

    In development

    Triggers, conditions, targets, choices, costs, effects, durations, zones and control. If the DSL can’t express a rule, you find out while authoring, not mid-match.

  • Visual rules editor

    Planned

    Edit a rule as blocks (when, choose, where, do) without touching a text file.

02

VALIDATE

Find problems before anyone plays.

Most rules bugs are interactions nobody thought about. The model makes them something you can search for instead of wait for.

  • Engine test suite

    Working

    The engine is covered by automated tests today, including multi-step interactions between effects.

  • Static rule checks

    Planned

    Targets that can never exist, missing zones, ownership checked at the wrong time, conflicting timing.

  • AI QA

    Planned

    Claude reads the model and the rulebook side by side and points out mismatches, missing behavior and interactions worth testing.

  • Generated test scenarios

    Planned

    Given, when, expect. Scenarios produced from the rules and executed on the engine, so the same test always gives the same answer.

03

RUN

Play the actual game, not a mock-up.

The model runs on the same deterministic engine whether it’s a test, a playtest or, eventually, a shipped game.

  • Deterministic engine

    Working

    Decides legality, targets, damage and the next state. Same state and same action always give the same result.

  • Multiplayer sessions

    Working

    Persistent matches, reconnect and several player configurations, running today in the private prototype.

  • Browser playtest Studio

    Planned

    Launch any modelled game as a browser session and send playtesters a link.

  • Rules debugger

    Planned

    Ask why: why an action is illegal, which effect changed a stat, what is still waiting to resolve.

04

LEARN & SHIP

Change the rules with evidence.

Once rules are data, you can compare versions, run thousands of matches and reuse the logic elsewhere.

  • Simulation & balance

    Planned

    Automated players report dominant strategies, loops, unused cards and game length.

  • Versioning & collaboration

    Planned

    Diff two ruleset versions and see which tests each change affects.

  • SDK / API

    Long-term

    Use validated rules logic from your own client or game engine.

PLAYTEST AND DEBUG · PLANNED

When a playtester asks “why?”,
the answer is on screen.

The planned Studio puts a running match next to a rules inspector. Every number and every illegal action traces back to the rule responsible. Illustrative data.

Mekyra / Playtest StudioPlanned interface · illustrative data
MATCH STATETURN 04
Effect resolvedstate_041 → state_042
Rules inspector
Final ATK6
Base ATK
4
Ally aura
+1
Lane bonus
+2
Opponent’s curse
−1

Each modifier points to the rule that applied it.

Persistent matchesReconnectServer-side validationInspectable state
VERSIONING · PLANNEDv0.8 → v0.9

Fire spell: damage 4 → 3 · Scout: cost 2 → 3

Each change lists the tests it affects.

CONTACT

Working on a game
with a lot of rules?

Tell us what you’re building and where the rules get difficult.
Early conversations with designers decide what the general engine supports first.

Email Mekyra [email protected]Mekyra is in private development. Every email is read by the founder.