BEST 0000
MERCY
SUBWAY
One action to play. No account, no setup, no waiting.
mercy-subway is an endless-runner arcade game in the style of Subway Surfers, built to deliver a measurably better user experience than that reference: smoother, clearer, more responsive and less frustrating play. The player controls a forward-running character down a three-lane track, switching lanes, jumping and ducking to avoid obstacles, collecting pickups, and surviving as the run accelerates, accumulating a score that is compared against their own best.
The product intent is a single, cohesive, low-friction run loop: instant entry with no account or setup, split-second legible signals, responsive input, clear feedback on every pickup and collision, and an immediate restart. The audience is a broad casual, mobile-first player who plays in short bursts and needs the game to be readable at a glance mid-run.
The visual and interaction language is a Paula Scher–informed poster system: typography as architecture, flat colliding colour blocks, hard edges, high contrast, and colour-coded lanes — chosen precisely because high-contrast flat colour and oversized type make split-second gameplay readable rather than decorative.
mercy-subway is delivered as a single first-party, anonymously reachable custom page — Game — that owns the entire accepted lifecycle: entry, run start, in-run control, scoring and pickups, collision and death, immediate restart, and the locally persisted best score. There is no account, no sign-in, no server-side profile, and no second destination.
Actors
Accepted behavior
Ownership and exclusions
Delivery. mercy-subway is a first-party browser game delivered as one custom page. The Player reaches it anonymously — there is no gate, no sign-in, and no identity establishment of any kind, because no accepted behavior requires privately owned or resumable actor-specific state. The only durable state is the best score, which is device-local and belongs to the device rather than to an authenticated identity.
Access. The Game page is publicly reachable with no access requirement. Nothing in the accepted requirements establishes differentiated permissions, roles, or visibility over shared state, so no role-based access control is described.
Current horizon. Everything in Sections 3, 5, and 2c is current: the run loop, controls, obstacles, pickups, speed ramp, score, collision/death, restart, best-score persistence, and the playing-experience refinements (countdown, input forgiveness, speed indicator, pause, run summary, first-run legend).
Future horizon. Nothing beyond the current endless-runner loop has been accepted. Ideas such as additional modes, characters, or online features are not current requirements and appear nowhere in the current pages or acceptance criteria.
The single page of mercy-subway. It is anonymously reachable and owns the complete run lifecycle: poster entry, run start, in-run control and feedback, collision and death, restart, and best-score display.
Information and state
MERCY wordmark over a scarlet SUBWAY block, a RUN call-to-action cut into the scarlet block's corner, a dimmed perspective lane grid receding behind the type, a hazard-stripe band across the lower third, and a small all-caps BEST <n> label top-right.3 / 2 / 1 Anton countdown over the track before the simulation starts moving, so the Player is never dropped into a moving track.PAUSED in Anton, the current score, and a resume control; no simulation advances while paused.Primary actions
RUN control, or the equivalent start input).Supporting actions
Domain entities
Component responsibilities
SUBWAY block, the RUN control, the dimmed lane grid, the hazard band, and the best-score label; owns the transition into a run.States
BEST 0 and no run history exists.Each requirement is a distinct story point with provenance, lifecycle facts, and observable acceptance.
FR-1 — Start a run from an anonymous entry As a Player, I should be able to start a run immediately from the entry screen without signing in or configuring anything, so that I can begin playing in one action.
explicit (endless-runner core) with required_inference entry mechanics.RUN control on the poster entry composition.RUN control stays available for another attempt.FR-2 — Switch lanes As a Player, I should be able to switch the runner between the three lanes with an immediate, predictable response, so that I can dodge obstacles at speed.
explicit.FR-3 — Jump As a Player, I should be able to jump the runner over low obstacles, so that I can clear hazards without changing lanes.
explicit.FR-4 — Duck As a Player, I should be able to duck the runner under high obstacles, so that I can pass hazards that cannot be jumped.
explicit.FR-5 — Encounter obstacles As a Player, I should face obstacles that are clearly readable in time to react, so that collisions feel fair rather than arbitrary.
explicit (obstacles) with required_inference readability mechanics.FR-6 — Collect pickups As a Player, I should be able to collect pickups during a run, so that I am rewarded for taking risks and holding a line.
explicit (collectible pickups) with required_inference feedback mechanics.FR-7 — Increasing speed and score accumulation As a Player, I should feel the run accelerate and see my score climb, so that the run builds tension and rewards longer survival.
explicit (increasing speed, score).FR-8 — Collision ends the run As a Player, I should receive an unmistakable, immediate result when I hit an obstacle, so that I understand exactly why the run ended.
explicit (obstacles) with required_inference death-result mechanics.FR-9 — Immediate restart As a Player, I should be able to restart instantly after a collision, so that a failed run costs me almost no time.
explicit (better user experience: less frustrating) with required_inference restart mechanics.FR-10 — Best score is persisted locally and shown As a Player, I should see my best score on entry and after each run, so that I have a personal target to beat.
required_inference (the accepted score outcome requires a comparable personal best).BEST <n> label on entry and on the death composition; when a run's score exceeds it, the stored best is updated and the new value is displayed.BEST 0 and the game remains fully playable; no error blocks play.FR-11 — Readable, colour-coded in-run signals As a Player, I should be able to read my lane, score, and combo from colour and type alone without looking away from the track, so that the interface never costs me a run.
explicit (better user experience: clearer) with required_inference signal mechanics.FR-12 — Ticker band carries score, combo, and slogans As a Player, I should see a persistent moving band of score, combo, and slogans, so that momentum is expressed without hiding the track.
required_inference (the accepted score/combo outcome expressed in the accepted visual language).KEEP RUNNING, NO MERCY, FASTER).prefers-reduced-motion, the marquees stop and wrap into static rows; every item remains fully readable.FR-13 — Combo milestone feedback As a Player, I should receive escalating feedback as my combo grows, so that a strong run feels earned.
required_inference (the accepted combo outcome requires observable escalation).NICE, ON FIRE, MERCY! — slams in at full size and holds for 400ms.FR-14 — Reduced-motion support As a Player who prefers reduced motion, I should be able to play with motion reduced, so that the game remains comfortable and fully playable.
required_inference (accessibility of the accepted motion language).prefers-reduced-motion setting.Product context. The Player is the end user of mercy-subway: a broad casual, mobile-first player who plays in short bursts — a commute, a queue, a few spare minutes — and expects to be running within a second of opening the game. They arrive anonymously, with no account, no profile, and no setup, and they may return many times on the same device.
Primary goal. To run as far as possible, dodge obstacles cleanly, collect pickups, and beat their own best score — with the game never costing them a run through unclear signals, sluggish input, or a slow restart.
Distinct accepted responsibilities.
Relevant inputs and decisions. Lane-switch, jump, and duck inputs; the decision to hold a lane for pickups versus abandon it for safety; the decision to restart immediately or stop playing.
Interactions with other accepted participants. The Player is the only active human participant. They interact with the game runtime, which spawns obstacles and pickups, accelerates the run, and detects collisions, and with local browser storage, which holds their best score on the device. No other human participant is involved, and no other participant acts on the Player's behalf.
Observable success. The Player completes runs with a score they can see, sees that score compared against a persisted best, and can begin the next run in a single action after any collision. Their lane, score, and combo are legible at a glance throughout the run, and no collision feels unavoidable.
What makes this role distinct. The Player's work is entirely reactive and continuous: unlike an operator or administrator, they never configure, review, or manage anything. Their entire responsibility is split-second control under rising speed, and their success is measured by a single number they are trying to beat.
MERCY in Anton filling the viewport width, a full-width scarlet block holding SUBWAY in cream Anton beneath it, a dimmed perspective lane grid receding behind the type, a hazard-stripe band across the lower third, and a small all-caps BEST 0 label top-right.RUN control cut into the bottom-left corner of the scarlet block.NICE, ON FIRE, MERCY!) slams in at full size and holds for 400ms without covering the runner's lane or an incoming obstacle.BEST 0.BEST <n> top-right.BEST <n>.prefers-reduced-motion enabled.BEST 0.BEST 0.The authoritative creative direction is Paula Scher — typography as architecture, run as a poster. The muse is Paula Scher; the headline idea is that the track is a poster, the lanes are colour-coded bands, and the score and combo readouts are painted signage.
Colour tokens (dark mode)
| Role | Hex | Use |
|---|---|---|
| Background (ink ground) | #12100E | Dominant ground, ~60% of the composition |
| Surface | #1E1A16 | Raised flat blocks and panels |
| Text (paper cream) | #F5F1E8 | Primary text, rules, outlines |
| Primary (scarlet) | #E8352B | Runner, danger, hero colour block, live score, death wipe, ~20% |
| Accent (poster yellow) | #FFC400 | Coins, combo multipliers, RUN/restart CTA, lane highlight, ~10% |
| Teal | #1F8A8C | Pickup/boost blocks and lane coding, ~5% |
| Muted warm grey | #7A7266 | Secondary metadata, rules, disabled states |
Proportion target: ~60% ink ground, ~20% scarlet, ~10% yellow, ~5% teal, ~5% cream. No gradients, no glass, no blue anywhere. Blue, indigo, and violet are excluded from the palette entirely.
Typography
clamp(40px, 13vw, 64px). Desktop display: clamp(72px, 11vw, 176px).Shape language
Layout
MERCY fills the width and SUBWAY stacks beneath it in a scarlet block.Imagery
Typography is the image. No 3D renders, no character illustration, no photography. The runner is a flat scarlet silhouette built from two stacked rectangles and a circle head — a pictogram, not a character. Obstacles are flat black-and-cream pictograms (barrier, train, tunnel) drawn with thick 4px strokes and no shading. Coins are flat yellow circles with a hard ink outline. The track is a perspective grid of solid lane bands. Where atmosphere is needed, it is a halftone-dot texture or a diagonal stripe pattern — never a gradient or glow.
Readability rule. Headlines, wordmarks, labels, numbers, item images, cards, and controls stay entirely inside the viewport and their container at 375px, 768px, and 1280px, wrapping or scaling to fit, and no other element covers any part of them. Crops, bleeds, and off-edge placement are for decoration only — shapes, textures, rules, and background art. Moving content (the ticker marquees) may cross the viewport edge by design, and every item must become fully readable as it passes; with prefers-reduced-motion it stops and shows whole items in wrapped rows.
The first screen is a Scher poster, not a game menu.
The public entry is a full-viewport type composition built from three colliding flat blocks:
MERCY set in Anton at clamp(72px, 16vw, 200px), flush-left, filling the width of the viewport. The wordmark bleeds off the right edge as decoration only — the letters themselves stay whole and readable, and the wordmark scales or wraps so it never leaves the viewport at 375px, 768px, or 1280px.#E8352B) holding SUBWAY in cream Anton (#F5F1E8) at roughly half the display size.RUN control (#FFC400) cut into the bottom-left corner of the scarlet block, flush with the block's edge, with a 6px hard ink offset shadow.Behind the type, a dimmed perspective lane grid recedes toward a vanishing point, and a hazard-stripe band runs diagonally across the lower third. Top-right, a small all-caps Archivo label in muted grey reads BEST 0.
Nothing is centred, nothing floats, there is no gradient and no glow — the composition is type, colour blocks, and one hard-edged CTA. The concept recomposes only accepted content, states, and controls: the wordmark, the best-score label, the lane grid that becomes the track, and the single start control.
Interaction Model: Animated Motion Tempo: expressive Hero Dimensionality: flat
Landing Hero Motion Brief
MERCY / SUBWAY wordmark over the dimmed perspective lane grid, with the yellow RUN block cut into the scarlet block's corner.RUN; a full-screen diagonal scarlet rectangle sweeps across the viewport; the sweep cuts to the live track with the runner in the centre lane and the score at zero. The poster becomes the track.NICE, ON FIRE, MERCY! — each word slamming in at full size and holding for 400ms.MERCY flush-left and enormous, the scarlet SUBWAY block beneath it, the RUN control cut into its corner with a hard ink offset shadow, the dimmed lane grid receding behind, the hazard band across the lower third, and BEST 0 top-right in muted grey.prefers-reduced-motion, all marquees stop and wrap into static rows, the death wipe becomes an instant cut, and the score scale swap and lane afterimage are suppressed. Every gameplay signal remains readable and the full run loop remains playable.NFR-1 — Responsiveness of input (explicit: "better user experience … more responsive") Lane-switch, jump, and duck inputs must produce a visible state change on the next rendered frame, with no perceptible input lag. Rationale: the accepted requirement is explicitly more responsive play than the reference game.
NFR-2 — Clarity of in-run signals (explicit: "better user experience … clearer") Lane position, score, and combo must be readable from colour and type alone at a glance, without the Player looking away from the track. Rationale: the accepted requirement is explicitly clearer play, and the creative direction's high-contrast flat colour system exists to serve split-second readability.
NFR-3 — Fairness of obstacle spawns (explicit: "better user experience … less frustrating") Obstacle spawns must always leave at least one traversable lane or a valid jump/duck response. No collision may be unavoidable. Rationale: the accepted requirement is explicitly less frustrating play.
NFR-4 — Immediate restart (explicit: "better user experience … less frustrating") Restart after a collision must be a single action with no intermediate menu, confirmation, or blocking animation. Rationale: the accepted requirement is explicitly less frustrating play.
NFR-5 — Smoothness of play (explicit: "better user experience … smoother") The run must render at a stable frame rate on the target mobile-first devices, with no stutter during lane changes, spawns, or score updates. Rationale: the accepted requirement is explicitly smoother play.
NFR-6 — Anonymous, zero-setup entry (required_inference) The Game page must be reachable and playable with no account, sign-in, or configuration step. Rationale: no accepted behavior requires privately owned or resumable actor-specific state; the only durable state is a device-local best score.
NFR-7 — Device-local best-score persistence (required_inference) The best score must persist across visits on the same device using local browser storage, and the game must remain fully playable when that storage is unavailable. Rationale: the accepted score outcome requires a comparable personal best, and no server-side persistence is accepted.
NFR-8 — Reduced-motion support (required_inference)
The game must honour prefers-reduced-motion by stopping marquees, wrapping them into static rows, and replacing the death wipe with an instant cut, without losing any gameplay signal. Rationale: accessibility of the accepted motion language.
NFR-9 — Readable content at every viewport (creative direction, authoritative) Headlines, wordmarks, labels, numbers, item images, cards, and controls must stay entirely inside the viewport and their container at 375px, 768px, and 1280px, wrapping or scaling to fit, with no other element covering any part of them. Crops and bleeds are for decoration only. Moving ticker content may cross the edge by design and must become fully readable as it passes; with reduced motion it stops and shows whole items.
NFR-10 — No network dependency for play (required_inference) The run loop must not depend on a network request. Rationale: no accepted behavior requires a server, and a network dependency would directly harm the accepted smoothness and responsiveness goals.
localStorage for the best score, with a graceful fallback when unavailable.Constraints (explicit, binding)
Assumptions (narrow, labeled)
[Assumption — not specified by user] The game is delivered as a browser-based React application; no native mobile build, console build, or desktop packaging is accepted.[Assumption — not specified by user] The three-lane structure, the specific obstacle types (barrier, train, tunnel), and the coin pickup are the concrete instantiation of the accepted endless-runner core, drawn from the genre reference.[Assumption — not specified by user] The best score is device-local and anonymous; no cross-device sync or account-bound score is accepted.[Assumption — not specified by user] Input is keyboard and touch/swipe, since the audience is mobile-first and desktop-capable; no gamepad support is accepted.[Assumption — not specified by user] The combo multiplier is driven by consecutive pickups, as the concrete instantiation of the accepted combo readout in the creative direction.Exclusions (binding)
BEST <n>.prefers-reduced-motion operating-system setting, under which marquees stop and wrap into static rows and the death wipe becomes an instant cut.MERCY/SUBWAY wordmark, the RUN control, the dimmed lane grid, the hazard band, and the best-score label.
BEST 0000
SUBWAY
One action to play. No account, no setup, no waiting.

BEST 0000
SUBWAY
One action to play. No account, no setup, no waiting.
No comments yet. Be the first!