Build this tool: LinkStack Builder - One-Click Sponsor/Code Block Generator for Video Descriptions Product folder name: LinkStack Builder PRODUCT BRIEF A free web tool where creators save their recurring links/codes/socials once, then generate a formatted, ready-to-paste description block (with UTM-tagged links optional) in one click. Include templates for "gaming sponsor stack," "merch stack," "socials stack." CONTEXT Difficulty: Easy Category: Gaming TREND HOOK Nearly every top video (CaseOh, Joe Bart, TechyCrew) has a near-identical sponsor block (Gamersupps code, Starforge, merch link, socials) manually retyped every time. VIDEO ANGLE Short: "Stop retyping your sponsors every video" demo of pasting a finished block in 5 seconds. Long video: build it in Cursor, show before/after time saved across 10 videos. WHY THIS TOOL Classic small, ships-in-a-day workflow tool — exactly Casey's freebie style. STACK (standalone desktop app) - Python 3 + tkinter GUI — standalone desktop tool (not a website). - Even if the brief says "web app" / "site", ship a Python desktop GUI for v1. - Include: main .py, requirements.txt, run_*.bat, build_exe.bat (PyInstaller), and an exports/ folder for saved output. - Smoke-test core logic offline without requiring live API keys when possible. GUI RULES - Clean, readable dark or light UI — pick one consistent palette (no brand lock-in required). - Clear app title / hero name derived from the product folder name. - Short muted "How to use: …" line under the title (one sentence: what to enter → what button → what you get). - Prefer real inputs (paste URL / fields / text) over fake demos. - No sample dropdowns or canned demo datasets unless explicitly requested. - Dropdowns: NEVER ttk.Combobox (unreadable on Windows dark UI). Use DarkSelect (preferred, no grab_set) OR dark-styled tk.OptionMenu (BG_ELEVATED / TEXT / active #243056 / BORDER+TEAL highlight; style the popup menu the same way). Never use grab_set (breaks close behavior on Windows). - Handle window close with WM_DELETE_WINDOW. - One job per tool; working copy/export; avoid overbuilt dashboards. APIs & KEYS - Never hardcode API keys or secrets into source or the packaged EXE. - Store keys in a local user settings JSON under %LOCALAPPDATA%\\ (or a single shared settings file if multiple tools share a key). - Label each key field clearly in the UI (e.g. YouTube API key vs Gemini API key). - Local/offline logic must work first; APIs are optional enhancements where possible. - Call network APIs in a background thread; update the UI with after(...). On failure, keep local results and show a clear error. Gemini API (optional copy / polish) - Add Gemini (AI-first for paste-ready copy) when the tool WRITES language creators will paste online (titles, captions, descriptions, pinned comments, end-cards, disclaimers, SEO templates). - UI: API key field + Model text field + checkbox like "Use Gemini" / "Polish with Gemini". - Default model: gemini-2.5-flash-lite. Also accept typed model ids (e.g. gemini-3.1-flash-lite). - Do not hardcode the model URL/path; pass the Model field value into the generate call. - Pattern: Gemini writes paste-ready copy first when enabled. Local templates/scores are the fallback if Gemini is off or fails. - On Gemini failure: keep local output, show error, do not wipe results. - Flash Lite is enough for short creative jobs — do not default to Pro. IMPLEMENTATION NOTES - Match the product brief closely; keep v1 focused on one job. - Support Copy and/or Export of results where useful (TXT/CSV/JSON as fits the tool). - Validate inputs; show empty/error states clearly. - If scoring/grading: show score + short explanation of what failed/passed. - If generating copy: show multiple variants when the brief asks for them. DEMO INPUT → OUTPUT (from live scan) - Real field labels + sample values from MOTION_DEMO: - Channel Name: Casey Builds It - Template: Gaming sponsor stack - Primary button name: Generate block - Example result lines — MUST be DISTINCT (unique episode hooks / twists): - 1 | -- SPONSORS & CODES -- - 2 | Thanks for watching - support the channel with these partners: - 3 | (Add sponsors in your saved stack first.) - Final Beat: Writing with Gemini... (The tool reports this status as the final payoff. Describe this moment LAST. Do not end the demo on Copy / Export instead, and do not cut away before it lands.) SAY (demo beat — AI voice friendly): Alright, so right here I am going to run through it live with something someone would actually use. I am typing Casey Builds It into Channel Name. I am typing Gaming sponsor stack into Template. Hit Generate block. Give it a second. And right here, that is your output. Look at 1: -- SPONSORS & CODES -- OUTPUT - Runnable standalone Python app - requirements.txt + run bat + optional EXE build script - In-app how-to line - Example of typical input → output (in README or comments, not fake UI samples)