Sandpaper Engine
Launch OS
The premium command-center vision for Sandpaper, where readiness, fixes, prompts, risk analysis, and final launch verification come together in one place.
Wow modules
15
All requested enhancements represented
Launch gates
3/8
Final Launch Room pass state
Prompt bundles
5
Grouped builder-ready fix packs
Guarded score
89%
Almost Ready until blockers clear
15 Enhancement Modules
Every idea is represented as a deterministic product surface with a clear real-integration path.
Real Repo Import
ingestion
Users see GitHub, ZIP, and manifest paths in one import command center.
Local manifest and pasted file tree intake already feed deterministic scans.
Launch Readiness Timeline
planning
The project feels alive because every scan becomes a visible launch journey.
A deterministic timeline shows score movement from first scan to launch room.
One-Click Fix Plan Generator
planning
The app tells builders exactly what to fix first, where, why, and how to verify.
A ranked fix plan includes files, reason, and verification commands.
PromptPack Bundles
prompts
Users can copy an entire auth, billing, Supabase, or deploy fix bundle.
Bundle cards group prompts by launch phase and builder target.
AI Builder Mode Selector
prompts
Every prompt adapts to Cursor, Lovable, Claude Code, Replit, Bolt, or Windsurf.
Builder profile cards show behavior, style, and stop-condition differences.
Risk Heatmap
audit
Founders instantly see which systems are most dangerous before launch.
A visual heatmap ranks auth, billing, database, AI, legal, deploy, UX, and support.
Before/After Scan Diff
planning
Re-scans become proof that work is actually reducing launch risk.
The diff separates resolved, still open, new issues, score change, and next fix.
Founder Mode vs Engineer Mode
trust
The same issue can be explained as business risk or implementation detail.
Mode cards translate a Stripe webhook blocker into founder and engineer language.
Launch Blocker Severity Explainer
trust
Every blocker explains what breaks, what to fix, and what proves it is fixed.
Severity cards show impact, failure mode, fix, and verification.
Auto-Generated README Audit
audit
The app catches missing setup docs before users or reviewers get stuck.
A README checklist checks setup, env vars, deploy notes, screenshots, support, and pricing.
Environment Variable Doctor
audit
Env mistakes become visible before deploy, auth, billing, or AI routes break.
Env Doctor flags missing app URL, unsafe public keys, and undocumented Stripe/Supabase vars.
Supabase RLS Policy Auditor
audit
Supabase safety gets its own launch-grade audit instead of generic database warnings.
RLS cards check owner columns, enabled RLS, policies, and service-role safety.
Stripe Launch Auditor
audit
Billing readiness becomes a complete product surface, not one warning.
Stripe checklist covers checkout, webhook signature, customer mapping, portal, plans, and refunds.
Final Launch Room
launch
The app turns launch into a cockpit with pass/fail gates and one final readiness call.
Launch Room gates show build, auth, billing, RLS, AI, legal, support, and final score.
Sandpaper Score Badge
trust
Users get a shareable repo badge that makes launch readiness visible.
A badge preview and markdown snippet are generated from the guarded score.
Launch Readiness Timeline
Before, during, and after scan progress.
42%
Step 01
First import
Raw AI-built app imported with missing auth, Stripe, and RLS proof.
68%
Step 02
ShipGuard scan
Critical blockers identified and grouped by launch phase.
82%
Step 03
Prompt fixes
Billing/auth duplicates reduced after builder-ready prompt bundles.
89%
Step 04
Launch room
Guarded score remains below Launch Ready until legal/support gates pass.
Risk Heatmap
System-by-system launch risk at a glance.
Auth
42%
Protected routes and recovery flow need proof.
Billing
48%
Webhook verification and customer mapping are launch blockers.
Database/RLS
55%
User ownership policies need a complete pass.
AI Cost
62%
Rate limits and usage tracking should ship before paid launch.
Legal
58%
Privacy, terms, cancellation, and AI disclaimer are incomplete.
Deploy
81%
Build path exists, but env proof still matters.
UX
76%
Onboarding and empty states need final polish.
Support
69%
Users need a clear contact path before launch.
One-Click Fix Plan
Exact order, files, reason, and verification for the next fixes.
Fix 1
Lock down auth and protected routes
Launch users cannot trust account areas if protected routes are public or recovery is missing.
Run build, open dashboard unauthenticated, confirm redirect or protected-state copy.
Fix 2
Verify Stripe webhook safety
Paid access cannot be trusted without signature verification and idempotency planning.
Confirm webhook secret is server-only and route rejects unsigned events.
Fix 3
Prove Supabase RLS ownership
User-owned data must be protected before any real customer enters the product.
Check every user-owned table has `user_id`, RLS enabled, and owner policies.
Fix 4
Add AI usage controls
AI routes can create runaway cost without quotas, limits, and logging.
Confirm rate checks happen before provider calls and limit errors are clear.
PromptPack Bundles
Grouped prompts for complete launch phases instead of one-off fixes.
Auth Fix Bundle
Cursor
4
Stop after login, signup, recovery, and protected route checks pass.
Stripe Fix Bundle
Claude Code
5
Stop after webhook, checkout, portal, plan limits, and refund copy are verified.
Supabase RLS Bundle
Cursor
3
Stop after schema, RLS, and service-role boundaries are verified.
AI Cost-Control Bundle
Replit
3
Stop after rate limit, usage logging, and fallback behavior are visible.
Launch Polish Bundle
Lovable
6
Stop after onboarding, empty states, legal, support, and final smoke test pass.
Founder Mode vs Engineer Mode
Same blocker, different explanation depth.
Founder Mode
Stripe webhook verification is a revenue-risk blocker. If this is wrong, users may pay but never receive access, or keep access after cancellation.
Launch Blocker Explainer
Severity becomes understandable and actionable.
Why this blocks launch
Paid users can lose access sync or receive access without a verified payment event.
What can go wrong
Unsigned webhook calls, duplicate events, stale subscription state, and support refunds.
What to fix
Verify signatures, document secrets, map customers to users, and add idempotency.
How to verify
Run build, inspect server-only env usage, and simulate rejected unsigned events.
README Audit
Auto-generated documentation readiness checks.
Local setup command documented
Required env vars listed
Vercel deploy notes included
Screenshots or product preview included
Support/contact path visible
Pricing or waitlist state explained
Environment Variable Doctor
Deploy-breaking env mistakes surfaced early.
Add `NEXT_PUBLIC_APP_URL` for callback and webhook URL consistency.
Keep `SUPABASE_SERVICE_ROLE_KEY` server-only and never `NEXT_PUBLIC_`.
Document `STRIPE_WEBHOOK_SECRET` separately from `STRIPE_SECRET_KEY`.
List AI provider keys without shipping real values.
Supabase RLS Auditor
Dedicated database safety checks.
Every user-owned table includes `user_id`.
RLS is enabled for projects, scans, issues, prompts, and reports.
Owner select/insert/update/delete policies are present.
Service-role behavior is separated from browser clients.
Stripe Launch Auditor
Billing readiness as a focused specialist audit.
Checkout entry point exists or has explicit not-live copy.
Webhook route verifies signatures before event handling.
Subscription status maps to a user/customer record.
Customer portal and cancellation/refund language are visible.
Plan limits are documented in product UI.
Final Launch Room
A cockpit view for launch gates and final readiness.
Build passes
PassAuth protected
Needs proofStripe verified
Needs proofSupabase RLS verified
PassAI rate limits
Needs proofLegal pages ready
Needs proofSupport path visible
PassFinal smoke test
Needs proofSandpaper Score Badge
A shareable repo badge concept for launch readiness.
Sandpaper Launch Readiness
89%
Almost Ready
