Claude Skill MartBrowse skillsQuick linesLearn by videoTerminal guideWhat is a Skill?
← Back to list

replica-backend — Backend builder for app clones

Builds the whole backend layer — auth, DB migrations and access rules, Stripe payments, email, background jobs, official-API integrations — with a security checklist to tick off.

Dev & CodingIntermediate★ 1,072⑂ 132AI score 8/10Last updated: Oct 3, 2026

What it does

  • Reads replica/architecture.md, writes migrations and server code, and keeps the checklist in replica/backend.md current.
  • Auth: verified email sign up, password reset, magic links, OAuth via your own developer apps, http-only secure cookie sessions, sign out everywhere, and account deletion that truly deletes.
  • Database: checked-in migrations run by a script, access rules on every table (Supabase RLS or an authorisation function), a second-user test that must return nothing, a realistic seed script, backups verified on.
  • Payments: Stripe Checkout plus Customer Portal (no hand-rolled card forms), signature-verified webhooks with stored event ids and idempotent handlers for the four key subscription events, subscription state read from your DB, one-click cancellation.
  • Email & jobs: transactional mail through Resend/Postmark on your own domain, scheduled jobs with retries and a dead-letter log, UTC storage with per-user display.
  • Rules and limits: official public APIs only, never the original app's private endpoints or OAuth client. The user creates every account and key; Claude only writes a value-free .env.example and keeps Stripe in test mode until deploy.

Who it's for

  • Indie hackers and solo devs building a SaaS modelled on an existing product
  • Junior developers wiring up auth, authorisation and billing webhooks for the first time
  • Small teams that want a fast MVP but a documented security pass

Examples

  1. Ask "set up auth" → verified sign up, reset flow, cookie sessions, and owner/admin/member roles behind a single permission function.
  2. Ask "connect Stripe" → Checkout + Customer Portal, signature verification, and idempotent handlers for checkout.session.completed, customer.subscription.updated/deleted, invoice.payment_failed.
  3. Ask "add Google Calendar" → official API, minimum OAuth scopes, and a note in backend.md that Google's OAuth verification takes weeks.

· · · Install guide · · ·

Try it now, no install

Paste this into Claude to use the skill without installing anything.

Read the instructions in this file and follow them to help me:
https://raw.githubusercontent.com/Jakeschincariol/replica-skill/HEAD/replica-backend/SKILL.md

What I want: (describe your task here)

If Claude can't open the link, open it yourself and paste the contents instead.

↓ If it works for you, download the ZIP below and install it. Then it runs on its own — no pasting each time.

Install in the Claude app (no terminal)
  1. Download the ZIP with the button below.
  2. In Claude, open Settings → Capabilities and turn on 'Code execution and file creation'. (one time)
  3. Go to Customize → Skills → + → 'Upload a skill' and upload the ZIP.
↓ Download ZIP
Install in Claude Code

Let Claude do it — paste this into Claude Code

Install the skill I found on Claude Skill Mart.
Copy the replica-backend folder from the GitHub repo Jakeschincariol/replica-skill into my ~/.claude/skills/replica-backend/.
When it's done, tell me in one line what this skill can do.

Install with a command instead

git clone https://github.com/Jakeschincariol/replica-skill.git && mkdir -p ~/.claude/skills && cp -r replica-skill/replica-backend ~/.claude/skills/

⚠ This is a third-party skill. Check the source repository before installing.

  1. Open a terminal.
  2. Clone the repo: git clone https://github.com/Jakeschincariol/replica-skill.git
  3. Create the skills folder: mkdir -p ~/.claude/skills
  4. Copy the skill: cp -r replica-skill/replica-backend ~/.claude/skills/
  5. (Recommended) copy the whole replica set so the workflow files line up: cp -r replica-skill/replica-* ~/.claude/skills/
  6. Restart Claude Code, then say something like "set up auth" or "add payments" to trigger it.
  7. Create your own Stripe/Supabase/Resend accounts, put the keys in .env.local, and use the generated .env.example as the variable reference.