proud-hi

byOleksander

hi

Landing
Landing

Comments (0)

No comments yet. Be the first!

System Requirements

System Requirements Document for proud-hi

1. Introduction

proud-hi is a browser-based euphoria ragdoll simulator: a cool, playful game in which a glossy, blob-like ragdoll character flops, dangles, and tumbles through a physics sandbox for the player's amusement. The product intent is a quick, giddy dopamine hit — a toy you open, poke, throw, and reset, wrapped in a candy-coloured, sensual pop-minimalist shell.

The audience is playful, curious visitors who want an absurd, satisfying physics toy in the browser with no sign-up, no account, and no friction: land on the page, see the ragdoll, and drop in.

This document is the System Requirements Document for the product; it specifies the current features, the two accepted destinations (Landing and Simulator), the single accepted persona (Player), and the visual and interaction direction.

Success Criteria

  • A first-time visitor understands within the first screen that this is a ragdoll physics game and can enter the simulator with a single action.
  • The player can start a simulation, interact with the ragdoll (drag, throw, drop), toggle gravity, and reset the simulation, and each interaction produces an immediate, visible, physics-driven result.
  • The ragdoll's motion reads as continuous, unpredictable, and joyful, and the interface never obstructs the character's face or the readable text and controls.
  • The experience is fully usable at 375px, 768px, and 1280px viewports, and offers a usable static arrangement under prefers-reduced-motion.
Page 1 of 18

2. System Overview

proud-hi is delivered as a React frontend backed by a shared FastAPI backend process and a MariaDB database, orchestrated with docker-compose. The product itself is a client-side physics toy: the ragdoll simulation runs in the browser (real-time WebGL/R3F hero subject and physics-driven ragdoll), while the backend and database are provisioned infrastructure available to the application. No account, login, or persistent player profile is part of the accepted scope; both destinations are publicly reachable with no access requirement.

The single active human actor is the Player. The Player moves through two destinations:

  • Landing — the anonymous public entry surface: a full-bleed hero with the dangling ragdoll, the oversized "FLOOOOP" headline, and the "DROP IN" call to action that leads into the simulator.
  • Simulator — the playable ragdoll sandbox: a full-viewport canvas with a floating capsule toolbar (reset, throw, gravity toggle) and a slim top bar showing flop count and ragdoll name.

Removed from scope

  • None — no concepts were explicitly removed by the user.
Page 2 of 18

2a. Product Interpretation and Delivery Boundary

The user asked for "a cool game" and specifically "a europhia ragdoll simulator." That is the whole product: a physics ragdoll playground, not a platform. Delivery is first-party custom UI owned by the application, served in the browser. Both pages are public and require no identity, session, or account; there is no private durable player state that must be resumed, so no authentication or account management is introduced.

The backend and database are provisioned infrastructure that support the application; they do not create product requirements, domain entities, or access rules on their own. The ragdoll simulation, its physics, and its visual presentation are the current delivery. Anything beyond a playable ragdoll sandbox — accounts, leaderboards, social features, monetisation, level progression — is outside the accepted scope and is not part of this delivery.

2c. Page Content and Component Coverage

Page 3 of 18

Landing

  • Information / state: Public, anonymous entry. Presents the product as a cool euphoria ragdoll simulator. No loading of user data; the hero scene initialises the ragdoll visual.
  • Primary action: "DROP IN" pill button (bubblegum pink with lime hover state) navigates the Player into the Simulator.
  • Supporting actions: None required beyond entry; the hero is a single-subject composition.
  • Domain entities: Ragdoll character (visual subject only on this page).
  • Component responsibilities:
    • Full-bleed pastel-pink colour field (#FF4FA3 at 20% opacity over #FFF5F0), gradient-free.
    • Glossy 3D ragdoll (capsule limbs, joint spheres, dot eyes, curved mouth) dangling from the top edge by one arm, mid-flop, casting a soft shadow on the ground plane.
    • Oversized rounded headline "FLOOOOP" in Comfortaa, 88px desktop / 48px mobile, flush-left, with the ragdoll's soft shadow overlapping the type's lower third but never covering the character's face.
    • Lime pill "DROP IN" button with glossy inner highlight beneath the headline.
    • Curved blob-shaped section divider echoing the ragdoll's organic form.
  • States:
    • Loading: hero scene initialises; ragdoll appears as the WebGL subject becomes ready.
    • Empty: not applicable (no data collections).
    • Success: hero renders with ragdoll, headline, and CTA fully visible and readable at 375px, 768px, and 1280px.
Page 4 of 18
  • Error / recovery: if the 3D hero cannot initialise, the page still presents the headline and "DROP IN" control so the Player can enter the Simulator.
  • Reduced motion: ragdoll frozen in a static pose; decorative morphs disabled; all text and controls remain whole and readable.
Page 5 of 18

Simulator

  • Information / state: Public, anonymous playable sandbox. Displays the live ragdoll physics state, a flop count, and the ragdoll's name in a slim top bar.
  • Primary actions:
    • Interact with the ragdoll directly on the canvas (drag, throw, drop).
    • Reset the simulation (circular icon button in the floating toolbar).
    • Throw the ragdoll (circular icon button).
    • Toggle gravity (circular icon button).
  • Supporting actions: None beyond the three toolbar controls and direct canvas interaction.
  • Domain entities: Ragdoll (capsule limbs, joint spheres, expressive face), simulation state (gravity on/off, flop count, ragdoll name).
  • Component responsibilities:
    • Full-viewport canvas rendering the ragdoll and its physics.
    • Floating white capsule toolbar pinned bottom-centre with three circular icon buttons (reset, throw, gravity) that bounce on press.
    • Slim top bar showing flop count and ragdoll name.
    • Generous negative space around the ragdoll so its flailing reads clearly.
  • States:
    • Loading: canvas and physics world initialise; ragdoll spawns.
    • Empty: not applicable.
    • Success: ragdoll responds to drag/throw/drop, gravity toggle changes motion, reset restores the starting pose, flop count updates.
    • Error / recovery: if physics or canvas fails to initialise, the Player can use reset to reinitialise the simulation.
    • Reduced motion: ragdoll frozen to a static pose; decorative morphs disabled; toolbar and top bar remain fully readable and operable.
Page 6 of 18

3. Functional Requirements

FR-1 — Cool game experience (explicit) As a Player, I should experience proud-hi as a cool, fun game, so that opening it feels entertaining and playful.

  • Trigger: Player opens the product.
  • Observable result: the product presents itself as a game with a clear entry into play.
  • Access: public, no identity required.
  • Failure/recovery: not applicable at this level; entry remains available.
  • Continuation: Player proceeds to the Simulator.

FR-2 — Euphoria ragdoll simulator (explicit) As a Player, I should play a euphoria ragdoll simulator, so that I can enjoy physics-based ragdoll flops and tumbles.

  • Trigger: Player enters the Simulator.
  • Observable result: a ragdoll character is present in a physics sandbox and moves according to physics.
  • Access: public, no identity required.
  • Failure/recovery: if the simulation fails to initialise, the Player can reset it.
  • Continuation: Player continues interacting with the ragdoll.
Page 7 of 18

FR-3 — Enter the simulator from the landing page (required_inference) As a Player, I should see the ragdoll hero and a "DROP IN" control on the Landing page, so that I can enter the simulator with one action.

  • Trigger: Player activates "DROP IN".
  • Observable result: the Simulator opens with the ragdoll ready to play.
  • Access: anonymous.
  • Failure/recovery: if the hero 3D scene fails, the headline and "DROP IN" control remain available.
  • Continuation: Player begins interacting with the ragdoll.

FR-4 — Interact with the ragdoll (required_inference) As a Player, I should drag, throw, and drop the ragdoll, so that I can experiment with physics and see amusing outcomes.

  • Trigger: Player drags, throws, or drops the ragdoll on the canvas.
  • Observable result: the ragdoll responds with physics-driven motion; the flop count reflects activity.
  • Access: anonymous.
  • Failure/recovery: if motion stalls, the Player can reset the simulation.
  • Continuation: Player keeps experimenting.

FR-5 — Reset the simulation (required_inference) As a Player, I should reset the simulation with the reset control, so that I can restore the ragdoll to its starting state and start over.

  • Trigger: Player presses the reset circular icon button.
  • Observable result: the ragdoll returns to its starting pose/state; the simulation restarts.
  • Access: anonymous.
  • Failure/recovery: reset also serves as recovery from a failed or stuck simulation.
  • Continuation: Player resumes play.
Page 8 of 18

FR-6 — Throw the ragdoll (required_inference) As a Player, I should use the throw control, so that I can launch the ragdoll and watch it flop.

  • Trigger: Player presses the throw circular icon button.
  • Observable result: the ragdoll is launched with physics-driven motion.
  • Access: anonymous.
  • Failure/recovery: reset restores the simulation.
  • Continuation: Player continues experimenting.

FR-7 — Toggle gravity (required_inference) As a Player, I should toggle gravity, so that I can change how the ragdoll falls and floats.

  • Trigger: Player presses the gravity circular icon button.
  • Observable result: gravity state changes and the ragdoll's motion reflects the new state.
  • Access: anonymous.
  • Failure/recovery: toggling again restores the previous gravity state.
  • Continuation: Player continues experimenting.

FR-8 — Read flop count and ragdoll name (required_inference) As a Player, I should see the flop count and the ragdoll's name in the top bar, so that I have a light sense of progress and character identity.

  • Trigger: Player plays in the Simulator.
  • Observable result: the top bar displays the flop count and ragdoll name, remaining readable at all viewports.
  • Access: anonymous.
  • Failure/recovery: not applicable.
  • Continuation: Player continues playing.

4. User Personas

Page 9 of 18

Player

  • Product context: A playful, curious visitor who wants a quick dopamine hit from absurd ragdoll flops. They arrive with no account and no setup, expecting an immediate toy.
  • Primary goal: Launch the simulator and experiment with ragdoll physics to see amusing, satisfying outcomes.
  • Distinct accepted responsibilities:
    • Entering the simulator from the Landing page via "DROP IN".
    • Interacting with the ragdoll by dragging, throwing, and dropping it.
    • Using the reset, throw, and gravity controls in the floating toolbar.
    • Observing the flop count and ragdoll name in the top bar.
  • Relevant inputs or decisions: When to drop in, how to fling the ragdoll, whether to toggle gravity, and when to reset.
  • Interactions with other accepted participants: None — the Player is the sole active human actor; the ragdoll is a simulated subject, not a persona.
  • Observable success: A playful sandbox session that feels satisfying and entertaining, with the ragdoll responding immediately and joyfully to every interaction.

5. Core User Flows

Page 10 of 18

Flow A — Enter the simulator (Player)

  1. Player opens the Landing page (anonymous, no account).
  2. Player sees the full-bleed pastel-pink hero with the glossy ragdoll dangling mid-flop, the oversized "FLOOOOP" headline, and the lime "DROP IN" pill button.
  3. Player activates "DROP IN".
  4. The Simulator opens with the ragdoll spawned in the physics sandbox and the top bar showing flop count and ragdoll name.
  5. Failure/recovery: if the hero 3D scene fails to initialise, the headline and "DROP IN" control remain available and the Player can still enter.
  6. Continuation: Player proceeds to interact with the ragdoll (Flow B).

Flow B — Play with the ragdoll (Player)

  1. Player is in the Simulator with the ragdoll visible on the full-viewport canvas.
  2. Player drags the ragdoll, throws it, or drops it.
  3. The ragdoll responds with physics-driven motion; the flop count reflects activity.
  4. Player optionally presses the throw control to launch the ragdoll.
  5. Player optionally presses the gravity toggle to change how the ragdoll falls or floats.
  6. Failure/recovery: if the simulation stalls or fails, the Player presses reset to restore the starting state.
  7. Continuation: Player keeps experimenting, resetting, and toggling gravity as desired.
Page 11 of 18

Flow C — Reset the simulation (Player)

  1. Player is in the Simulator.
  2. Player presses the reset circular icon button in the floating capsule toolbar.
  3. The ragdoll returns to its starting pose/state and the simulation restarts.
  4. Continuation: Player resumes play from a clean state.
Page 12 of 18

6. Visuals Colors and Theme

Muse: Karim Rashid — sensual pop minimalism for a euphoric ragdoll playground. Giddy, glossy, slightly unhinged; pure fun with a candy shell.

Headline: "FLOOOOP" — oversized, rounded, flush-left.

Colour tokens (light mode):

RoleHex
Background#FFF5F0
Surface#FFFFFF
Text#1A1A1A
Primary (brand/CTA)#FF4FA3
Accent (highlights, hover, joint markers)#B8FF3C
Muted (secondary copy)#7A6F78

No blue anywhere; the indigo/blue-on-white SaaS template is forbidden.

Typography:

  • Headings: Comfortaa, medium weight (500–600), generous letter-spacing on display sizes, lowercase-friendly with occasional all-caps micro-labels.
  • Body: Quicksand.
  • Scale: 1.333 modular — 88 / 64 / 48 / 32 / 24 / 18 / 16, with mobile clamp (48px min for display, 88px max on desktop).
Page 13 of 18

Shape language: Organic blobs, capsules, and soft-cornered rectangles with 24–40px radii. Section boundaries curve like melted candy. Buttons are pill-shaped with a glossy inner highlight. Ragdoll limbs are rounded capsules with visible joint spheres. No sharp corners except thin 1px rules for data readouts.

Layout: Asymmetric, playful grid. Hero is a full-bleed 3D ragdoll scene with floating glassy UI labels. Landing stacks a giant curved headline over a colour-blocked playground teaser. Simulator is a full-viewport canvas with a floating capsule toolbar pinned bottom-centre and a slim top bar. Generous negative space around the ragdoll.

Imagery: Glossy 3D blobs and a capsule-shaped ragdoll with a simple expressive face (two dot eyes, curved mouth). Soft studio lighting with pink and lime rim lights. No photography, no clip art. Backgrounds are flat colour fields with subtle radial glow behind the ragdoll.

Accessibility of text and controls: Headlines, wordmarks, labels, numbers, cards' text and controls stay entirely inside the viewport and their container at 375px, 768px, and 1280px, wrapping or scaling (e.g. font-size: clamp(...)) to fit; no other element covers them. Imagery and decoration may bleed, overlap, or crop as the direction asks, but never cover readable text or controls.

Page 14 of 18

7. Signature Design Concept

The public entry is a single-subject hero: a full-bleed pastel-pink colour field (#FF4FA3 at 20% opacity over #FFF5F0, gradient-free) fills the viewport. A glossy 3D ragdoll — capsule limbs, joint spheres, dot eyes, curved mouth — dangles from the top edge by one arm, mid-flop, casting a soft shadow on the ground plane. The oversized rounded headline "FLOOOOP" in Comfortaa 88px (48px mobile) sits flush-left, overlapping the ragdoll's shadow but never covering the character's face. Beneath it, a lime pill "DROP IN" button with a glossy inner highlight invites entry. No centred stack, no subtext paragraph — just the ragdoll, the word, and the button. A curved blob-shaped divider morphs between pages, echoing the ragdoll's organic form.

Page 15 of 18

8. Interaction Model & Motion Direction

Interaction Model: Animated Motion Tempo: expressive Hero Dimensionality: webgl

Landing Hero Motion Brief

  • Focal subject: the glossy 3D ragdoll dangling from the top edge by one arm, mid-flop, with a soft shadow on the ground plane.
  • Input → transformation → outcome thesis: the ragdoll hangs and sways under its own physics; on hover the "DROP IN" pill squishes and bounces back with a soft overshoot; activating it transitions into the Simulator with a liquid morph and a curved blob-shaped divider.
  • Motion vocabulary: liquid morphs on section transitions, springy scale-ins for cards and buttons, squish-and-bounce hover states with soft overshoot, and the ragdoll's own continuous, unpredictable, joyful physics as the primary motion.
  • Composed first frame: pastel-pink field, ragdoll dangling flush against the top edge, "FLOOOOP" flush-left overlapping the shadow's lower third, lime "DROP IN" pill beneath.
  • Reduced-motion state: ragdoll frozen in a static pose, decorative morphs disabled, all text and controls whole and readable.

Landing Hero 3D Scene Brief — DIRECTION-DERIVED

A single crafted real-time WebGL/R3F object: the glossy capsule-limbed ragdoll with joint spheres and a simple expressive face, lit by soft studio lighting with pink and lime rim lights, dangling from the top edge by one arm and swaying under physics. The scene shows the product's defining state — a ragdoll mid-flop — as the sole hero subject.

Page 16 of 18

9. Non-Functional Requirements

  • NFR-1 — Responsive readability (explicit, from creative direction): all readable text and controls remain whole and inside the viewport and their container at 375px, 768px, and 1280px; no element covers them.
  • NFR-2 — Reduced motion (explicit): under prefers-reduced-motion, the ragdoll freezes to a static pose, decorative morphs are disabled, and a usable static arrangement is provided.
  • NFR-3 — Palette discipline (explicit): no blue anywhere; the indigo/blue-on-white SaaS template is forbidden.
  • NFR-4 — Performance (required_inference): the ragdoll physics and WebGL hero must run smoothly in the browser to deliver continuous, joyful motion.
  • NFR-5 — No account friction (explicit): both destinations are publicly reachable with no access requirement.

10. Tech Stack

  • Frontend: React application UI, with WebGL/R3F for the real-time 3D ragdoll hero and physics-driven ragdoll simulation.
  • Backend: shared FastAPI process for application APIs and domain modules.
  • Database: MariaDB for application-owned persistent data.
  • Orchestration: docker-compose with the backend, database, and frontend services.
Page 17 of 18

11. Assumptions and Constraints

  • A-1: The ragdoll simulation runs client-side in the browser; the backend and database are provisioned infrastructure and do not by themselves create domain entities or authentication.
  • A-2: No account, login, or persistent player profile is part of the accepted scope; both pages are public.
  • A-3: The Player is the sole active human persona; the ragdoll is a simulated subject, not a persona.
  • A-4: The creative direction is authoritative for visuals, motion, and layout; the palette, fonts, and shape language are fixed as specified.
  • A-5: The product is a single-player toy; no social, leaderboard, or monetisation features are in scope.

12. Glossary

  • Ragdoll: the glossy, capsule-limbed, blob-like character with joint spheres and an expressive face that the Player flops, throws, and drops.
  • Flop count: the numeric readout in the Simulator top bar reflecting ragdoll activity.
  • DROP IN: the lime pill call-to-action on the Landing page that enters the Simulator.
  • FLOOOOP: the oversized rounded headline on the Landing page.
  • Euphoria ragdoll simulator: the product category — a joyful, physics-based ragdoll sandbox.
  • Reduced motion: the prefers-reduced-motion mode that freezes the ragdoll and disables decorative morphs.
Page 18 of 18
Live
Landing design preview
Landing: View ragdoll hero
Landing: Activate DROP IN
Simulator: Watch ragdoll spawn
Simulator: Read flop count and name
Simulator: 1. Drag ragdoll
Simulator: 2. Drop ragdoll
Simulator: 3. Press throw control
Simulator: 4. Toggle gravity
Simulator: 5. Press reset control
Simulator: 6. Resume play from clean state
Live
Landing design preview
Landing: View ragdoll hero
Landing: Activate DROP IN
Simulator: Watch ragdoll spawn
Simulator: Read flop count and name
Simulator: 1. Drag ragdoll
Simulator: 2. Drop ragdoll
Simulator: 3. Press throw control
Simulator: 4. Toggle gravity
Simulator: 5. Press reset control
Simulator: 6. Resume play from clean state