System Requirements Document for roblox-forgegui

1. Introduction

Product intent. roblox-forgegui is a first-party web workspace that runs a short-form promotional video operation for ForgeGUI — an AI tool for developers and creators that generates thumbnails, 3D models, GUIs, skins, scripting (coding), and other assets. The operation produces promoting videos for the Roblox game Dress to Impress, built by repurposing pre-made ForgeGUI footage with a little bit of editing, and distributes them through YouTube Shorts, TikTok, and Instagram Reels to show off the tool to Roblox and Fortnite developers.

Audience. Roblox and Fortnite developers and creators — largely teens to mid-20s, fluent in streetwear, drop culture, "fit check" language, and Dress to Impress runway aesthetics. The product must read as a creator's own feed and label, never as an advertisement.

What the product is not. It is not a video-generation tool, not a Roblox game client, and not a social network. It does not create full videos from scratch; the footage is supplied. It does not replace the platform apps where warmup scrolling, engagement, and publication actually happen.

2. System Overview

roblox-forgegui is a single first-party web application with a shared backend. It carries the operator through one continuous, ordered operation:

1. Account readiness — select an already-owned fully Roblox-based account or create a new channel, apply the required bio, and confirm the account looks clean, realistic, and organic rather than spam.
2. Warmup — execute the mandatory three-day sequence (Day 1 normal FYP scrolling with no searching; Day 2 niche search and light engagement plus continued normal scrolling; Day 3 full niche engagement) before any posting is allowed.
3. Repurposing — take the supplied ForgeGUI footage and apply at least one real edit (captions or on-screen text, slight trimming or pacing changes, simple zooms, cuts, or transitions; music recommended) so that no provided footage is ever uploaded unchanged.
4. Publishing — push the edited video to YouTube Shorts, TikTok, and Instagram Reels, then sustain at least 15 minutes of daily engagement after Day 3.

Actors. Two accepted human personas operate the product: the Content Creator / Account Operator, who owns the account, the warmup, and the posting cadence; and the ForgeGUI Footage Provider / Editor, who supplies the footage and performs the repurposing edits. The social platforms (YouTube Shorts, TikTok, Instagram Reels) and the Roblox account surface are external, provider-owned destinations — the product tracks and hands off to them but does not impersonate them.

Narrow exclusions. No aggressive promotion. No uploading provided footage with no changes. No skipping warmup. No blue/indigo accents, no gradients, no rounded corners, no centred hero headline with a pill button.

2a. Product Interpretation and Delivery Boundary

Delivery ownership. The product is a first-party web application with a shared backend that persists the operator's account record, warmup progress, edit checklist state, and publication log. The actual scrolling, searching, engaging, and posting happen on the external platforms; the product's job is to sequence, gate, record, and hand off that work truthfully.

Access ownership. The Landing page is the anonymous public entry. The working destinations — Account Setup, Warmup, Content Editor, and Publishing — are protected and require the operator to establish and verify application-owned identity so that account records, warmup day progress, edit state, and publication history remain bound to the correct operator and can be resumed across sessions. First-use identity establishment is self-service; returning operators verify to resume their own durable state. No differentiated permissions, roles, or visibility tiers are established by this identity — both accepted personas share the same product state.

Current vs. future. Everything in this document is current. No future-horizon features are accepted.

2b. Source Content Inventory

The authoritative reference directive is the supplied Provided ForgeGUI footage [Assets] (content_source, feature_reference, authoritative). Its verified content is:

• Asset collection: pre-made ForgeGUI videos/footage, supplied to be repurposed and uploaded.
• Asset constraint: footage must not be uploaded unchanged; every clip must receive at least one edit.
• Asset subject matter (ForgeGUI capability set shown in footage): thumbnails, 3D models, GUIs, skins, scripting (coding), and other assets.
• Asset context: Roblox and Fortnite developer/creator audience; Dress to Impress "fit" frames.
• External link: https://forgegui.com (referenced in the required account bio and the ticker).

No other factual entities, dates, contacts, or media references are supplied by the directive.

2c. Page Content and Component Coverage

Landing

• Information/state: anonymous public entry. Explains the ForgeGUI short-form video workflow for Roblox and Fortnite developers, including the Dress to Impress promotion. States the four numbered spec-sheet sections: 01 — ACCOUNT, 02 — WARMUP, 03 — REPURPOSE, 04 — POST.
• Primary action: START THE WARMUP — the primary CTA, a flat #FF4D00 rectangle pinned under the hazard-stripe band, leading into the protected workflow.
• Supporting actions: read the workflow overview; follow the forgegui.com link; view the looping ForgeGUI footage in the hero phone frame.
• Domain entities: ForgeGUI capability set (thumbnails, 3D models, GUIs, skins, scripting, other assets); the Dress to Impress promotion; the three distribution platforms.
• Component responsibilities:
  • Hero: asymmetric 7:5 split at 1280px; oversized all-caps Archivo Expanded headline wrapped in literal quotation marks, clamp(44px, 9vw, 120px), stacked over four lines and broken across the column rule; 45° hazard-stripe band running full width beneath it; primary CTA pinned directly under the band.
  • Phone frame: 9:16 frame bled off the right viewport edge, looping ForgeGUI footage with a hard cut every 2.5s and a caption bar snapping in from the bottom on each cut; a second smaller phone frame overlapping at 6° rotation with a hang-tag label reading ASSET PACK 01.
  • Ticker: thin strip crossing the very bottom of the viewport at 15px uppercase — FORGEGUI — THUMBNAILS · 3D MODELS · GUIS · SKINS · SCRIPTING — FORGEGUI.COM — scrolling continuously, pausing on hover.
  • Numbered spec-sheet sections with the 12-column grid rules left visible.
• States:

• Loading: hero phone frame shows a still first frame with the caption bar visible until footage is ready.
• Empty: not applicable — the Landing is static content plus looping footage.
• Success: operator reads the workflow and enters the protected workflow via the CTA.
• Error: if footage fails to load, the phone frame holds the still frame and caption bar; the CTA and ticker remain fully functional.
• Recovery: retry footage load on next visit; the CTA path is never blocked by media failure.

Account Setup

• Information/state: the operator's account record — whether an already-owned fully Roblox-based account is being used or a new channel is being created; the required bio text; the clean/realistic/organic (not spam) confirmation.
• Primary action: select an already-owned fully Roblox-based account, or create a new channel.
• Supporting actions: apply the required bio The Best AI Tool for Roblox Devs > forgegui.com; confirm the account looks clean, realistic, and organic; save the account record.
• Domain entities: Roblox-based account; required bio string; account presentation status.
• Component responsibilities:
  • Account source selector: choose "use an account I already own" or "create a new channel".
  • Bio field: pre-filled with the exact required bio string, editable only to match it exactly.
  • Presentation checklist: clean / realistic / organic / not spam, each a hard checkbox square.
  • Hang-tag label strip on the account card, rotated 90°, uppercase, 13px, #8A8A8A.
• States:
  • Loading: account record fetch shows the tag card skeleton with hairline outline.
  • Empty: no account record yet — the selector is presented with both options unselected and the bio field pre-filled.
  • Success: account record saved with source, bio, and presentation confirmation; the Warmup destination unlocks.
  • Error: if the account record cannot be saved, the form retains entered values and shows a plain factual message; the operator can retry.
  • Recovery: the operator can return at any time to change the account source or re-confirm the bio before warmup begins.

Warmup

• Information/state: the mandatory three-day sequence and its progress — Day 1 (scroll FYP normally, do not search anything, act like a real user), Day 2 (search the niche: Roblox dev, Roblox AI softwares, etc.; engage with a few related videos; continue normal scrolling), Day 3 (fully engage with the niche). Posting is locked until after Day 3.
• Primary action: mark each day's warmup actions complete.
• Supporting actions: read the day's instructions; record the daily engagement; view the progress rule.
• Domain entities: warmup day (1, 2, 3); day instructions; completion state; posting lock.
• Component responsibilities:
  • Horizontal three-panel sequence with hard dividers, one panel per day.
  • Progress rule that fills as the operator advances.
  • Day 1 panel: explicit "do not search anything" constraint shown as a hard rule.
  • Day 2 panel: niche search terms (Roblox dev, Roblox AI softwares, etc.) and light engagement.
  • Day 3 panel: full niche engagement.
  • Posting lock indicator: states that posting begins only after Day 3, and that skipping warmup means weak reach.
• States:
  • Loading: three panels render with the progress rule at its current fill.
  • Empty: no days completed — Day 1 panel is active, Days 2 and 3 are locked.
  • Success: all three days marked complete; the Content Editor and Publishing destinations unlock.
  • Error: if a day's completion cannot be saved, the panel retains its prior state and shows a plain factual message; the operator can retry.
  • Recovery: the operator can re-open a completed day to review its instructions; the posting lock is never bypassed.

Content Editor

• Information/state: the supplied ForgeGUI footage/assets and the repurposing checklist — captions or text on screen, slight trimming or pacing changes, simple zooms, cuts, or transitions, and music (recommended). The editor must show ForgeGUI clearly, keep content minimal and easy to understand, and avoid aggressive promotion.
• Primary action: apply edits to the supplied footage and mark the edit checklist complete.
• Supporting actions: add captions or on-screen text; trim or adjust pacing; add simple zooms, cuts, or transitions; attach recommended music; preview the edited result; confirm ForgeGUI is shown clearly.
• Domain entities: supplied ForgeGUI footage/asset; edit checklist item (captions / trim / zoom / cut / music); edited video; ForgeGUI visibility confirmation.
• Component responsibilities:
  • Footage source panel: lists the supplied ForgeGUI assets available for repurposing.
  • Ruled repurposing checklist table with hard checkbox squares: captions / trim / zoom / cut / music.
  • Preview frame: 9:16 hard-edged phone frame with hairline outline and caption bar.
  • Guard: the "upload unchanged" prohibition is enforced — the editor will not mark a video ready if no edit has been applied.
  • Hang-tag label strip on each asset card, rotated 90°, uppercase, 13px, #8A8A8A.
• States:
  • Loading: footage list and checklist render with the tag-card skeleton.
  • Empty: no footage selected — the source panel shows the supplied assets awaiting selection.

• Success: at least one edit applied, ForgeGUI shown clearly, checklist marked complete; the video becomes publishable.
• Error: if an edit fails to apply or the footage cannot be loaded, the prior edit state is retained and a plain factual message is shown; the operator can retry.
• Recovery: the operator can revert an edit and reapply; the unchanged-upload guard remains in force.

Publishing

• Information/state: the edited video ready for distribution, the target platforms (YouTube Shorts, TikTok, Instagram Reels), the publication log, and the post-Day-3 daily engagement requirement of at least 15 minutes.
• Primary action: publish the edited video to the selected platforms.
• Supporting actions: select target platforms; confirm the video carries at least one edit; record the publication; log the daily engagement of at least 15 minutes.
• Domain entities: edited video; target platform (YouTube Shorts, TikTok, Instagram Reels); publication record; daily engagement record.
• Component responsibilities:
  • Platform selector: YouTube Shorts, TikTok, Instagram Reels.
  • Pre-publish guard: blocks publication if the video has no applied edit.
  • Publication log: ruled table of published videos with platform, date, and status.
  • Daily engagement tracker: records at least 15 minutes of engagement per day after Day 3.
  • Hang-tag label strip on each publication card, rotated 90°, uppercase, 13px, #8A8A8A.
• States:
  • Loading: publication log and platform selector render with the tag-card skeleton.
  • Empty: no publications yet — the log shows an empty ruled table and the platform selector is presented.
  • Success: the edited video is published to the selected platforms and the publication is recorded; the daily engagement tracker accepts the day's entry.
  • Error: if a platform handoff fails, the publication is not recorded as complete and a plain factual message is shown; the operator can retry.
  • Recovery: the operator can re-attempt publication to a failed platform; the pre-publish guard remains in force.

3. Functional Requirements

FR-1 — Produce promoting short-form videos for Dress to Impress. As a Content Creator / Account Operator, I should produce promoting short-form videos for the Roblox game Dress to Impress using the provided ForgeGUI footage, so that ForgeGUI is shown off to Roblox and Fortnite developers.

• Provenance: explicit. Access: protected (Publishing). Trigger: edited ForgeGUI footage ready. Observable result: a promoting short-form video for Dress to Impress exists and is published. Failure/recovery: if production cannot complete, the prior state is retained and the operator can retry. Continuation: the video enters the publication log.

FR-2 — Post videos using provided ForgeGUI footage with a little bit of editing. As a ForgeGUI Footage Provider / Editor, I should post videos using the provided ForgeGUI footage with a little bit of editing, so that the footage feels native to the platform.

• Provenance: explicit. Access: protected (Content Editor, Publishing). Trigger: supplied footage available. Observable result: an edited video is published. Failure/recovery: if editing or posting fails, the prior state is retained and the operator can retry. Continuation: the publication is logged.

FR-3 — Content must feel natural, clean, and organic. As a Content Creator / Account Operator, I should keep content natural, clean, and organic, so that it reads as a creator's own feed rather than an ad.

• Provenance: explicit. Access: protected (Account Setup, Content Editor). Trigger: account setup and editing. Observable result: the account and content pass the clean/realistic/organic confirmation. Failure/recovery: the operator can revise the account or edit before proceeding. Continuation: the content proceeds to publication.

FR-4 — ForgeGUI capability set. As a ForgeGUI Footage Provider / Editor, I should show ForgeGUI as an AI tool for developers and creators that creates thumbnails, 3D models, GUIs, skins, scripting (coding), and other assets, so that the tool's scope is clear.

• Provenance: explicit. Access: protected (Content Editor). Trigger: footage selection. Observable result: the footage shows the ForgeGUI capability set clearly. Failure/recovery: the operator can select different footage. Continuation: the edited video proceeds to publication.

FR-5 — Distribution goal. As a Content Creator / Account Operator, I should show off the tool to Roblox or Fortnite developers through YouTube Shorts, TikTok, and Instagram Reels, so that the target audience sees ForgeGUI.

• Provenance: explicit. Access: protected (Publishing). Trigger: edited video ready. Observable result: the video is published to the selected platforms. Failure/recovery: a failed platform handoff is not recorded as complete and can be retried. Continuation: the publication is logged.

FR-6 — Fully Roblox-based account. As a Content Creator / Account Operator, I should use a fully Roblox-based account, so that the operation runs on the required account type.

• Provenance: explicit. Access: protected (Account Setup). Trigger: account setup. Observable result: the account record is marked as fully Roblox-based. Failure/recovery: the operator can change the account source. Continuation: warmup unlocks.

FR-7 — Use an already-owned account. As a Content Creator / Account Operator, I should be able to use an account I already own, so that I do not have to create a new one unnecessarily.

• Provenance: explicit. Access: protected (Account Setup). Trigger: account setup. Observable result: the already-owned account is selected and saved. Failure/recovery: the operator can switch to creating a new channel. Continuation: warmup unlocks.

FR-8 — Create a new channel if none is owned. As a Content Creator / Account Operator, I should create a new channel if I do not already own a Roblox account, so that the operation has a valid account.

• Provenance: explicit. Access: protected (Account Setup). Trigger: no owned account. Observable result: a new channel is created and saved. Failure/recovery: the operator can retry creation. Continuation: warmup unlocks.

FR-9 — Clean, realistic, organic account. As a Content Creator / Account Operator, I should keep the account clean, realistic, and organic — not spam, so that the account is not flagged as spam.

• Provenance: explicit. Access: protected (Account Setup). Trigger: account setup. Observable result: the presentation checklist is confirmed. Failure/recovery: the operator can revise the account before proceeding. Continuation: warmup unlocks.

FR-10 — Required account bio. As a Content Creator / Account Operator, I should set the required account bio The Best AI Tool for Roblox Devs > forgegui.com, so that the account carries the required bio.

• Provenance: explicit. Access: protected (Account Setup). Trigger: account setup. Observable result: the bio is saved exactly as specified. Failure/recovery: the operator can re-enter the bio. Continuation: warmup unlocks.

FR-11 — Warmup Day 1. As a Content Creator / Account Operator, I should on Day 1 scroll FYP normally, not search anything, and act like a real user, so that the account warms up correctly.

• Provenance: explicit. Access: protected (Warmup). Trigger: Day 1 begins. Observable result: Day 1 is marked complete. Failure/recovery: the day can be re-opened and reviewed. Continuation: Day 2 unlocks.

FR-12 — Warmup Day 2. As a Content Creator / Account Operator, I should on Day 2 search my niche (Roblox dev, Roblox AI softwares, etc.), engage with a few related videos, and continue normal scrolling, so that the account warms up correctly.

• Provenance: explicit. Access: protected (Warmup). Trigger: Day 2 begins. Observable result: Day 2 is marked complete. Failure/recovery: the day can be re-opened and reviewed. Continuation: Day 3 unlocks.

FR-13 — Warmup Day 3. As a Content Creator / Account Operator, I should on Day 3 fully engage with my niche, so that the account warms up correctly.

• Provenance: explicit. Access: protected (Warmup). Trigger: Day 3 begins. Observable result: Day 3 is marked complete. Failure/recovery: the day can be re-opened and reviewed. Continuation: posting unlocks.

FR-14 — Post after Day 3 and engage daily. As a Content Creator / Account Operator, I should start posting after Day 3 and engage at least 15 minutes daily, so that reach is sustained.

• Provenance: explicit. Access: protected (Publishing). Trigger: Day 3 complete. Observable result: posting is enabled and the daily engagement of at least 15 minutes is recorded. Failure/recovery: a missed day is visible in the tracker and can be resumed. Continuation: the daily cadence continues.

FR-15 — Skipping warmup means weak reach. As a Content Creator / Account Operator, I should be shown that skipping warmup means weak reach, so that I understand the consequence of skipping.

• Provenance: explicit. Access: protected (Warmup). Trigger: warmup view. Observable result: the consequence is stated plainly. Failure/recovery: not applicable — this is a stated consequence. Continuation: the operator proceeds through warmup.

FR-16 — Repurposing supplied footage. As a ForgeGUI Footage Provider / Editor, I should repurpose the pre-made ForgeGUI videos/footage I am given, so that I do not have to create full videos from scratch.

• Provenance: explicit. Access: protected (Content Editor). Trigger: footage supplied. Observable result: the footage is selected for repurposing. Failure/recovery: the operator can select different footage. Continuation: edits are applied.

FR-17 — Repurposing edit options. As a ForgeGUI Footage Provider / Editor, I should be able to add captions or text on screen, make slight trimming or pacing changes, add simple zooms, cuts, or transitions, and add music (recommended), so that the footage feels native to the platform.

• Provenance: explicit. Access: protected (Content Editor). Trigger: footage selected. Observable result: at least one edit is applied and the checklist is marked complete. Failure/recovery: an edit can be reverted and reapplied. Continuation: the video becomes publishable.

FR-18 — Do not upload unchanged footage. As a ForgeGUI Footage Provider / Editor, I should not upload the provided footage with no changes, so that every published video carries at least one edit.

• Provenance: explicit. Access: protected (Content Editor, Publishing). Trigger: pre-publish check. Observable result: publication is blocked if no edit has been applied. Failure/recovery: the operator applies an edit and retries. Continuation: the video becomes publishable.

FR-19 — Content format. As a ForgeGUI Footage Provider / Editor, I should use the provided ForgeGUI footage [Assets] in a simple UGC style, keep content minimal and easy to understand, avoid aggressive promotion, and show ForgeGUI clearly, so that the content reads as native UGC.

• Provenance: explicit. Access: protected (Content Editor). Trigger: editing. Observable result: the edited video meets the format constraints. Failure/recovery: the operator can revise the edit. Continuation: the video proceeds to publication.

FR-20 — Account readiness before warmup and publication. As a Content Creator / Account Operator, I should have a fully Roblox-based account selected or created before warmup and publication, so that the operation has a valid account.

• Provenance: required_inference. Access: protected (Account Setup). Trigger: workflow start. Observable result: the account record exists. Failure/recovery: the operator can complete account setup. Continuation: warmup unlocks.

FR-21 — Bio set before posting. As a Content Creator / Account Operator, I should have the required account bio set before the account is used for posting, so that the account carries the required bio at publication time.

• Provenance: required_inference. Access: protected (Account Setup). Trigger: account setup. Observable result: the bio is saved before posting is enabled. Failure/recovery: the operator can re-enter the bio. Continuation: posting unlocks.

FR-22 — Three-day warmup before posting. As a Content Creator / Account Operator, I should complete the three-day warmup before posting begins, so that reach is not weakened.

• Provenance: required_inference. Access: protected (Warmup). Trigger: workflow progression. Observable result: posting remains locked until all three days are complete. Failure/recovery: the operator completes the remaining days. Continuation: posting unlocks.

FR-23 — Footage available before editing and publication. As a ForgeGUI Footage Provider / Editor, I should have the provided ForgeGUI footage/assets available before editing and publication, so that the repurposing step can run.

• Provenance: required_inference. Access: protected (Content Editor). Trigger: editing start. Observable result: the footage list is populated. Failure/recovery: the operator can retry loading the footage. Continuation: editing proceeds.

FR-24 — Every video receives edits before upload. As a ForgeGUI Footage Provider / Editor, I should apply edits to every video before upload, so that no footage is uploaded unchanged.

• Provenance: required_inference. Access: protected (Content Editor, Publishing). Trigger: pre-publish check. Observable result: publication is blocked until at least one edit is applied. Failure/recovery: the operator applies an edit and retries. Continuation: the video becomes publishable.

FR-25 — Platform publishing access available. As a Content Creator / Account Operator, I should have YouTube Shorts, TikTok, and Instagram Reels accounts or publishing access available for distribution, so that the edited video can be distributed.

• Provenance: required_inference. Access: protected (Publishing). Trigger: publication. Observable result: the selected platforms accept the handoff. Failure/recovery: a failed platform handoff is not recorded as complete and can be retried. Continuation: the publication is logged.

4. User Personas

Content Creator / Account Operator

Product context. This persona runs the social operation. They own the Roblox-based account, the required bio, the three-day warmup, and the post-Day-3 posting cadence. They are steeped in Roblox creator culture — streetwear, drop culture, "fit check" language, Dress to Impress runway aesthetics — and they know that a spam-looking account kills reach.

Primary goal. Run a clean, realistic, organic Roblox-based account that publishes edited ForgeGUI footage for Dress to Impress and sustains reach through daily engagement.

Distinct accepted responsibilities. Selecting or creating the fully Roblox-based account; applying the required bio The Best AI Tool for Roblox Devs > forgegui.com; confirming the account looks clean, realistic, and organic rather than spam; executing Day 1 (normal FYP scrolling, no searching, acting like a real user), Day 2 (niche search for Roblox dev, Roblox AI softwares, etc., light engagement, continued normal scrolling), and Day 3 (full niche engagement); starting to post only after Day 3; engaging at least 15 minutes daily; publishing to YouTube Shorts, TikTok, and Instagram Reels.

Relevant inputs or decisions. Whether to use an already-owned account or create a new channel; whether the account presentation passes the clean/realistic/organic bar; when each warmup day is genuinely complete; which platforms to publish to; whether the daily 15-minute engagement has been met.

Interactions with other accepted participants. Hands the supplied ForgeGUI footage to the ForgeGUI Footage Provider / Editor for repurposing; receives the edited video back for publication; hands off to the external platforms (YouTube Shorts, TikTok, Instagram Reels) and the Roblox account surface.

Observable success. A fully Roblox-based account with the exact required bio, a completed three-day warmup, published edited videos on the selected platforms, and a sustained daily engagement record of at least 15 minutes.

ForgeGUI Footage Provider / Editor

Product context. This persona supplies the pre-made ForgeGUI footage/assets and performs the repurposing edits. They are not expected to create full videos from scratch — their job is to make the provided footage feel native to the platform through simple edits. They understand that the footage must show ForgeGUI clearly and that aggressive promotion breaks the organic feel.

Primary goal. Repurpose the supplied ForgeGUI footage into platform-native edits that show the tool clearly in a minimal, easy-to-understand UGC style, with no footage uploaded unchanged.

Distinct accepted responsibilities. Supplying the pre-made ForgeGUI footage/assets; adding captions or text on screen; making slight trimming or pacing changes; adding simple zooms, cuts, or transitions; adding music (recommended); ensuring ForgeGUI is shown clearly; keeping content minimal and easy to understand; avoiding aggressive promotion; ensuring no provided footage is uploaded unchanged.

Relevant inputs or decisions. Which supplied footage to repurpose; which edits to apply (captions / trim / zoom / cut / music); whether the edit makes the footage feel native; whether ForgeGUI is shown clearly enough; whether the content stays minimal and avoids aggressive promotion.

Interactions with other accepted participants. Receives the footage supply from the Content Creator / Account Operator; hands the edited video back to the Content Creator / Account Operator for publication.

Observable success. An edited video that carries at least one real edit, shows ForgeGUI clearly, reads as simple UGC, and is accepted for publication without triggering the unchanged-upload guard.

5. Core User Flows

Flow A — Content Creator / Account Operator: Set up the account

1. The operator opens the Landing page anonymously and reads the four numbered spec-sheet sections (01 — ACCOUNT, 02 — WARMUP, 03 — REPURPOSE, 04 — POST).
2. The operator selects START THE WARMUP. Because the working destinations are protected, the operator establishes application-owned identity on first use (self-service) or verifies to resume existing state.
3. The operator arrives at Account Setup. They choose either "use an account I already own" or "create a new channel".
4. If creating a new channel, the operator creates it and returns to record it. If using an owned account, the operator selects it.
5. The operator applies the required bio The Best AI Tool for Roblox Devs > forgegui.com exactly.
6. The operator confirms the presentation checklist: clean, realistic, organic, not spam.
7. Observable result: the account record is saved with source, bio, and presentation confirmation. Next step: the Warmup destination unlocks.
8. Failure/recovery: if the account record cannot be saved, the form retains entered values and shows a plain factual message; the operator retries. The operator can return at any time to change the account source or re-confirm the bio before warmup begins.

Flow B — Content Creator / Account Operator: Complete the three-day warmup

1. The operator opens Warmup. The three-panel sequence shows Day 1 active, Days 2 and 3 locked, and the posting lock indicator stating that posting begins only after Day 3 and that skipping warmup means weak reach.
2. Day 1: the operator scrolls FYP normally, does not search anything, and acts like a real user. The operator marks Day 1 complete.
3. Day 2: the operator searches the niche (Roblox dev, Roblox AI softwares, etc.), engages with a few related videos, and continues normal scrolling. The operator marks Day 2 complete.
4. Day 3: the operator fully engages with the niche. The operator marks Day 3 complete.
5. Observable result: all three days are marked complete and the progress rule is full. Next step: the Content Editor and Publishing destinations unlock.
6. Failure/recovery: if a day's completion cannot be saved, the panel retains its prior state and shows a plain factual message; the operator retries. The operator can re-open a completed day to review its instructions; the posting lock is never bypassed.

Flow C — ForgeGUI Footage Provider / Editor: Repurpose the supplied footage

1. The editor opens Content Editor. The footage source panel lists the supplied ForgeGUI assets.
2. The editor selects a supplied asset. The 9:16 preview frame shows it with a hairline outline and caption bar.
3. The editor applies at least one edit from the ruled repurposing checklist: captions or text on screen; slight trimming or pacing changes; simple zooms, cuts, or transitions; music (recommended).
4. The editor confirms ForgeGUI is shown clearly, the content stays minimal and easy to understand, and the edit avoids aggressive promotion.
5. The editor marks the checklist complete.
6. Observable result: the video carries at least one applied edit and the checklist is complete; the video becomes publishable. Next step: the video moves to Publishing.
7. Failure/recovery: if an edit fails to apply or the footage cannot be loaded, the prior edit state is retained and a plain factual message is shown; the editor retries. The editor can revert an edit and reapply; the unchanged-upload guard remains in force.

Flow D — Content Creator / Account Operator: Publish and sustain engagement

1. The operator opens Publishing. The edited video is ready, and the platform selector shows YouTube Shorts, TikTok, and Instagram Reels.
2. The operator selects the target platforms.
3. The pre-publish guard checks that the video carries at least one applied edit. If it does not, publication is blocked and the operator returns to the Content Editor.
4. The operator publishes the edited video to the selected platforms.
5. Observable result: the edited video is published and the publication is recorded in the ruled publication log with platform, date, and status. Next step: the operator records the day's engagement.
6. The operator logs at least 15 minutes of daily engagement in the daily engagement tracker.
7. Failure/recovery: if a platform handoff fails, the publication is not recorded as complete and a plain factual message is shown; the operator re-attempts publication to the failed platform. The pre-publish guard remains in force.

Flow E — Content Creator / Account Operator: Hand off footage to the editor

1. The operator receives the pre-made ForgeGUI footage/assets.
2. The operator makes the footage available to the ForgeGUI Footage Provider / Editor for repurposing.
3. Observable result: the footage appears in the Content Editor's footage source panel. Next step: the editor runs Flow C.
4. Failure/recovery: if the footage cannot be loaded, the editor retries; the operator can re-supply the asset.

6. Visuals Colors and Theme

Muse and headline. Virgil Abloh — remixed familiarity: a Roblox-native drop page wearing its own label. This is a drop page / label, not a SaaS landing page. The register is playful, insider, ironic-but-sincere: it must feel like a creator's own feed, not an ad.

Mode. Dark mode only.

Colour tokens by role.

No blue, no indigo, no gradient fills of any kind.

Typography.

• Headings: Archivo Expanded / Archivo — all-caps, wide letterspacing (0.06em–0.14em), heavy Archivo Expanded for display, Archivo Medium for subheads. Headlines frequently wrapped in literal quotation marks, set flush-left, ragged-right.
• Body: Space Grotesk.
• Numeric labels and step counts: Space Grotesk tabular figures.
• No italics, no script, no serif.
• Scale: 1.25 modular — 44/34/26/20/16 mobile to 120/72/40/24/17 desktop. Display clamp(44px, 9vw, 120px); section head clamp(26px, 4.4vw, 40px); body 16–17px; label 13px uppercase 0.12em tracking; ticker 15px uppercase.

Shape language. Hard 0px corners everywhere — no radius, no softness, no glass. Elements framed like shipping labels and hang tags: 1px hairline outlines, chunky 2px black rules, exposed grid lines, and 45° hazard-stripe bands (#FF4D00 / #0B0B0B, 12px pitch) used as section dividers and button underlines. Buttons are flat rectangles with a hard 3px offset shadow in #FF4D00, no blur. Quotation marks drawn as oversized graphic glyphs (120–200px) sitting behind or beside headings as composition, not decoration.

Spacing rhythm. A visible 12-column industrial grid with the column rules left showing at 1280px. Sections numbered like spec sheets: 01 — ACCOUNT, 02 — WARMUP, 03 — REPURPOSE, 04 — POST. Content arranged as tag cards: a left rail carrying a vertical label strip (rotated 90°, uppercase, 13px, #8A8A8A) and the right area carrying the content. The 3-day warmup is a horizontal three-panel sequence with hard dividers and a progress rule that fills as you scroll; the repurposing checklist is a ruled table of edits (captions / trim / zoom / cut / music) with checkbox squares. Everything left-aligned; nothing centred except the ticker.

Imagery style. The product's own UGC footage is the imagery: vertical 9:16 screen recordings of ForgeGUI generating a thumbnail, a 3D model, a GUI, and a skin, plus Dress to Impress "fit" frames. Presented inside hard-edged phone frames with a thin #F2F0EB hairline and a caption bar, cropped tight and bled off the right edge of the hero on desktop. Supporting imagery is industrial and photographic: concrete texture, gaffer tape, hang tags, barcode strips, and halftone-treated stills. No stock people, no gradient blobs, no 3D renders of abstract shapes.

7. Signature Design Concept

"THE DROP LABEL" — the Landing as a garment tag for the ForgeGUI pipeline.

The public entry is composed as a hang tag on a drop, not a hero banner. At 1280px the page is a full-bleed near-black concrete ground (#0B0B0B) split asymmetrically 7:5.

On the left, an oversized all-caps Archivo Expanded headline — literally wrapped in quotation marks — is set at clamp(44px, 9vw, 120px), stacked over four lines and broken across the column rule. The opening and closing quotation marks are rendered as 160px graphic glyphs in #FF4D00 sitting behind the type as composition. A 45° hazard-stripe band (12px pitch, #FF4D00 on #0B0B0B) runs the full width beneath the headline, and the primary CTA — START THE WARMUP — is a flat #FF4D00 rectangle pinned directly under the band with a hard 3px offset shadow, no blur.

On the right, a 9:16 phone frame bled off the viewport's right edge shows looping ForgeGUI footage with a caption bar snapping in from the bottom on each hard cut every 2.5s. A second smaller phone frame overlaps it at a 6° rotation, carrying a hang-tag label reading ASSET PACK 01 — punched hole, rotated 90° uppercase label strip, barcode rule.

A thin ticker strip crosses the very bottom of the viewport at 15px uppercase: FORGEGUI — THUMBNAILS · 3D MODELS · GUIS · SKINS · SCRIPTING — FORGEGUI.COM. It is the site's only promotional voice, and it stays plain and factual.

At 375px the headline drops to 44px and stacks above the phone frame, which becomes a single centred 9:16 frame with the ticker still crossing the bottom edge and the CTA pinned full-width beneath the hazard band. Every headline, label, number, and control stays entirely inside the viewport and its container at 375px, 768px, and 1280px; the gesture lives in the stripes, tags, and frames, never in cropping readable text.

8. Interaction Model & Motion Direction

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

Landing Hero Motion Brief.

• Focal subject. The 9:16 phone frame bled off the right viewport edge, looping ForgeGUI footage — the product's own UGC imagery, not a rendered abstraction.
• Input → transformation → outcome thesis. As the operator's eye moves across the hero, the looping footage hard-cuts every 2.5s and the caption bar snaps in from the bottom on each cut; the ticker scrolls continuously across the bottom edge; hovering a tag card flips its label strip from #F2F0EB to #E8FF3A and shifts the card 3px up-left onto its offset shadow. The outcome is a hero that reads as a live feed — the same remix pipeline the product runs — without adding any behaviour beyond the accepted workflow.
• Motion vocabulary. Snappy and mechanical: 120–180ms cubic-bezier(0.2, 0.9, 0.1, 1) transitions, no bounce. Marquee tickers scroll continuously and pause on hover. Section labels clip in from the left with a 1-frame hard-edge wipe (no fade). Hard cuts, not dissolves.
• Composed first frame. Near-black concrete ground; oversized quotation-marked headline flush-left, broken across the column rule; hazard-stripe band beneath it; START THE WARMUP pinned under the band; phone frame bled off the right edge with the caption bar visible; overlapping rotated phone frame with the ASSET PACK 01 hang tag; ticker crossing the bottom edge.
• Reduced-motion state. With prefers-reduced-motion, all marquees become static wrapped rows, the phone frame shows a single still with the caption bar permanently visible, and all wipes become instant state changes. Every item in the ticker becomes fully readable in the wrapped rows.

9. Non-Functional Requirements

NFR-1 — Organic presentation. The account must look clean, realistic, and organic — not spam. Provenance: explicit. Rationale: a spam-looking account weakens reach and contradicts the required presentation.

NFR-2 — No aggressive promotion. Content must avoid aggressive promotion. Provenance: explicit. Rationale: aggressive promotion breaks the organic, creator-native feel the brief requires.

NFR-3 — Minimal, easy-to-understand content. Content must stay minimal and easy to understand. Provenance: explicit. Rationale: simple UGC style is the accepted format.

NFR-4 — ForgeGUI shown clearly. ForgeGUI must be shown clearly in the content. Provenance: explicit. Rationale: the goal is to show off the tool.

NFR-5 — No unchanged uploads. Provided footage must never be uploaded with no changes. Provenance: explicit. Rationale: the repurposing step is the product's core value.

NFR-6 — Warmup is mandatory. The three-day warmup must be completed before posting; skipping warmup means weak reach. Provenance: explicit. Rationale: the source states the consequence directly.

NFR-7 — Daily engagement. At least 15 minutes of daily engagement after Day 3. Provenance: explicit. Rationale: sustained reach requires ongoing engagement.

NFR-8 — Readable text and controls stay whole. Headlines, wordmarks, labels, numbers, cards' text, and controls stay entirely inside the viewport and their container at 375px, 768px, and 1280px, wrapping or scaling to fit; no other element covers any part of them. Provenance: explicit (creative direction). Rationale: accessibility and legibility.

NFR-9 — Reduced-motion usability. With prefers-reduced-motion, provide a usable static arrangement: marquees become static wrapped rows, the phone frame shows a single still with the caption bar permanently visible, and all wipes become instant state changes. Provenance: explicit (creative direction). Rationale: accessibility.

NFR-10 — No blue/indigo, no gradients, no rounded corners. Provenance: explicit (creative direction). Rationale: the forbidden generic indigo/blue-on-white SaaS template look.

NFR-11 — Durable operator state. Account record, warmup day progress, edit checklist state, and publication log persist across sessions and remain bound to the correct operator. Provenance: required_inference. Rationale: the accepted workflow spans multiple days and must be resumable.

10. Tech Stack

• Frontend: React (web). The product is a browser-based workspace with a public Landing and protected working destinations.
• Backend: Python / FastAPI — a single shared backend process serving the application's routes and modules for account records, warmup progress, edit checklist state, and publication log. No separate containers or ingress routes are needed for these domain features.
• Storage: a relational database for durable operator state (account record, warmup day progress, edit checklist state, publication log, daily engagement records).
• Deployment: Docker / docker-compose for local and single-host deployment. Kubernetes is not required by the current scope.

No source-specified technology choices conflict with these; the source does not name a stack, so these are the practical defaults for the accepted product.

11. Assumptions and Constraints

Assumptions.

• A1. The operator has access to the external platforms (YouTube Shorts, TikTok, Instagram Reels) and the Roblox account surface; the product tracks and hands off to them but does not impersonate them. [Assumption — not specified by user]
• A2. The supplied ForgeGUI footage/assets are made available to the product before editing begins. [Assumption — not specified by user]
• A3. The operator can establish and verify application-owned identity on first use so that multi-day state remains bound to the correct operator. [Assumption — required_inference]
• A4. The product does not generate video; it sequences, gates, records, and hands off the repurposing and publication work. [Assumption — not specified by user]

Constraints.

• C1. Must use a fully Roblox-based account; accounts already owned may be used, otherwise create a new channel. (explicit)
• C2. The account must look clean, realistic, and organic — not spam. (explicit)
• C3. Required account bio: The Best AI Tool for Roblox Devs > forgegui.com. (explicit)
• C4. Warmup Day 1: do not search anything. (explicit)
• C5. Do not start posting until after Day 3 of warmup. (explicit)
• C6. Engage at least 15 minutes daily after Day 3. (explicit)
• C7. Skipping warmup = weak reach. (explicit)
• C8. Do not upload the provided footage with no changes. (explicit)
• C9. Avoid aggressive promotion. (explicit)
• C10. Keep content minimal and easy to understand. (explicit)
• C11. Show ForgeGUI clearly. (explicit)
• C12. No blue or indigo accent, and no gradient fill. (explicit — creative direction)
• C13. No rounded corners, soft shadows, glassmorphism, or frosted panels. (explicit — creative direction)
• C14. No centred hero headline with a subhead and a pill button beneath it. (explicit — creative direction)
• C15. No Inter, Roboto, Poppins, or any neutral system sans for headings or body. (explicit — creative direction)
• C16. No stock photography of people, 3D abstract blobs, or decorative illustration. (explicit — creative direction)
• C17. Readable text and controls stay whole at every viewport; imagery, decoration, and motion may be cropped, bled, rotated, overlapped, or cut as the direction asks, as long as they cover no readable text or control. (explicit — creative direction)

12. Glossary

• ForgeGUI — an AI tool for developers and creators that creates thumbnails, 3D models, GUIs, skins, scripting (coding), and other assets.
• Dress to Impress — the Roblox game for which the promoting videos are produced.
• Fully Roblox-based account — an account that is entirely Roblox-based, as required by the account setup step.
• Warmup — the mandatory three-day sequence (Day 1 normal FYP scrolling with no searching; Day 2 niche search and light engagement plus continued normal scrolling; Day 3 full niche engagement) that must be completed before posting begins.
• FYP — "For You Page," the algorithmic feed where normal scrolling happens during warmup.
• Niche — the target interest area for warmup searching and engagement: Roblox dev, Roblox AI softwares, etc.
• Repurposing — taking the supplied pre-made ForgeGUI footage and applying simple edits (captions or on-screen text, slight trimming or pacing changes, simple zooms, cuts, or transitions, and recommended music) so the footage feels native to the platform.
• UGC style — user-generated-content style: simple, minimal, easy to understand, and not aggressively promotional.
• Unchanged-upload guard — the rule that provided footage must never be uploaded with no changes; publication is blocked until at least one edit is applied.
• Hang-tag label — the visual motif of a small punched-hole tag with a rotated 90° uppercase label strip and a barcode rule, carried by every card, asset, and phone frame.
• Hazard-stripe band — a 45° band of #FF4D00 on #0B0B0B at 12px pitch, used as section dividers, button underlines, and the hero's base rule.
• Ticker — the continuous bottom marquee strip at 15px uppercase, the site's only promotional voice, staying plain and factual.