System Requirements Document for cherry-hub-gui

1. Introduction

cherry-hub-gui delivers a single Lua script that, when executed inside a Roblox environment, constructs and displays a graphical user interface named exactly "Cherry Hub\x20\xf0\x9f\x8c\xb8". The hub is a floating, glossy, candy-pink control panel that a player uses to toggle and tune a broad set of movement, world, and visual utility features while remaining inside the game world.

The product intent is playful and expressive rather than utilitarian: the GUI must be extremely dynamic with motion animations, must ship with an original coquette pink (rosinha) theme, must support minimize and maximize, and must allow the user to customize everything about its appearance and behavior. The audience is the player who runs the Lua script — a young, mobile-first Roblox user who wants a hub that feels like a toy: glossy, bouncy, alive, and unmistakably not a default Roblox UI.

This document specifies the script's behavior, its single cohesive GUI surface, the closed persona set, the accepted feature catalog, and the visual, motion, and interaction direction that governs how the hub looks and feels.

2. System Overview

The product is a client-side Lua script that builds a runtime GUI. There is no server, no account system, no network service, and no persistent backend. The script runs in the Roblox environment where the user executes it; the GUI it creates is the entire product surface.

Actors:

• Script Executor / Hub User — the accepted human persona. This person runs the Lua script and interacts with the "Cherry Hub\x20\xf0\x9f\x8c\xb8" GUI: opening it, using the coquette-pink themed interface, toggling and tuning movement and utility features, customizing the GUI's appearance, and minimizing/maximizing it as needed.
• Roblox runtime — the non-persona host environment that provides the player character, camera, and world state the hub's features act upon. It is not a human actor and owns no product UI.

Accepted behavior: the hub loads and animates smoothly; every feature can be toggled and tuned from the GUI; the GUI can be minimized to a floating cherry icon and maximized back; and the user can recolor and reshape the GUI live.

Ownership: the single cohesive local-device GUI is the anonymous first impression and workspace. It is the only first-party surface. There is no login, no account, and no protected destination — the hub is available immediately upon script execution.

Narrow exclusions: this document does not add server-side persistence, multiplayer coordination, account management, telemetry, or any capability beyond the accepted feature catalog and the customization/minimize/maximize requirements.

2a. Product Interpretation and Delivery Boundary

The delivery is a Lua script — the user's explicit request — that produces a client-side GUI inside Roblox. The GUI is the product. It is delivered as a single script the user runs; there is no separate web app, no backend service, and no deployment pipeline in the accepted scope.

Access ownership: the hub is anonymous and local. It requires no identity, no login, and no account. The GUI appears when the script executes and is immediately usable. This is consistent with the accepted access requirement of none for the "Cherry Hub\x20\xf0\x9f\x8c\xb8" surface.

Current vs. future boundary: everything specified in this document is current. The user asked for "TODAS as funções POSSÍVEIS" (all possible functions) and named a representative set (Fly, fly speed, Jump, Infinite Jump, Jump weight, Walk speed, Noclip, Sit, ESP, toggles). The accepted current catalog is enumerated in Section 3. Any feature not enumerated there is future and must not appear in current pages or acceptance.

2b. Source Content Inventory

Not applicable. No reference directive in this project declares a content_source; the authoritative content is the user requirement thread itself, which is fully represented in Sections 3, 4, and 5.

2c. Page Content and Component Coverage

The reconciled page inventory contains exactly one page, matching the versioned page contract.

Cherry Hub\x20\xf0\x9f\x8c\xb8

The single cohesive local-device GUI. It is the anonymous first impression and the workspace for launching, animating, customizing, minimizing, maximizing, toggling, and tuning the requested Roblox utility features, with a coquette pink default theme.

Information and state

• Wordmark "cherry hub\x20\xf0\x9f\x8c\xb8" set oversized in Comfortaa Black, with the\x20\xf0\x9f\x8c\xb8 glyph floating above the baseline and rotating slowly.
• Current active tab (Movement, Combat, Visual, World, GUI Theme, Customize).
• Per-feature state: on/off for toggles; current numeric value for sliders (fly speed, jump weight, walk speed, etc.).
• Live customization state: background colour, accent colour, panel radius, blur amount, animation speed, font size.
• Panel state: expanded, minimized (56px floating cherry icon), maximized.

Primary actions

• Drag the panel by its header to reposition it.
• Minimize (—) and maximize (\xe2\x9b\xb6) via capsule buttons in the header.
• Switch tabs via the horizontal pill tab bar.
• Toggle any feature on/off via its pill-shaped candy toggle.
• Adjust any numeric feature via its blob-thumb slider.
• Open the Customize tab and change background colour, accent colour, panel radius, blur amount, animation speed, and font size — all applied live.

Supporting actions

• Quick-start capsule chips (Fly, Speed, ESP, Noclip) above the tab bar for one-tap activation of common features.
• Hover on any feature row lifts it 2px and grows a 3px magenta bar on its left edge.
• Scroll the panel body when content exceeds max-height.

Domain entities

• Feature — a named toggle or slider (Fly, Fly Speed, Jump, Infinite Jump, Jump Weight, Walk Speed, Noclip, Sit, ESP, and the remaining accepted catalog).
• Tab — a named group of features (Movement, Combat, Visual, World, GUI Theme, Customize).
• Theme — the set of live-editable appearance values (background colour, accent colour, panel radius, blur, animation speed, font size).
• Panel state — expanded / minimized / maximized, plus position.

Component responsibilities

• Header — glossy white, 24px bottom radius; wordmark left; minimize and maximize capsule buttons right; drag handle.
• Quick-start chip row — 4 capsule chips with glossy highlight sweep on hover.
• Tab bar — horizontal pill tabs that scroll horizontally at 375px; active pill morphs its width to fit the label.
• Feature row — label left, toggle or slider right, 12px gap; pill toggle with candy knob; blob-thumb slider with magenta→pink gradient fill.
• Customize panel — colour swatches and sliders for background colour, accent colour, panel radius, blur amount, animation speed, font size.
• Minimized state — a single 56px cherry icon with a leaf, spring-animated.
• Decorative layer — soft radial pink glow behind the panel; three large blurred pink blobs drifting on a 20s loop; petal particles (max 6, 8px, #FFB3D1) on feature activation.

States

• Loading: the script builds the GUI; the panel enters from the bottom-left with a scale-from-0.85 spring overshoot (420ms), tilted -2deg settling to 0deg.
• Empty: each tab shows a petal SVG empty-state illustration when it has no features to display (only relevant if a tab is emptied by future configuration).
• Success: toggling a feature on plays a 180ms knob squash-and-stretch with a 1.06 row pulse and releases a 6-petal pink confetti burst; the row's icon tints #FF3D7F.
• Error: if a feature cannot be applied in the current environment (e.g., the character is unavailable), the toggle reverts to its previous state and the row shows a muted #C48AA8 disabled treatment; the user can retry by toggling again.
• Recovery: the user can re-toggle any feature, re-open the Customize tab to reset appearance values, or minimize/maximize to reset the panel layout.

3. Functional Requirements

Each requirement is a distinct story point with provenance, lifecycle facts, and observable acceptance.

FR-1 — Script creates the named GUI (explicit) As a Script Executor / Hub User, I should run a Lua script that creates a GUI named exactly "Cherry Hub\x20\xf0\x9f\x8c\xb8", so that I have a single hub surface for all features.

• Trigger: the user executes the Lua script in a Roblox environment.
• Observable result: a GUI titled "Cherry Hub\x20\xf0\x9f\x8c\xb8" appears in the viewport.
• Access state: anonymous, local, no login.
• Failure/recovery: if the script errors, no GUI appears; the user re-runs the script.
• Continuation: the user interacts with the hub.

FR-2 — Extremely dynamic motion animations (explicit) As a Script Executor / Hub User, I should see the GUI animate with extremely dynamic motion animations, so that the hub feels alive and playful.

• Trigger: panel open, tab switch, toggle, slider grab, minimize, maximize, feature activation, hover.
• Observable result: the panel enters with a spring overshoot; tabs slide and fade; toggles squash-and-stretch; sliders grow on grab; minimize/maximize spring; feature activation releases a petal burst; hover lifts rows.
• Access state: anonymous, local.
• Failure/recovery: with prefers-reduced-motion, transitions become 0ms, petals are suppressed, and the\x20\xf0\x9f\x8c\xb8 stops rotating — the GUI remains fully usable.
• Continuation: the user continues interacting.

FR-3 — Original coquette pink theme (explicit) As a Script Executor / Hub User, I should see the GUI ship with an original coquette pink (rosinha) theme by default, so that the hub matches the requested aesthetic on first open.

• Trigger: first render of the GUI.
• Observable result: background #FCE7F0, surfaces #FFFFFF, primary #FF6FA5, accent #FF3D7F, text #3D1F2E, muted #C48AA8; Comfortaa headings, Quicksand body.
• Access state: anonymous, local.
• Failure/recovery: if a font fails to load, the GUI falls back to a rounded sans-serif while preserving the palette.
• Continuation: the user may customize the theme (FR-4).

FR-4 — Everything is customizable (explicit) As a Script Executor / Hub User, I should be able to customize everything about the GUI, so that the hub matches my personal taste.

• Trigger: the user opens the Customize tab.
• Observable result: background colour, accent colour, panel radius, blur amount, animation speed, and font size are all adjustable via colour swatches and sliders, and every value is live-applied.
• Access state: anonymous, local.
• Failure/recovery: if a value is out of range, the slider clamps to its bounds and the GUI keeps the last valid value.
• Continuation: the user continues using the hub with the new appearance.

FR-5 — Minimize and maximize (explicit) As a Script Executor / Hub User, I should be able to minimize and maximize the GUI, so that I can reclaim screen space and restore the hub at will.

• Trigger: the user presses the minimize (—) or maximize (\xe2\x9b\xb6) capsule button in the header.
• Observable result: minimize collapses the panel to a 56px floating cherry icon with a spring; maximize expands it back with the same spring.
• Access state: anonymous, local.
• Failure/recovery: if the panel is already minimized, the maximize control restores it; the minimized icon remains draggable.
• Continuation: the user continues interacting with the hub in either state.

FR-6 — Fly (explicit) As a Script Executor / Hub User, I should toggle Fly on and off, so that my character can fly.

• Trigger: the user toggles the Fly feature.
• Observable result: the toggle switches on with a squash-and-stretch animation and a petal burst; the character gains flight.
• Access state: anonymous, local.
• Failure/recovery: if the character is unavailable, the toggle reverts and the row shows a disabled treatment.
• Continuation: the user may adjust Fly Speed (FR-7) or toggle Fly off.

FR-7 — Fly speed (explicit) As a Script Executor / Hub User, I should adjust fly speed with a slider, so that I can control how fast I fly.

• Trigger: the user drags the Fly Speed slider.
• Observable result: the thumb grows 1.15x on grab; the track fills with an animated magenta→pink gradient; the numeric value updates live.
• Access state: anonymous, local.
• Failure/recovery: the slider clamps to its bounds.
• Continuation: the user continues flying at the new speed.

FR-8 — Jump (explicit) As a Script Executor / Hub User, I should toggle Jump, so that I can control whether my character jumps.

• Trigger: the user toggles the Jump feature.
• Observable result: the toggle switches with the standard animation; jump behavior is enabled or disabled.
• Access state: anonymous, local.
• Failure/recovery: if the character is unavailable, the toggle reverts.
• Continuation: the user may adjust Jump Weight (FR-10).

FR-9 — Infinite Jump (explicit) As a Script Executor / Hub User, I should toggle Infinite Jump, so that my character can jump repeatedly without touching the ground.

• Trigger: the user toggles the Infinite Jump feature.
• Observable result: the toggle switches with the standard animation; infinite jump is enabled or disabled.
• Access state: anonymous, local.
• Failure/recovery: if the character is unavailable, the toggle reverts.
• Continuation: the user continues playing.

FR-10 — Jump weight (explicit) As a Script Executor / Hub User, I should adjust jump weight with a slider, so that I can control how heavy my jumps feel.

• Trigger: the user drags the Jump Weight slider.
• Observable result: the thumb grows on grab; the track fills with the animated gradient; the numeric value updates live.
• Access state: anonymous, local.
• Failure/recovery: the slider clamps to its bounds.
• Continuation: the user continues playing.

FR-11 — Walk speed (explicit) As a Script Executor / Hub User, I should adjust walk speed with a slider, so that I can control how fast my character walks.

• Trigger: the user drags the Walk Speed slider.
• Observable result: the thumb grows on grab; the track fills with the animated gradient; the numeric value updates live.
• Access state: anonymous, local.
• Failure/recovery: the slider clamps to its bounds.
• Continuation: the user continues playing.

FR-12 — Noclip (explicit) As a Script Executor / Hub User, I should toggle Noclip, so that my character can pass through solid objects.

• Trigger: the user toggles the Noclip feature.
• Observable result: the toggle switches with the standard animation; noclip is enabled or disabled.
• Access state: anonymous, local.
• Failure/recovery: if the character is unavailable, the toggle reverts.
• Continuation: the user continues playing.

FR-13 — Sit (explicit) As a Script Executor / Hub User, I should toggle Sit, so that my character can sit on command.

• Trigger: the user toggles the Sit feature.
• Observable result: the toggle switches with the standard animation; the character sits or stands.
• Access state: anonymous, local.
• Failure/recovery: if the character is unavailable, the toggle reverts.
• Continuation: the user continues playing.

FR-14 — ESP (explicit) As a Script Executor / Hub User, I should toggle ESP, so that I can see visual overlays for tracked entities.

• Trigger: the user toggles the ESP feature.
• Observable result: the toggle switches with the standard animation; ESP overlays appear or disappear. The ESP feature chip may use the secondary glossy mint #B8F2E6 as a counter-colour.
• Access state: anonymous, local.
• Failure/recovery: if the environment does not support the overlay, the toggle reverts.
• Continuation: the user continues playing.

FR-15 — Toggles for all accepted features (explicit) As a Script Executor / Hub User, I should have a toggle for every accepted feature, so that I can switch any feature on or off from the hub.

• Trigger: the user interacts with any feature row's toggle.
• Observable result: the pill toggle's candy knob squashes on press; the row pulses 1.06; a 6-petal pink confetti burst releases when switched on; the row's icon tints #FF3D7F when active and #C48AA8 when off.
• Access state: anonymous, local.
• Failure/recovery: if a feature cannot be applied, the toggle reverts and the row shows a disabled treatment.
• Continuation: the user continues using the hub.

FR-16 — Additional possible functions (explicit) As a Script Executor / Hub User, I should have as many additional utility functions as possible beyond the named set, so that the hub is a comprehensive toolbox.

• Trigger: the user browses the tabs.
• Observable result: additional features are grouped under the Movement, Combat, Visual, World, and GUI Theme tabs, each with its own toggle or slider.
• Access state: anonymous, local.
• Failure/recovery: any feature that cannot be applied reverts and shows a disabled treatment.
• Continuation: the user continues using the hub.

FR-17 — Tab navigation (explicit) As a Script Executor / Hub User, I should switch between tabs (Movement, Combat, Visual, World, GUI Theme, Customize), so that I can reach every feature group.

• Trigger: the user taps a tab in the horizontal pill tab bar.
• Observable result: the active pill morphs its width to fit the label; the outgoing content slides 24px horizontally and fades in 220ms; the incoming content appears.
• Access state: anonymous, local.
• Failure/recovery: at 375px the tab bar scrolls horizontally so every tab remains reachable.
• Continuation: the user interacts with the features in the new tab.

FR-18 — Panel drag (explicit) As a Script Executor / Hub User, I should drag the panel by its header, so that I can reposition the hub.

• Trigger: the user drags the header.
• Observable result: the panel follows the pointer and stays within the viewport.
• Access state: anonymous, local.
• Failure/recovery: the panel clamps to the viewport edges.
• Continuation: the user continues using the hub at the new position.

FR-19 — Quick-start chips (explicit) As a Script Executor / Hub User, I should use quick-start capsule chips (Fly, Speed, ESP, Noclip) above the tab bar, so that I can activate common features with one tap.

• Trigger: the user taps a quick-start chip.
• Observable result: the corresponding feature toggles; the chip shows a glossy highlight sweep on hover.
• Access state: anonymous, local.
• Failure/recovery: if the feature cannot be applied, the chip reverts.
• Continuation: the user continues playing.

FR-20 — Responsive layout (explicit) As a Script Executor / Hub User, I should have the hub adapt to my viewport, so that it is usable on mobile and desktop.

• Trigger: the viewport changes size.
• Observable result: at 375px the panel is a bottom-sheet (full-width, 88vh, drag handle at top); at 768px it widens to 420px; at 1280px it stays a floating panel (never full-width) so the game world stays visible behind it.
• Access state: anonymous, local.
• Failure/recovery: readable text and controls stay whole at every viewport; the tab bar scrolls horizontally when needed.
• Continuation: the user continues using the hub.

4. User Personas

Script Executor / Hub User

Product context. This person runs Lua scripts inside a Roblox environment. They are young, mobile-first, and treat the hub as a toy rather than a tool. They expect the GUI to feel glossy, bouncy, and alive — not like a default Roblox UI or a SaaS dashboard.

Primary goal. Open the hub, use the coquette-pink themed interface, toggle and adjust movement and utility features (Fly, fly speed, Jump, Infinite Jump, Jump weight, Walk speed, Noclip, Sit, ESP, toggles), and customize the GUI's appearance, minimizing and maximizing it as needed. Success means the hub loads, animates smoothly, and every feature can be toggled and tuned from the GUI.

Distinct accepted responsibilities.

• Execute the Lua script to create the "Cherry Hub\x20\xf0\x9f\x8c\xb8" GUI.
• Toggle features on and off via pill-shaped candy toggles.
• Tune numeric features (fly speed, jump weight, walk speed) via blob-thumb sliders.
• Switch between tabs (Movement, Combat, Visual, World, GUI Theme, Customize).
• Customize the GUI's appearance live via the Customize tab.
• Minimize the panel to a floating cherry icon and maximize it back.
• Drag the panel to reposition it.
• Use quick-start chips for one-tap activation of common features.

Relevant inputs or decisions.

• Which features to enable or disable.
• What numeric values to set for sliders.
• Which appearance values to change (background colour, accent colour, panel radius, blur, animation speed, font size).
• When to minimize or maximize the panel.

Interactions with other accepted participants. None. The hub is a single-user, local, anonymous surface. The Roblox runtime is a non-persona host environment, not a participant.

Observable success. The hub loads with a spring-overshoot entrance, animates smoothly, every feature toggles and tunes from the GUI, the theme recolours live when customized, and minimize/maximize spring cleanly between the panel and the cherry icon.

5. Core User Flows

Flow 1 — Open the hub

1. The Script Executor / Hub User executes the Lua script in a Roblox environment.
2. The script builds the "Cherry Hub\x20\xf0\x9f\x8c\xb8" GUI.
3. The panel enters from the bottom-left corner of the viewport as a glossy white capsule-topped card with a 28px radius, tilted -2deg on entry then settling to 0deg, scaling from 0.85 with a soft overshoot (cubic-bezier(0.34, 1.56, 0.64, 1)), 420ms.
4. Behind the panel, a full-viewport soft radial gradient of #FCE7F0 → #FFD6E6 with three large blurred pink blobs (200–320px, 80px blur) drifts on a 20s loop.
5. The wordmark "cherry hub\x20\xf0\x9f\x8c\xb8" appears in Comfortaa Black with the\x20\xf0\x9f\x8c\xb8 glyph floating 8px above the baseline, rotating slowly (8s loop) and bobbing 2px; a 1px magenta underline draws itself on first reveal.
6. Result: the hub is open and ready. Next step: the user toggles a feature or switches tabs.

Flow 2 — Toggle a feature

1. The user is on any tab (e.g., Movement).
2. The user taps the pill-shaped toggle for a feature (e.g., Fly).
3. The candy knob squashes on press; the row pulses 1.06; a 6-petal pink confetti burst releases; the row's icon tints #FF3D7F.
4. Result: the feature is on. Next step: the user adjusts its slider (Flow 3) or toggles another feature.

Flow 3 — Tune a numeric feature

1. The user is on a tab containing a slider (e.g., Fly Speed).
2. The user grabs the blob thumb.
3. The thumb grows 1.15x; the track fills with an animated magenta→pink gradient; the numeric value updates live.
4. Result: the feature uses the new value. Next step: the user continues playing or tunes another slider.

Flow 4 — Switch tabs

1. The user is on any tab.
2. The user taps a different tab in the horizontal pill tab bar.
3. The active pill morphs its width to fit the new label; the outgoing content slides 24px horizontally and fades in 220ms; the incoming content appears.
4. Result: the new tab is active. Next step: the user interacts with the new tab's features.

Flow 5 — Customize the GUI

1. The user opens the Customize tab.
2. The user adjusts background colour, accent colour, panel radius, blur amount, animation speed, or font size via colour swatches and sliders.
3. Every value is live-applied — the GUI recolours itself in front of the user.
4. Result: the GUI reflects the new appearance. Next step: the user continues using the hub with the new look.

Flow 6 — Minimize and maximize

1. The user presses the minimize (—) capsule button in the header.
2. The panel collapses to a 56px floating cherry icon with a spring.
3. The user presses the cherry icon (or its maximize control).
4. The panel expands back with the same spring.
5. Result: the panel is restored. Next step: the user continues using the hub.

Flow 7 — Drag the panel

1. The user drags the panel by its header.
2. The panel follows the pointer and clamps to the viewport edges.
3. Result: the panel is repositioned. Next step: the user continues using the hub.

Flow 8 — Use quick-start chips

1. The user taps a quick-start capsule chip (Fly, Speed, ESP, Noclip) above the tab bar.
2. The corresponding feature toggles; the chip shows a glossy highlight sweep on hover.
3. Result: the feature is on. Next step: the user continues playing.

Flow 9 — Reduced-motion fallback

1. The user's environment has prefers-reduced-motion enabled.
2. Transitions become 0ms; petals are suppressed; the\x20\xf0\x9f\x8c\xb8 stops rotating.
3. Result: the GUI is static but fully usable. Next step: the user continues using the hub normally.

6. Visuals Colors and Theme

The creative direction is authoritative for this section. The muse is Karim Rashid; the headline is "Sensual pop minimalism in cherry-blossom pink — a hub that feels like candy you can play with."

Palette (light mode)

• Background: #FCE7F0 (cherry-blossom pink ground)
• Surface: #FFFFFF (pure white glossy panels)
• Text: #3D1F2E (deep plum-rose; ≥7:1 on white, ≥4.5:1 on the pink ground)
• Primary: #FF6FA5 (candy pink for toggles, sliders, active states)
• Accent: #FF3D7F (hot magenta for the title, focus rings, and the 'on' pulse of every switch)
• Muted: #C48AA8 (dusty rose for labels, dividers, inactive tracks)
• Secondary counter-colour: #B8F2E6 (glossy mint, allowed only inside ESP/visual feature chips, never as a surface)
• Panel inner border: #FFD6E6
• Panel shadow: 0 8px 24px rgba(255,111,165,0.18)
• Petal particles: #FFB3D1

Typography

• Headings: Comfortaa — rounded futuristic display, bold-to-black weights, generous letter-spacing on the wordmark, lowercase-biased. "cherry hub" set in Comfortaa Bold; the\x20\xf0\x9f\x8c\xb8 emoji floats as a glyph that orbits the wordmark. Section headers in Comfortaa SemiBold at 18–22px with a 1px pink underline that draws itself on reveal.
• Body: Quicksand.
• Scale: 1.25 modular, mobile-first — title clamp(34px, 5vw, 56px); section header 18px → 22px; tab label 13px → 15px; toggle label 13px → 14px; slider value 12px → 13px tabular; helper text 11px → 12px.

Shape language

• Blobs and capsules everywhere. Every panel is a rounded-rect with a 22–28px radius, glossy white fill, a 1px #FFD6E6 inner border, and a soft pink offset shadow.
• Toggles are pill-shaped with a glossy candy knob that squashes on press.
• Sliders have a blob thumb.
• Section boundaries are curved SVG wave dividers, never straight lines.
• Buttons are capsules; the primary CTA is a wide capsule with a moving glossy highlight sweep.
• No sharp corners anywhere — the only sharp element is the thin 2px magenta focus ring, used as a deliberate accent.

Spacing rhythm

• Feature rows: 12px gap between label and control.
• Panel body: scrollable when content exceeds max-height (78vh desktop, 88vh mobile).
• Header: 24px bottom radius.

Imagery style

• No photography. The imagery is the GUI itself: glossy 3D-ish candy blobs, cherry and petal SVG shapes used as decorative accents behind the header and as empty-state illustrations for each tab, and a soft radial pink glow behind the panel.
• Petal particles (max 6, 8px, #FFB3D1) drift upward on feature activation.
• The minimize state is a single cherry icon with a leaf.
• Icons for each feature are thick-line rounded glyphs (Lucide-style, 3px stroke, rounded caps) tinted #FF3D7F when active and #C48AA8 when off.

Avoid: default Roblox UI greys, blues, or the stock Roblox toggle style; any blue/indigo primary (#0057FF, #2563EB, #6366F1, etc.) on a white or near-white ground; Inter, Roboto, Arial, Helvetica, Open Sans, Lato, Poppins, or system-ui for any heading or body text; flat, sharp-cornered rectangles or a grid of identical hover-lift cards; gradient-blob heroes or generic SaaS centred headline + subtext + button stacks; photographic imagery, stock people, or realistic 3D renders of humans; heavy backdrop blur that drops below 30fps on low-end mobile devices (cap blur radius at 12px and degrade gracefully); motion that ignores prefers-reduced-motion.

7. Signature Design Concept

The "hero" is the floating Cherry Hub panel itself, not a marketing page.

Composition. The panel enters from the bottom-left corner of the viewport as a glossy white capsule-topped card with a 28px radius, tilted -2deg on entry then settling to 0deg. Dominant element: the wordmark "cherry hub\x20\xf0\x9f\x8c\xb8" set at clamp(34px, 5vw, 56px) in Comfortaa Black, deep plum-rose, with the\x20\xf0\x9f\x8c\xb8 glyph floating 8px above the baseline and rotating slowly. Behind the panel, a full-viewport soft radial gradient of #FCE7F0 → #FFD6E6 with three large blurred pink blobs (200–320px, 80px blur) drifting on a 20s loop. A row of 4 quick-start capsule chips (Fly, Speed, ESP, Noclip) sits just above the panel's tab bar, each with a glossy highlight sweep on hover.

Signature moves.

• The entire hub is a floating glossy pink capsule-panel that enters with a spring overshoot and can be dragged, minimized to a single rotating cherry icon, and maximized back — the minimize/maximize transition is the signature motion, not a fade.
• Every feature row is a pill-shaped toggle with a candy knob that squashes on press and releases a 6-petal pink confetti burst when switched on; the row's left edge grows a 3px magenta bar on hover.
• A live Customize tab where background colour, accent colour, panel radius, blur, animation speed, and font size are all adjustable with colour swatches and sliders that apply instantly — the GUI recolours itself in front of the user.
• The wordmark "cherry hub\x20\xf0\x9f\x8c\xb8" is set oversized in Comfortaa Black with a\x20\xf0\x9f\x8c\xb8 glyph that orbits and bobs independently of the text, and a 1px magenta underline that draws itself on first reveal.
• Tab switching uses a morphing pill indicator that stretches to the new label's width while the outgoing content slides and fades — no static tab bar anywhere.

Constraint. No centered headline, no blue button, no gradient blob hero — the panel is the subject and it is unmistakably a playable pink toy. Readable text and controls stay whole at every viewport (375px, 768px, 1280px); imagery, decoration, and motion may be cropped, bled, rotated, or overlapped as the direction asks, as long as they cover no readable text or control.

8. Interaction Model & Motion Direction

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

Landing Hero Motion Brief

• Focal subject: the floating Cherry Hub panel itself, with the wordmark "cherry hub\x20\xf0\x9f\x8c\xb8" as the dominant element and the\x20\xf0\x9f\x8c\xb8 glyph orbiting and bobbing independently.
• Input → transformation → outcome thesis: the user executes the script → the panel enters from the bottom-left with a scale-from-0.85 spring overshoot (420ms, cubic-bezier(0.34, 1.56, 0.64, 1)), tilted -2deg settling to 0deg → the hub is open and ready, with the wordmark's\x20\xf0\x9f\x8c\xb8 rotating slowly (8s loop) and bobbing 2px, and the 1px magenta underline drawing itself on first reveal.
• Motion vocabulary: expressive and liquid. Panel entrance: scale from 0.85 with a soft overshoot, 420ms. Tab switch: content slides 24px horizontally and fades in 220ms, with the active pill morphing its width to fit the label. Every toggle: 180ms knob squash-and-stretch with a 1.06 scale pulse on the whole row. Sliders: thumb grows 1.15x on grab, track fills with a magenta→pink gradient that animates. Minimize: panel collapses to a 56px floating cherry icon with a spring; maximize: expands back with the same spring. Feature activation: a tiny confetti burst of 6 pink petals from the toggle. Hover on any row: the row lifts 2px and its left edge grows a 3px magenta bar. The wordmark's\x20\xf0\x9f\x8c\xb8 rotates slowly (8s loop) and bobs 2px.
• Composed first frame: the panel at rest in the bottom-left, glossy white capsule-topped card with a 28px radius, wordmark "cherry hub\x20\xf0\x9f\x8c\xb8" in Comfortaa Black,\x20\xf0\x9f\x8c\xb8 glyph floating 8px above the baseline, quick-start chips above the tab bar, three blurred pink blobs drifting behind, soft radial pink glow.
• Reduced-motion state: transitions become 0ms, petals are suppressed, the\x20\xf0\x9f\x8c\xb8 stops rotating; the GUI is static but fully usable, and the tab bar scrolls horizontally so every tab remains reachable.

9. Non-Functional Requirements

NFR-1 — Performance on low-end mobile (explicit, from creative direction) The GUI must not drop below 30fps on low-end mobile devices. Backdrop blur radius is capped at 12px and degrades gracefully. Rationale: the audience is mobile-first and the direction explicitly warns against heavy blur.

NFR-2 — Reduced-motion accessibility (explicit, from creative direction) All motion must respect prefers-reduced-motion: transitions become 0ms, petals are suppressed, and the\x20\xf0\x9f\x8c\xb8 stops rotating. Rationale: the direction requires a static, usable fallback.

NFR-3 — Readable text and controls at every viewport (explicit, from creative direction) Headlines, wordmarks, labels, numbers, cards' text and controls must 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 may cover any part of them. Rationale: the direction's readability rule takes precedence over decorative cropping.

NFR-4 — Contrast (explicit, from creative direction) Text must maintain ≥7:1 contrast on white surfaces and ≥4.5:1 on the pink ground. Rationale: the direction specifies these ratios for the deep plum-rose text.

NFR-5 — Anonymous local access (explicit, from planning scope) The GUI requires no login, no account, and no network. It appears when the script executes and is immediately usable. Rationale: the accepted access requirement for the "Cherry Hub\x20\xf0\x9f\x8c\xb8" surface is none.

NFR-6 — Single-script delivery (explicit) The product is delivered as a Lua script that creates the GUI. Rationale: the user explicitly requested a Lua script.

10. Tech Stack

• Language: Lua (explicitly requested by the user).
• Runtime: Roblox environment (the host that provides the player character, camera, and world state the hub's features act upon).
• GUI: Roblox GUI primitives (the script builds the interface at runtime).
• Fonts: Comfortaa (headings) and Quicksand (body), per the creative direction.
• No backend, no database, no container, no deployment pipeline — the accepted scope is a single client-side script.

11. Assumptions and Constraints

Assumptions

• The user has a Roblox environment in which to execute the Lua script.
• The Roblox runtime provides the player character, camera, and world state the hub's features act upon.
• The user's device supports the fonts and animations specified; if not, the fallbacks in NFR-1 and NFR-2 apply.

Constraints

• The GUI name must be exactly "Cherry Hub\x20\xf0\x9f\x8c\xb8" (explicit).
• The default theme must be coquette pink (rosinha) (explicit).
• The GUI must be extremely dynamic with motion animations (explicit).
• All GUI aspects must be customizable (explicit).
• Minimize and maximize must be supported (explicit).
• The delivery is a Lua script (explicit).
• The generic indigo/blue-on-white SaaS template is forbidden for this project (explicit, from creative direction).

Future (not current)

• Any feature not enumerated in Section 3 is future and must not appear in current pages or acceptance.
• Server-side persistence, multiplayer coordination, account management, and telemetry are out of scope.

12. Glossary

• Cherry Hub\x20\xf0\x9f\x8c\xb8 — the exact name of the GUI created by the Lua script.
• Coquette pink (rosinha) — the default theme: cherry-blossom pink ground, glossy white panels, candy pink primary, hot magenta accent, deep plum-rose text.
• Feature — a named toggle or slider in the hub (e.g., Fly, Fly Speed, Jump, Infinite Jump, Jump Weight, Walk Speed, Noclip, Sit, ESP).
• Tab — a named group of features: Movement, Combat, Visual, World, GUI Theme, Customize.
• Theme — the set of live-editable appearance values: background colour, accent colour, panel radius, blur amount, animation speed, font size.
• Panel state — expanded, minimized (56px floating cherry icon), or maximized.
• Petal burst — the 6-petal pink confetti animation released when a feature is switched on.
• Quick-start chip — a capsule chip above the tab bar for one-tap activation of a common feature (Fly, Speed, ESP, Noclip).
• Script Executor / Hub User — the accepted human persona who runs the Lua script and interacts with the GUI.
• Roblox runtime — the non-persona host environment that provides the player character, camera, and world state.