from checkout to launch dayin seven commands🧭

01What you need

Works on macOS, Windows and Linux. Run each check in a terminal (PowerShell on Windows).

02Setup, about 5 minutes

1. 1

   Connect GitHub

   After checkout, your order email from Dodo Payments has a link to connect your GitHub account. Any GitHub account works; it doesn't need the same email as your order. The link is also in the Dodo customer portal.

2. 2

   Accept the repo invite

   GitHub then emails an invite to the private repo. Accept it there, or at github.com/launchdaykit/launchdaykit-kit/invitations. Until you do, cloning fails with "Repository not found".

3. 3

   Get the kit (once)

   Clone it to one folder on your computer. On Windows (PowerShell), use $HOME\launchdaykit-kit as the folder.

   git clone https://github.com/launchdaykit/launchdaykit-kit.git ~/launchdaykit-kit

4. 4

   Install it into your product

   From your product's folder (the one with its code), run the installer, then install the kit's packages once per product (2–3 minutes).

   node ~/launchdaykit-kit/install.mjs
   cd launchdaykit && npm install

5. 5

   Let it use your Chrome (once)

   For submissions, open this page in Chrome and turn remote debugging on. Keep Chrome open while submitting. Claude in Chrome works too.

   chrome://inspect/#remote-debugging

6. 6

   Start Claude Code

   Open a new Claude Code session in your product's folder and approve chrome-devtools when asked. Type / and the seven /launch commands appear. Start with the brief.

   /launch-brief https://your-product.com

Rather let Claude do steps 4 and 5? After cloning, open Claude Code in your product's folder and ask it to install LaunchDay Kit with node ~/launchdaykit-kit/install.mjs, then start a new session.

03The commands, in order

Each command reads what the earlier ones wrote. Allow about an hour for the first five; the video takes longer because you pick a track and compare drafts. Submissions run over days, since many sites review or schedule listings.

1. 1./launch-brief→ launch/brief.md

   Asks a few questions and reads your site. Read the brief and fix anything wrong: every other command uses it.

2. 2./launch-copy→ launch/copy.md

   Taglines, descriptions, Product Hunt, Show HN, Reddit, Indie Hackers and every directory's fields, each within that site's limit.

3. 3./launch-x→ launch/x-posts.md

   A dated X plan from a week before launch to a week after, with reply templates.

4. 4./launch-seo→ a report, then your approved fixes

   Checks metadata, canonicals, Open Graph, JSON-LD, robots.txt, sitemap and llms.txt like a crawler would. Changes nothing until you pick the fixes.

5. 5./launch-assets→ launch/assets/

   Open Graph images in three styles, logo sizes, screenshots at every site's size and framed gallery shots, all from your real site.

6. 6./launch-video→ launch/assets/video/

   Studies 1–3 launch videos you like, pitches three intros, shows you 2–3 drafts, then renders landscape, square and portrait.

7. 7./launch-submit→ launch/submit/tracker.html

   Asks four permission questions once, then submits to launch sites in your Chrome, 10 at a time. Run it again to continue.

The submissions follow the directory guides: every site with a free route, its approval time, badge and account rules.

04What stays with you

It works in your own Chrome and never signs up for you. Sites whose rules forbid automated submissions get a paste sheet instead.

05Updates

Pull the kit, then run the installer again in your product. Your launch/ files are never touched. Start a new Claude Code session afterwards.

cd ~/launchdaykit-kit && git pull
cd path/to/your-product && node ~/launchdaykit-kit/install.mjs

06Troubleshooting

Stuck anywhere else? Message @amitkushh on X with the command, what happened and the error text.