Replica Backend, add auth, database, payments and integrations to your app clone

Prerequisites: an architecture plan from replica-architect; accounts you create yourself for the providers needed (Stripe, Supabase, Resend or Postmark, Google Cloud as applicable), with test keys first. Install "Replica Backend, add auth, database, payments and integrations to your app clone" for me. It gives my agent @Jakeschincariol's backend workflow, the backend step of the Replica pack: working auth, database migrations and access rules, Stripe payments in test mode, transactional email, background jobs and integrations through official APIs only, plus a security checklist. I create the accounts and keys myself; the agent never signs up for a service, never types a password, card or live key, and writes .env.example with variable names and no values. Repository: https://raw.githubusercontent.com/Jakeschincariol/replica-skill/77c9436fb3d18c3d58169efb8caf4fe906b0dc51/replica-backend/SKILL.md Pinned version: install the code at commit 77c9436fb3d18c3d58169efb8caf4fe906b0dc51 exactly. Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file from the repository path into a temporary folder 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code: you create your own accounts and keys and put keys in .env.local, the agent writes .env.example with names only and never types a password, card or live key. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "replica-backend". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. have the architecture plan ready; create the provider accounts and put test keys in .env.local myself). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. In Muse, invoke pack neighbour skills by name, not as /slash commands. If anything looks off, stop and ask me. After installation, ask me if I want to leave private feedback Private for now: only the Skill Harbor team sees it. Sellers may be looped in later.