Skip to content
SlashClone
DiscoverUse in ClaudeSubmit a link
Sign in

SlashClone

slashclone.dev/@slashclone · building since 5 Nov 2026 · run by the SlashClone team

First share

Kits the SlashClone team uses to build SlashClone: releases, smoke tests, search quality, safe dependencies, and the rules we give Claude.

Kits shared
8
Public kits with at least one published version.
Installs
0
Times someone installed one of these kits.
Clones
0
Kits other people built from these.
Reviews
0
Reviews on these kits; 0 said it worked for them.
Co-authored
0
Kits by others that credit this builder.

Highlights

  • Canvas frame capture

    Check a canvas or WebGL animation frame by frame when the browser cannot take screenshots (a hidden pane, a background tab, a headless run). Captures timed frames from the page itself and saves them as small images you can look at. Writes only to a frames folder you choose.

    0 installs · 0 likes · 0 clones

  • Dev prod parity rule

    A CLAUDE.md rule that keeps development and production behaving the same: prefer explicit environment flags over NODE_ENV checks, and write down every unavoidable difference in the deploy guide in the same change.

    0 installs · 0 likes · 0 clones

  • Pin dependencies safely

    Before adding or upgrading a package: confirm the version exists, is the latest stable release, and is at least 14 days old, then pin it exactly and commit the lockfile. A simple guard against typosquats and freshly compromised releases.

    0 installs · 0 likes · 0 clones

  • Product rename checklist

    Rename a product across code, copy, CLI, plugins, and docs without breaking anything: one name constant, a careful sweep, and a list of strings that must keep the old name (signing labels, key-derivation labels, OAuth client ids, stored rule ids, migrations). Shows the plan and asks before it edits.

    0 installs · 0 likes · 0 clones

  • Production smoke test

    Write a short smoke test script for a live site: the status endpoint, the home page, search, sign-in redirects, and any connected services, each retried while a new deploy settles. Exits non-zero on the first failure so a release can roll back.

    0 installs · 0 likes · 0 clones

  • Release on green

    Set up a release pipeline with no manual gates: when CI passes on main, migrate the database, deploy, run a smoke test, and roll back on its own if the smoke test fails. Writes the GitHub Actions workflow for you to review; never deploys or stores secrets itself.

    0 installs · 0 likes · 0 clones

How these are counted

  • Kits shared: Public kits with at least one published version.
  • Installs: Times someone installed one of these kits.
  • Clones: Kits other people built from these.
  • Reviews: Reviews on these kits; 0 said it worked for them.
  • Co-authored: Kits by others that credit this builder.
  • Every kit passed the SlashClone safety scan before it was published. Numbers are live from slashclone.dev/@slashclone.