Build HookLab with Codex.

You are Sol, the lead orchestrator for this HookLab project.

Your job is to plan the work, delegate bounded tasks, integrate the results, and verify the finished app. Do not do all of the implementation yourself.

First inspect the project folder. If it is empty, build the first version with plain HTML, CSS, and JavaScript so it can run locally without installing dependencies or entering an API key.

Use this delegation sequence:

1. Delegate a read-only UX planning task to a gpt-5.6-luna agent. Ask it to recommend a simple beginner-friendly layout, user flow, labels, and result structure. It must return recommendations without editing files.

2. Review those recommendations yourself and define the final scope.

3. Delegate implementation to one gpt-5.6-terra agent. It may create and edit the project files, but it must stay within the approved scope below.

4. After implementation is complete, delegate a read-only QA review to a new gpt-5.6-luna agent. Ask it to test the main flow, responsive layout, keyboard usability, copy buttons, and browser console.

5. You must review the implementation and QA report, fix confirmed issues, run the app yourself, and verify the final result.

Never let two agents edit the same files at the same time. Keep all agents inside this project folder and preserve any existing user work.

Build a polished single-page web app called HookLab.

HookLab helps YouTube creators turn basic video ideas into stronger titles and opening hooks.

Include inputs for:
- Video topic
- Target audience
- Desired tone
- Main viewer benefit

Generate:
- 10 YouTube titles
- 3 opening hooks
- 5 short thumbnail phrases

Separate titles into searchable, curiosity-driven, and story-driven categories. Include copy buttons and a regenerate button.

Use a modern dark interface with bright accent colors. Make it responsive, easy to read, and visually polished. Include useful sample or deterministic results so the complete interface works without an external API.

Do not add authentication, a database, payments, analytics, deployment, or unrelated features.

Before finishing, report:
- Which agents were delegated and which models they used
- What each agent contributed
- Files changed
- Commands and tests run
- Confirmed fixes
- Known limitations

Sol, coordinate a focused design upgrade for HookLab. Remain the lead orchestrator and use smaller agents for review, implementation, and QA.

1. Delegate a read-only interface critique to a gpt-5.6-luna agent. Have it inspect the current app and recommend improvements to visual hierarchy, typography, spacing, button labels, color contrast, mobile usability, and the presentation of generated results. It must not edit.

2. Review the critique and select only improvements that support the current HookLab scope.

3. Delegate the approved visual changes to one gpt-5.6-terra implementation agent. It may edit only the interface and presentation layer. It must preserve the existing form, generation behavior, and copy buttons.

4. After implementation, delegate a read-only QA pass to a new gpt-5.6-luna agent. Have it check desktop and mobile layouts, keyboard focus, contrast, copy buttons, regenerate behavior, and browser console errors.

5. Personally inspect and run the integrated result. Fix confirmed issues and summarize the before-and-after improvements.

The finished interface should feel like a premium creative tool. Make the results the main visual focus and use subtle animations when new results appear. Keep everything fast, clean, responsive, and beginner-friendly.

Never allow two agents to edit the same files concurrently. Do not expand the product scope or change the technology stack.

Sol, add one focused feature to HookLab: Remix. You remain responsible for the plan, integration, and final verification.

First inspect the current implementation and define the smallest safe change. Then delegate implementation to one gpt-5.6-terra agent with this exact scope:

- Add a Remix button beside every generated title.
- When clicked, produce three variations of that title:
  - A safer version
  - A bolder version
  - A search-friendly version
- Allow every variation to be copied individually.
- Match the existing visual design.
- Handle repeated Remix clicks cleanly.
- Preserve the form, title categories, hooks, thumbnail phrases, sample data, copy behavior, and regenerate button.
- Do not introduce a backend or external API.

After implementation, delegate a read-only QA pass to a gpt-5.6-luna agent. Have it verify every Remix button, copied text, repeated clicks, keyboard navigation, mobile layout, and browser console.

Review the changes and QA report yourself. Fix confirmed problems, run the main user flow, and report the delegated work, files changed, tests run, fixes made, and remaining limitations.

Sol, perform a final release check for the HookLab demo.

Delegate a read-only audit to a gpt-5.6-luna QA agent. Ask it to verify:

- The app starts using the documented method.
- A user can enter all four inputs.
- Results appear without an API key.
- Titles appear in all three categories.
- Hooks and thumbnail phrases are visible.
- Copy buttons work and copy the correct text.
- Regenerate works.
- Remix works, including repeated clicks.
- The layout is usable on desktop and mobile.
- Keyboard focus and color contrast are reasonable.
- There are no obvious browser console errors.

The QA agent must report evidence and must not edit files.

Review its report yourself. Fix only confirmed issues, rerun the affected checks, and verify the complete user flow. Do not add features or expand the scope. Finish with a concise demo-ready summary containing agents used, files changed, tests passed, and known limitations.

Sol, improve the quality and variety of HookLab's generated writing using a small-agent review workflow.

Delegate a read-only content audit to a gpt-5.6-luna agent. Have it identify repeated structures, vague claims, misleading clickbait, unnecessary capitalization, weak hooks, and thumbnail phrases that merely repeat titles.

After reviewing its report, delegate only the approved content-rule changes to one gpt-5.6-terra implementation agent. Titles should be concise, accurate, and meaningfully different. Hooks should immediately deliver on the title's promise. Thumbnail phrases should contain no more than four words.

Then personally test at least three different topics and verify that the changes improve variety without breaking existing functionality. Report the agents used, changes made, examples tested, and remaining limitations.

I want to go a step further and improve the titles. Can you take these 2026 best practices from Perplexity AI and improve the title generations, please?