Steal a Egg is a script for the game Steal a Egg that steals eggs automatically. Its defining rule is selective: it steals eggs from areas that are not egg areas, and it never steals eggs that have been placed on the ground. The product pairs that automation with a smart, attractive interface so the user can understand what the script does, start it, stop it, and see its current status at a glance.
The audience is the script user — a player of Steal a Egg who wants automatic egg stealing without manually picking up eggs, and who wants a calm, readable, good-looking control surface rather than a raw console or a cluttered overlay. The interface is presented in a warm editorial style (cream ground, serif voice, rust action colour, teal running state) that keeps the tool playful and legible.
The product is delivered as a first-party web application: a public Landing page that explains the script, and a Control Panel where the user starts and stops automatic egg stealing and reads the current status. No account is required to use either page.
Steal a Egg is a small, focused tool with two current surfaces and one background automation responsibility.
The application is provisioned as three services: a shared FastAPI backend that hosts the application APIs and the egg-stealing domain module, a MariaDB database for application-owned persistent data, and a React frontend that renders the Landing and Control Panel. The backend is reused for all feature APIs rather than split into additional services.
Actors: the Script user is the only active human persona. The egg-stealing automation is a system process owned by the backend; it is not a persona and has no independent goals.
Removed from scope
The accepted product is a script plus a smart, attractive UI. The script's job is automatic egg stealing under two hard rules: eggs are taken only from areas that are not egg areas, and eggs placed on the ground are never taken. The UI's job is to make that automation understandable and controllable — a public explanation on the Landing page and a clear Start/Stop control with a live status view on the Control Panel.
Both current pages are first-party and anonymously reachable; the source establishes no account, login, or identity requirement, and none is indispensable, because the automation's state is a single running/stopped condition that the user controls directly rather than durable private state that must be resumed across sessions or bound to a specific participant. The Control Panel is therefore reachable directly from the Landing call to action without an identity step.
The background automation is a system process, but every human-facing part of it — starting, stopping, and reading status — is owned by the Control Panel. Nothing in the current scope is delegated to a provider surface or an external destination.
Future ideas are not part of the current delivery and are listed separately in Section 11.
Not applicable. No reference directive in this request declares content_source; the product facts come from the authoritative user requirement thread and Planning Scope only.
FR-1 — Automatic egg stealing As a Script user, I should have the script steal eggs automatically, so that I do not have to pick up eggs by hand.
FR-2 — Steal only from areas that are not egg areas As a Script user, I should have the script steal eggs only from areas that are not egg areas, so that the automation follows the game's area rule.
FR-3 — Never steal eggs placed on the ground As a Script user, I should have the script skip eggs placed on the ground, so that ground eggs are never taken.
FR-4 — Understand the script from the Landing page As a Script user, I should read on the Landing page what the script does, so that I understand the automation and its rules before using it.
FR-5 — Start automatic egg stealing As a Script user, I should start automatic egg stealing from the Control Panel, so that the script begins working.
FR-6 — Stop automatic egg stealing As a Script user, I should stop automatic egg stealing from the Control Panel, so that the script stops working when I want it to.
FR-7 — See the current status As a Script user, I should see the current status of the automation on the Control Panel, so that I know whether the script is working.
FR-8 — Smart, attractive UI As a Script user, I should use a smart and attractive interface, so that controlling the script feels clear and pleasant.
The creative direction is authoritative for this section: Warm editorial craft for an egg-stealing script, after the muse Frank Chimero. Headline idea: a calm cream page with a readable serif voice and a rust egg basket — playful, not corporate.
Colour tokens (light mode)
| Role | Hex | Use |
|---|---|---|
| Background | #F5EEDF | Cream page ground, covers most of the page |
| Surface | #FFFBF2 | Panels and the wide control card |
| Text | #221E1A | Ink text and rules, held for contrast |
| Primary | #B5502F | Rust action colour: CTA, Start/Stop switch, hairline rules, egg-basket illustration |
| Accent | #2E6E63 | Teal running state: status dot, allowed-area column, small hero rule |
| Muted | #8A7F6E | Secondary labels and supporting text |
Typography
clamp(...) with its mobile size.Shape language. Soft 12 px radii on panels; thin 1 px ink rules; small hand-drawn egg marks as icons.
Layout. One column with a 640 px reading measure. A wide two-panel control block sits under the text on the Control Panel. Generous margins at 1280 px; full width with 20 px gutters at 375 px.
Imagery. Flat warm illustration of an egg basket and a hand; a hand-drawn diagram of the egg areas. No photography.
Avoid. No blue or indigo accents; no gradient blobs or glass panels; no grid of identical hover-lift cards; no stock photography; no Inter or Roboto fonts. The generic indigo/blue-on-white SaaS template is forbidden.
Readability rule. Headlines, wordmarks, labels, numbers, and card text and controls stay entirely inside the viewport and their container at 375 px, 768 px, and 1280 px, wrapping or scaling to fit; no other element covers any part of them. Imagery and decoration may be cropped or bled off an edge as the direction asks, but never over readable text or controls.
The public entry is a cream editorial spread with a rust egg basket bleeding off the right edge.
#F5EEDF ground. A 640 px reading measure holds the text column; generous margins at 1280 px, 20 px gutters at 375 px.#221E1A, 56 px on mobile rising to 96 px on wide viewports, over three lines with tight leading and sentence case.#2E6E63 rule, then the subline "Retro Ovos steals eggs automatically. It skips eggs on the ground and keeps a clear status view." in Source Serif 4.#B5502F control labelled "Open control panel" sits under the headline and rule, kept whole at every viewport.#FFFBF2 card with a thick ink top rule and a large Start/Stop switch, with the teal status dot as the running signal.Interaction Model: Animated Motion Tempo: restrained Hero Dimensionality: flat
Landing Hero Motion Brief
prefers-reduced-motion, the fade-and-lift is removed and the hero renders in its final composed arrangement; the status dot on the Control Panel renders static in its teal running colour without pulsing. All content remains fully readable and every control remains whole.prefers-reduced-motion. Rationale: the direction's motion tempo is restrained.frontend, backend, and database. No additional services are required for the current scope; the backend is reused for all feature APIs.Assumptions
Constraints
Future (not current scope, not in current pages or acceptance)
No completed page designs yet.
Completed design pages will appear here when they are ready to preview.
No completed page designs yet.
Completed design pages will appear here when they are ready to preview.
No comments yet. Be the first!