retro-ovos

byKaua Maua625

Script para steal a egg com auto roubar ovos de áreas não de ovos colocados no chão ui inteligente e bonita

No preview

Comments (0)

No comments yet. Be the first!

System Requirements

System Requirements Document for Steal a Egg

1. Introduction

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.

Page 1 of 22

2. System Overview

Steal a Egg is a small, focused tool with two current surfaces and one background automation responsibility.

  • Landing is the anonymous public entry. It explains what the script does, states the egg-area rule plainly (allowed areas versus ground eggs), and offers the call to action that leads into the Control Panel.
  • Control Panel is where the script user starts and stops automatic egg stealing and observes the current status. It is the working surface for the automation and holds the Start/Stop switch and the status readout.
  • Background automation is the script's own egg-stealing process. It runs while the user has started it, selects eggs only from areas that are not egg areas, and never selects eggs placed on the ground. Its state is what the Control Panel reports.

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

  • None. No concept from the authoritative requirement thread was removed or superseded.
Page 2 of 22

2a. Product Interpretation and Delivery Boundary

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.

2b. Source Content Inventory

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.

2c. Page Content and Component Coverage

Page 3 of 22

Landing

Page 4 of 22
  • Information and state. Anonymous public entry. Presents the product name (Retro Ovos / Steal a Egg), the hero headline "Steal eggs from the right areas", the subline "Retro Ovos steals eggs automatically. It skips eggs on the ground and keeps a clear status view.", and the call to action "Open control panel". Explains the two hard rules: eggs are stolen from areas that are not egg areas; eggs placed on the ground are skipped.
  • Primary action. "Open control panel" — navigates to the Control Panel.
  • Supporting actions. Reading the explanation sections; no other commitment is made on this page.
  • Domain entities. None persisted. The page describes the egg-stealing rule set (allowed areas, ground eggs) as content.
  • Component responsibilities.
    • Hero block — oversized Fraunces headline on the left over three lines, rust egg-basket illustration bleeding off the right edge, small teal rule and the CTA beneath the headline.
    • Egg-area rule diagram — a small two-column hand-drawn diagram: allowed areas in teal, ground eggs crossed out in rust.
    • Explanation sections — short prose blocks with hand-drawn egg-mark openers and rust hairline rules, describing automatic stealing and the ground-egg exclusion.
    • CTA control — a single rust action control labelled "Open control panel", kept whole at every viewport.
  • States.
    • Loading — static content; a single slow fade-and-lift on load.
    • Empty — not applicable; the page has fixed explanatory content.
    • Success — the user has read the explanation and can activate the CTA.
    • Error — if navigation to the Control Panel fails, the CTA remains available to retry; no data is lost.
    • Recovery — retry the CTA.
Page 5 of 22

Control Panel

  • Information and state. Shows the current automation status: Stopped (default, before the user starts it) or Running (after the user starts it). The status is shown with a teal status dot when running, and the dot pulses at a 2 s rhythm. The panel also restates the active rule set so the user can confirm what the script will and will not take: eggs from areas that are not egg areas are eligible; eggs placed on the ground are never taken.
  • Primary action. The large Start/Stop switch — starts automatic egg stealing when stopped, stops it when running.
  • Supporting actions. Reading the current status; reading the rule restatement; returning to the Landing page.
  • Domain entities.
    • Automation run state — a single running/stopped condition owned by the backend automation module and persisted in MariaDB so the reported status is authoritative.
    • Egg selection rule — the two hard constraints (non-egg areas only; never ground eggs) applied by the automation.
  • Component responsibilities.
    • Control card — one wide cream card with a thick ink top rule, containing the Start/Stop switch and the status readout.
    • Start/Stop switch — a single large control whose label reflects the available action; it stays entirely inside its container at 375 px, 768 px, and 1280 px.
    • Status readout — text status plus the teal status dot (pulsing at 2 s while running).
    • Rule restatement — the two-column allowed/ground diagram reused from the Landing page, so the user can verify the selection rule while the script runs.
  • States.
Page 6 of 22
  • Loading — while the current status is being fetched, the switch is disabled and the status area shows a neutral loading state.
  • Empty — before any run has been started, status reads Stopped.
  • Success — after Start, status reads Running with the teal pulsing dot; after Stop, status reads Stopped with the dot at rest.
  • Error — if starting or stopping fails, the status readout reports that the change did not take effect and the switch returns to reflecting the last known authoritative status.
  • Recovery — the user can retry the Start/Stop action; the panel re-reads the authoritative status so the displayed state never claims a run that is not actually active.
Page 7 of 22

3. Functional Requirements

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.

  • Provenance: explicit.
  • Lifecycle: the user starts the automation from the Control Panel; the backend automation module performs the stealing; the observable result is the Running status on the Control Panel.
  • Acceptance: while the automation is running, eggs are stolen automatically without further user action.

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.

  • Provenance: explicit (hard constraint).
  • Lifecycle: the rule is applied by the automation on every selection; the Control Panel restates the rule so the user can verify it.
  • Acceptance: eggs located in areas that are not egg areas are eligible for stealing; eggs in egg areas are not selected by this 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.

  • Provenance: explicit (hard constraint).
  • Lifecycle: the rule is applied by the automation on every selection; the Control Panel and Landing page both show ground eggs crossed out in rust.
  • Acceptance: an egg placed on the ground is never stolen, regardless of the automation's running state.
Page 8 of 22

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.

  • Provenance: required_inference.
  • Lifecycle: the user opens the anonymous Landing page, reads the hero and explanation sections, and sees the egg-area rule diagram; the observable result is that the CTA is available.
  • Acceptance: the Landing page states that the script steals eggs automatically, that it steals from areas that are not egg areas, and that it does not steal eggs placed on the ground.

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.

  • Provenance: required_inference.
  • Lifecycle: the user opens the Control Panel, activates the Start/Stop switch while status is Stopped; the backend records the run as active; the observable result is the Running status with the teal pulsing dot.
  • Acceptance: after a successful start, the Control Panel reports Running and the automation is active.

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.

  • Provenance: required_inference.
  • Lifecycle: the user activates the Start/Stop switch while status is Running; the backend records the run as stopped; the observable result is the Stopped status with the dot at rest.
  • Acceptance: after a successful stop, the Control Panel reports Stopped and the automation is inactive.
Page 9 of 22

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.

  • Provenance: required_inference.
  • Lifecycle: the Control Panel reads the authoritative run state from the backend on open and after each Start/Stop action; the observable result is a Stopped or Running readout.
  • Acceptance: the displayed status matches the authoritative run state, and a failed start or stop does not leave the panel claiming a state that is not active.

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.

  • Provenance: explicit.
  • Lifecycle: applies to both current pages; the visual and interaction direction in Sections 6–8 governs.
  • Acceptance: both pages follow the warm editorial direction (cream ground, Fraunces headings, Source Serif 4 body, rust action colour, teal running state), and all readable text and controls remain whole at 375 px, 768 px, and 1280 px.

4. User Personas

Page 10 of 22

Script user

  • Product context. A player of Steal a Egg who wants eggs collected automatically instead of by hand. They came for the automation and stay for a control surface that is calm and readable rather than a raw console.
  • Primary goal. Have the script steal eggs automatically from areas that are not egg areas, while never taking eggs placed on the ground, and be able to start, stop, and confirm that behaviour at a glance.
  • Distinct accepted responsibilities.
    • Reading the Landing page to understand what the script does and which eggs it will and will not take.
    • Starting automatic egg stealing from the Control Panel.
    • Stopping automatic egg stealing from the Control Panel.
    • Reading the current status to confirm whether the script is working.
  • Relevant inputs and decisions. The single decision that matters is whether the automation should be running; the user expresses it through the Start/Stop switch. The user also verifies the rule set (non-egg areas allowed, ground eggs excluded) from the diagram shown on both pages.
  • Interactions with other accepted participants. The only other participant is the script's own background automation, which acts on the user's Start/Stop decision and whose state the user observes. There is no second human participant, no counterparty, and no handoff to another person.
  • Observable success. The Landing page clearly explains the automation and its two rules; the Control Panel shows Running with a teal pulsing dot after Start and Stopped after Stop; ground eggs are never taken.
  • Constraints carried from source. The script steals only from areas that are not egg areas and never steals eggs placed on the ground. No account or identity is required to use either page.

5. Core User Flows

Page 11 of 22

Flow A — Understand the script (Script user)

  1. The Script user opens the Landing page anonymously.
  2. The page fades and lifts once on load; the hero headline "Steal eggs from the right areas" and the subline appear over the cream ground, with the rust egg-basket illustration bleeding off the right edge.
  3. The user reads the explanation sections, each opened by a hand-drawn egg mark and a rust hairline rule, learning that the script steals eggs automatically.
  4. The user reads the egg-area rule diagram: allowed areas in teal, ground eggs crossed out in rust. This confirms the two hard rules — eggs are taken only from areas that are not egg areas, and eggs placed on the ground are never taken.
  5. The user activates the CTA "Open control panel" and continues to Flow B.
  6. Failure/recovery. If navigation fails, the CTA remains available and the user retries; no state is lost because the Landing page holds no user data.
Page 12 of 22

Flow B — Start automatic egg stealing (Script user)

  1. The Script user arrives at the Control Panel from the Landing CTA.
  2. The panel loads the authoritative run state; while loading, the Start/Stop switch is disabled and the status area shows a neutral loading state.
  3. The panel shows Stopped with the status dot at rest, and restates the rule set so the user can confirm what will be taken.
  4. The user activates the large Start/Stop switch on the wide cream control card.
  5. The backend records the run as active and the automation begins stealing eggs automatically, selecting only eggs from areas that are not egg areas and never selecting eggs placed on the ground.
  6. The observable result: the status readout changes to Running and the teal status dot pulses at a 2 s rhythm.
  7. Failure/recovery. If the start request fails, the readout reports that the change did not take effect, the switch returns to reflecting the last known authoritative status, and the user can retry. The panel re-reads the authoritative status so it never claims a run that is not active.
  8. Continuation. The user leaves the panel open to monitor status, or proceeds to Flow C to stop the run.
Page 13 of 22

Flow C — Stop automatic egg stealing (Script user)

  1. With the Control Panel showing Running, the Script user activates the Start/Stop switch again.
  2. The backend records the run as stopped and the automation ceases stealing eggs.
  3. The observable result: the status readout changes to Stopped and the teal status dot comes to rest.
  4. Failure/recovery. If the stop request fails, the readout reports that the change did not take effect and the switch returns to reflecting the last known authoritative status; the user retries. The panel re-reads the authoritative status so the displayed state stays truthful.
  5. Continuation. The user can start again (Flow B) or return to the Landing page.

Flow D — Confirm the current status (Script user)

  1. The Script user opens or returns to the Control Panel.
  2. The panel reads the authoritative run state from the backend.
  3. The observable result: the readout shows Running with the pulsing teal dot, or Stopped with the dot at rest, matching the actual automation state.
  4. Failure/recovery. If the status cannot be read, the panel reports that the status is unavailable rather than showing a guessed state, and the user can retry by reloading or re-opening the panel.
Page 14 of 22

6. Visuals Colors and Theme

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)

RoleHexUse
Background#F5EEDFCream page ground, covers most of the page
Surface#FFFBF2Panels and the wide control card
Text#221E1AInk text and rules, held for contrast
Primary#B5502FRust action colour: CTA, Start/Stop switch, hairline rules, egg-basket illustration
Accent#2E6E63Teal running state: status dot, allowed-area column, small hero rule
Muted#8A7F6ESecondary labels and supporting text

Typography

  • Headings: Fraunces, weight 600, soft optical size, large sizes with tight leading, sentence case only.
  • Body: Source Serif 4.
  • Scale: 1.333 modular — 56 / 40 / 28 / 20 / 17 / 15 px. Mobile headline starts at 40 px; the hero headline scales from 56 px up to 96 px on wide viewports using 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.

Page 15 of 22

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.

Page 16 of 22

7. Signature Design Concept

The public entry is a cream editorial spread with a rust egg basket bleeding off the right edge.

  • Ground and frame. Full-width cream #F5EEDF ground. A 640 px reading measure holds the text column; generous margins at 1280 px, 20 px gutters at 375 px.
  • Headline. On the left, "Steal eggs from the right areas" set in Fraunces 600, ink #221E1A, 56 px on mobile rising to 96 px on wide viewports, over three lines with tight leading and sentence case.
  • Subline and rule. Beneath the headline, a short teal #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.
  • CTA. A rust #B5502F control labelled "Open control panel" sits under the headline and rule, kept whole at every viewport.
  • Illustration. A flat rust egg-basket illustration sits to the right, partly cropped by the edge — the gesture of cropping is carried by the artwork only, never by text or controls.
  • Rule diagram. Below the hero, the egg-area rule appears as a small two-column hand-drawn diagram: allowed areas in teal, ground eggs crossed out in rust.
  • Section openers. Each explanation section opens with a short hand-drawn egg mark and a rust hairline rule.
  • Control panel echo. The Control Panel reuses the same cream ground and the same signature control block: one wide cream #FFFBF2 card with a thick ink top rule and a large Start/Stop switch, with the teal status dot as the running signal.
Page 17 of 22

8. Interaction Model & Motion Direction

Interaction Model: Animated Motion Tempo: restrained Hero Dimensionality: flat

Landing Hero Motion Brief

  • Focal subject. The rust egg-basket illustration bleeding off the right edge, paired with the oversized Fraunces headline on the left.
  • Input → transformation → outcome thesis. On load, the composed hero fades in and lifts once into place; the headline, teal rule, subline, and "Open control panel" CTA settle as a single readable composition, and the egg-area diagram resolves beneath it. No scroll-linked or looping motion is added.
  • Motion vocabulary. One slow fade and lift on load; the status dot pulses at a 2 s rhythm on the Control Panel; no other motion.
  • Composed first frame. Cream ground; ink headline left over three lines; teal rule and rust CTA beneath; rust egg basket cropped at the right edge; hand-drawn egg-area diagram below.
  • Reduced-motion state. With 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.
Page 18 of 22

9. Non-Functional Requirements

  • NFR-1 — Rule enforcement (explicit). The two hard constraints are enforced by the automation itself, not only displayed in the UI: eggs are selected only from areas that are not egg areas, and eggs placed on the ground are never selected. Rationale: the source states both as hard constraints.
  • NFR-2 — Truthful status (required_inference). The Control Panel's displayed status must reflect the authoritative run state held by the backend; a failed start or stop must not leave the panel claiming a state that is not active. Rationale: the user relies on the status to know whether the script is working.
  • NFR-3 — Anonymous access (explicit boundary). Both current pages are reachable without an account; no login, registration, or identity step is introduced. Rationale: the source establishes no identity requirement and none is indispensable for the accepted journeys.
  • NFR-4 — Readability and containment (explicit design constraint). All readable text and controls stay entirely inside the viewport and their container at 375 px, 768 px, and 1280 px, wrapping or scaling to fit; decoration may crop but never covers text or controls. Rationale: stated in the creative direction's readability rule.
  • NFR-5 — Visual direction compliance (explicit). The palette, fonts, shape language, layout, and motion limits in Sections 6–8 are binding; the forbidden looks listed there are excluded. Rationale: the user asked for a smart and beautiful UI and the direction is authoritative.
  • NFR-6 — Restrained motion (explicit). Motion is limited to one slow fade-and-lift on load and the 2 s status-dot pulse, with a usable static arrangement under prefers-reduced-motion. Rationale: the direction's motion tempo is restrained.
Page 19 of 22

10. Tech Stack

  • Frontend: React application rendering the Landing and Control Panel, styled to the warm editorial direction (Fraunces and Source Serif 4, cream/rust/teal tokens).
  • Backend: shared FastAPI process hosting the application APIs and the egg-stealing domain module, including the run-state control endpoints and the automation that applies the two selection rules.
  • Database: MariaDB for application-owned persistent data, holding the authoritative automation run state.
  • Orchestration: docker-compose with the three provisioned services — frontend, backend, and database. No additional services are required for the current scope; the backend is reused for all feature APIs.
Page 20 of 22

11. Assumptions and Constraints

Assumptions

  • [Assumption — required_inference] The automation's run state is a single running/stopped condition, which is why the Control Panel needs no per-user identity to resume or protect it.
  • [Assumption — required_inference] The Control Panel is reached from the Landing CTA and is also directly reachable, since no identity gate exists.
  • [Assumption — required_inference] "Areas that are not egg areas" and "eggs placed on the ground" are the two selection categories the automation distinguishes; the UI presents them as the allowed/ground diagram.

Constraints

  • The script steals eggs only from areas that are not egg areas (explicit, hard).
  • The script does not steal eggs placed on the ground (explicit, hard).
  • Both current pages are anonymous; no account-management capability is added.
  • The visual direction in Sections 6–8 is binding, including the forbidden looks and the readability rule.

Future (not current scope, not in current pages or acceptance)

  • No future requirements were stated in the authoritative thread. Any extension beyond automatic stealing, the two selection rules, and the Landing/Control Panel UI would be a new requirement and is out of scope here.
Page 21 of 22

12. Glossary

  • Steal a Egg — the game the script is built for.
  • Script — the product's automation that steals eggs on the user's behalf.
  • Egg area — a game area that is an egg area; eggs there are not stolen by this script's area rule.
  • Non-egg area — an area that is not an egg area; eggs there are eligible for automatic stealing.
  • Ground egg — an egg placed on the ground; never stolen by the script.
  • Automation run state — the authoritative running/stopped condition of the script, held by the backend and shown on the Control Panel.
  • Control Panel — the page where the user starts and stops automatic egg stealing and reads the current status.
  • Landing — the anonymous public entry page that explains the script and links to the Control Panel.
  • Script user — the sole active human persona: a player who wants automatic egg stealing and a smart, attractive control UI.
Page 22 of 22

No completed page designs yet.

Completed design pages will appear here when they are ready to preview.

Landing: 1. Read hero explanation

Landing: 2. Review egg-area rule diagram

Landing: 3. Open control panel

Landing: 4. Retry opening control panel

Control Panel: 5. Wait for status to load

Control Panel: 6. Confirm stopped status and rules

Control Panel: 7. Start automatic egg stealing

Control Panel: 8. Confirm running status

Control Panel: 9. Retry start after failure

Control Panel: 10. Stop automatic egg stealing

Control Panel: 11. Confirm stopped status

Control Panel: 12. Retry stop after failure

Control Panel: 13. Reopen to confirm current status

Control Panel: 14. Retry reading unavailable status

Control Panel: 15. Return to landing page

No completed page designs yet.

Completed design pages will appear here when they are ready to preview.

Landing: 1. Read hero explanation

Landing: 2. Review egg-area rule diagram

Landing: 3. Open control panel

Landing: 4. Retry opening control panel

Control Panel: 5. Wait for status to load

Control Panel: 6. Confirm stopped status and rules

Control Panel: 7. Start automatic egg stealing

Control Panel: 8. Confirm running status

Control Panel: 9. Retry start after failure

Control Panel: 10. Stop automatic egg stealing

Control Panel: 11. Confirm stopped status

Control Panel: 12. Retry stop after failure

Control Panel: 13. Reopen to confirm current status

Control Panel: 14. Retry reading unavailable status

Control Panel: 15. Return to landing page