Ship a landing waitlist

Add a landing waitlist page so visitors can leave an email, then open a draft pull request after you Approve.

Layer 01

What you say to StellarFirm

Add a landing waitlist page so visitors can leave an email, and open a pull request.

Layer 02

What StellarFirm tells the coding session

Implement a simple landing waitlist: a page where a visitor can leave an email. Follow the repository's existing UI and form patterns. Do not add a new stack, a payment step, or a new email vendor.

Keep the Slack text as the task. Add any path or acceptance note the CEO named.

Edit the working tree only. Do not commit, push, merge, or switch away from the current branch.

Run the repository's quality gate from AGENTS.md (for example lint, typecheck, test) and report the commands you ran and their results.

After the CEO Approves, the Coder publishes a new stellarfirm/coder/<slug>-<job> branch with git push -u origin (never force) and opens a draft pull request against the branch the checkout was on.

Never merge. Never force-push. Never push the default branch. Merging stays with the CEO.

Do not use subscription-login tokens. Keep keys, passwords, and personal data out of the prompt.

Back to the Coder library