Skip to content
SlashClone
Starter packFor Building apps, Founder@slashcloneRun by the SlashClone team

Build an app

Build a real app with Claude Code: split the work into parallel sessions that each end in a pull request, keep dev and production the same, pin dependencies, release on green CI, and smoke test every deploy.

What's inside

  1. @slashclone/parallel-sessions

    Build faster with several Claude Code sessions at once. Splits a big plan into independent workstreams, writes a brief for each, runs each in its own git worktree and branch, and merges every pull request on green CI in a safe order. Works in the Claude Code desktop app and in the terminal.

  2. @slashclone/dev-prod-parity-rule

    A CLAUDE.md rule that stops bugs that only show up in production by keeping development and production behaving the same. Your agent prefers explicit env flags over NODE_ENV checks and records every unavoidable difference in your deploy guide, in the same change that adds it. Shows you the edit before saving.

  3. @slashclone/pin-dependencies-safely

    Install and upgrade npm packages safely, so your agent never pulls a typosquat or a freshly compromised release. Before adding a package it confirms the exact name, the latest stable version, and that the version is at least 14 days old, then pins it exactly and commits the lockfile. Also pins CI actions and container images by SHA or digest.

  4. @slashclone/release-on-green

    Deploy to production only when tests pass, automatically or with one button, and always know what is live. A GitHub Actions release that ships main's head or stops and says why, records each release as a GitHub deployment, smoke tests, and rolls back on failure. Writes the workflow for you to review; never deploys or stores secrets itself.

  5. @slashclone/production-smoke-test

    Know a deploy worked before your users find out it did not: a short smoke test that checks your live site after each release. Checks the status endpoint, home page, search, sign-in redirects, and connected services, retrying while the deploy settles, and exits non-zero so the release can roll back. Read-only, no credentials.

Keys to set

Nothing to set. Every kit here works without keys.

Cookies that keep you signed in and remember these choices are always on. Everything else is off until you turn it on.