Skip to content
SkillModel-led811 tokens in use

replica-backend

Builds the backend of an app clone: auth, migrations with access rules, Stripe in test mode, email, jobs and official-API integrations.

10,140 stars on the repository MIT LicenseJakeschincariol/replica-skill · replica-backend
/plugin install replica-skill@replica-skill
View source

Install command as written in the repository's README

Skill label

measured from its files

What installing replica-backend costs

99tokens idle
811tokens in use

Idle is what sits in context while the skill is installed. In use is its instructions, loaded when it runs. Counts are approximate, made offline with cl100k_base.

Model dependence Model-led

Script-ledMixedModel-led

Mostly instructions, so how well it works depends on the model that follows them.

This describes the skill's structure, how much of it is scripts. It does not say how well it works.

Touches

shelldetected

Declared tags come from the skill's frontmatter; detected ones from its scripts, its code blocks and the commands it names in inline code. This is detected, not audited.

How it scores

Quality

How well the skill is written, counted from its own files: its frontmatter, its steps, examples, stated output and constraints, its size and whether every file it ships is one it names.How we score it →
Good
  • Frontmatter12/15
  • Structure9/25
  • Examples3/15
  • Output15/15
  • Size15/15
  • Resources10/15

Security

Starts at 100 and loses points for each thing in the skill's files that a reader should look at first.How we score it →
Excellent

No findings.

Repository health

Pre-computed score based on development activity, maintenance, community, maturity, and trend momentum.How we score it →
Needs attention
  • Development activity32
  • Maintenance4
  • Community64
  • Maturity12
  • Momentum40

replica-backend wires up the server side of a clone from the architecture plan. It covers sign up and sessions, database migrations with access rules, Stripe Checkout and webhooks, transactional email, background jobs and third-party integrations.

You create the accounts and keys yourself and the agent writes only variable names into .env.example. Everything runs in test mode until deploy.

What You Get

  • Auth with email verification, password reset, optional OAuth, roles and real account deletion
  • Checked-in migrations with row level security or an authorisation function on every table
  • Stripe Checkout and Customer Portal with signature-verified, idempotent webhook handlers
  • Transactional email, retried background jobs and an .env.example with names only
  • A replica/backend.md with the security checklist ticked

Common Use Cases

  • Adding login, teams and roles to a clone that runs on seed data
  • Connecting Stripe in test mode with webhooks that survive retries
  • Starting Google OAuth verification early for calendar or other sensitive scopes

What Makes It Unique

It sets hard rules about who holds the keys: the user creates every account and live key, the agent never types a password or card number, and only official public APIs with your own credentials are used. It also tests access rules with a second user and treats one-click cancelling as a requirement.

Under The Hood

The skill is instructions only. The agent writes migration files, server code, a seed script and markdown notes into your project, and the checklist mentions running a dependency audit with npm. It reads and writes files and runs commands in your repository. It points at third-party services such as Stripe, Supabase and Resend, using keys you place in env files yourself.

Join founders building with open source

Opinionated takes, migration guides, cost-saving tips, and insights from the open source ecosystem.

Subscribe on SubstackJoin 750+ subscribers