What it does

Shows primary routes, Studio handoff, runtime status, theme, and supporting pages.

When to use it

Use it to start over, open Studio, check privacy, change theme, or jump to a public page.

How to use it

1. Open the top navigation.
2. Choose Create or Studio.
3. Use Menu for Method, About, Use cases, Guide, and legal pages.

What to look for

• Create remains primary.
• Studio opens after a jam exists.
• Comparison pages stay lower-priority in the footer.

Common mistakes

• Opening Studio before a jam exists sends you back to Create.

What it does

Combines the AI/engine status pill with the light/dark theme control.

When to use it

Check it before generation, after a failure, or when inspecting a saved Studio result.

How to use it

1. Read the AI/Engine pill.
2. Open details when available.
3. Use the theme switch for light or dark mode.

What to look for

• AI ready state.
• Engine fallback language.
• Developer-action detail when service health degrades.

Common mistakes

• Do not assume a fallback result came from AI; the status explains the source.

What it does

Frames Chord Draft as a free AI chord-progression generator for songwriters.

When to use it

Start here if you are new, evaluating the product, or looking for Method or About.

How to use it

1. Read the promise.
2. Check free-access chips.
3. Choose Start a draft or See the method.

What to look for

• One primary CTA.
• Free-tier transparency.
• Founder credit below the songwriter value prop.

Common mistakes

• Home is the public start, not Studio.

What it does

Packages HowTo, access, and FAQ content for users and search engines.

When to use it

Use it when you want proof, policy, or a plain-English explanation of the first-draft flow.

How to use it

1. Review the three-step method.
2. Read free access.
3. Scan FAQs for account, editing, and Studio questions.

What to look for

• No paywall language.
• No speed or quality overclaims.
• Links to Method and About.

Common mistakes

• The FAQ supports the flow; it does not replace Create.

What it does

Guides setup before Review and generation.

When to use it

Use it when you have a lyric, hook, mood, or scene and want a playable loop.

How to use it

1. Enter the idea.
2. Pick feel and playability.
3. Choose lane, tempo, and style.
4. Continue to Review.

What to look for

• Idea input.
• Feel choices.
• Playability controls.
• Lane and extras.
• Current configuration summary.

Common mistakes

• Leaving the idea too vague gives the engine less emotional direction.

What it does

Summarizes choices and exposes quiet handling details for transparency.

When to use it

Use it immediately before Generate my draft.

How to use it

1. Check the idea text.
2. Review mood, playability, style, and tempo.
3. Open build details.
4. Click Generate my draft.

What to look for

• Ready state.
• Access warning if unavailable.
• Change the vibe link.

Common mistakes

• If Review redirects home, the local draft was missing; start again from Create.

What it does

Streams progress and shows actionable developer reason plus Reference ID on failure.

When to use it

Use it after Review while Chord Draft builds the first loop.

How to use it

1. Watch the phase label.
2. Open build details.
3. Wait for Studio handoff or use Retry now on recoverable failure.

What to look for

• Runtime mode.
• Step log.
• Ready state.
• Actual reason and Developer action when generation fails.

Common mistakes

• Do not refresh repeatedly; wait for ready or an actionable error.

What it does

Loads the current local jam, shows source badges, and organizes the Studio zones.

When to use it

Use it after a draft is ready or when returning to your most recent local jam.

How to use it

1. Open Studio.
2. Read the source badge.
3. Use the zone tabs.
4. Export or revise locally.

What to look for

• Jam title and key.
• AI or theory-engine source.
• Listen, Understand, Change, and Share zones.

Common mistakes

• Studio is noindex and local; it is not a public share page by itself.

What it does

Combines transport controls, sound presets, chord cards, and visual feedback.

When to use it

Use Listen first after generation.

How to use it

1. Press play.
2. Choose a sound.
3. Select a chord.
4. Watch the waveform.

What to look for

• Play controls.
• Chord symbols and notes.
• Sound preset chips.

Common mistakes

• Do not edit before hearing the full loop at least once.

What it does

Shows theory cards, sheet music, chord diagrams, and optional instructor detail.

When to use it

Use it when the loop feels good but you want to know why.

How to use it

1. Open Understand.
2. Read Harmonic Arc.
3. Review tips and diagrams.
4. Toggle theory detail if available.

What to look for

• Plain-language theory.
• Input anchors.
• Practice tips.

Common mistakes

• Do not treat theory notes as a rulebook; use them as songwriting context.

What it does

Provides chord-change and continuation tools around the local jam.

When to use it

Use it when one chord or next section needs a different emotional color.

How to use it

1. Open Change.
2. Choose Chords or Continuation.
3. Preview a proposal.
4. Apply only the version you want.

What to look for

• Chord workspace.
• Continuation tab.
• Access messaging if generation is unavailable.

Common mistakes

• Changing chords is local; export or preserve state if you need the version.

What it does

Offers MIDI/WAV export, another-version creation, and start-new-jam actions.

When to use it

Use it when the loop is worth keeping or you want another pass.

How to use it

1. Open Actions.
2. Export MIDI or WAV.
3. Make another version if needed.
4. Start new jam when done.

What to look for

• Export controls.
• New version action.
• Public sharing removed notice.

Common mistakes

• Exports are working materials, not publication proof.

What it does

Groups Product, Use cases, Compare, Legal / AI, support, and social links.

When to use it

Use it for policy, citation, public pages, and support contact.

How to use it

1. Scroll to the footer.
2. Choose the relevant group.
3. Use Support for operational questions.

What to look for

• Grouped public links.
• Founder credit to About.
• All sitemap pages reachable.

Common mistakes

• Do not use footer links as the main generation flow; Create remains the first-draft path.