agentleFS
Sign inStart free
charanjit-singhcharanjit-singh/lovable-skills/skills/lovable-ship-checklist/SKILL.md

lovable-ship-checklist

Skill10 starsChanged 6 months agoMITView on GitHub

Use when I say I'm about to launch, ship, go live, release, or ask if the app is production-ready. Run the checklist and report pass/fail per item. Not for feature building, refactors, or SEO copywriting from scratch.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    No tenant or user ID accepted from request bodies for authorization.

    line 31
  2. Distinctive:

    Test cards work in test mode.

    line 37
  3. Distinctive:

    No placeholder copy ("Lorem ipsum", "TODO", "Your headline here").

    line 44
  4. Very specific:

    Every input has a visible label.

    line 48
  5. Very specific:

    No service-role or webhook secrets exposed in VITE_* variables.

    line 55

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Launch / ship checklist

Walk every section. Report pass, fail, or needs manual check. Do not say "ready to launch" until all pass or are explicitly waived.

Account flows

  • Sign-up, sign-in, sign-out, password reset work end to end.
  • Signed-out users cannot access protected routes.
  • Post-login redirect lands on the correct page.

Core surfaces

  • Home and primary routes render without console errors.
  • Lists/feeds have real empty states (not "No data" alone).
  • Long actions show loading; errors offer retry or clear message.
  • Mobile (~375px): no horizontal scroll; primary actions reachable.

Data and permissions

  • User tables have RLS enabled (see supabase-rls-and-auth if fixing).
  • Cross-account access blocked — flag needs manual check; ask for second test account.
  • Destructive actions (delete, cancel, refund) require confirmation.
  • No tenant or user ID accepted from request bodies for authorization.

Billing (if payments are part of the product)

  • Stripe webhook endpoint configured, signature verified, idempotent (stripe-payment-webhooks).
  • subscriptions / orders table is the source of truth — no client query-string entitlement.
  • Test cards work in test mode; live keys only on production env.
  • Failed-payment banner + Customer Portal link (payment-failed-and-recovery).

Content and trust

  • App name, favicon, OG image, meta description set on public pages.
  • Privacy policy and terms links work (footer).
  • No placeholder copy ("Lorem ipsum", "TODO", "Your headline here").

Accessibility (quick pass)

  • Every input has a visible label; icon-only buttons have aria-label.
  • Keyboard: Tab order makes sense; modal Escape closes; visible focus ring.
  • Text contrast ≥ 4.5:1 on body text.

Environment and secrets

  • No localhost, dev URLs, or test API keys (sk_test_*) in production paths.
  • No service-role or webhook secrets exposed in VITE_* variables.
  • Required env vars set in Lovable / hosting; secrets configured in Supabase for edge functions.
  • Analytics/events fire on signup, activation, and key conversions.

Observability

  • Errors visible (Sentry/PostHog/Logflare or at least Supabase function logs).
  • 404 and 500 pages exist and link home.

Final output

  1. Summary of failures and manual checks, priority order.
  2. Go / no-go with explicit blockers.
  3. List items waived (and why) so they are not forgotten next ship.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free