Skip to content
Rescue engineering · Toronto

Enterprise quality.
Startup speed.

You vibe-coded something real. Now it looks like AI slop and the data isn't locked down. I de-slop the UI, harden auth & storage, and rebuild what can't be saved.

ask_edmel// 2 spots left this quarter

Ask edmel…

// hit enter to start a rescue conversation

.NET 8 / C#ASP.NET Web APIBlazor / WASMSvelteKitReact / TypeScriptEF Core / DapperSQL ServerPostgreSQLSupabaseSnowflakeAWS · EC2 · LambdaDockerGitHub ActionsSAML 2.0 / OAuth 2.0JWT / SSO / RBACOpenAI APIRetell AIElevenLabsn8n / Make.comStripePostHogVercelZapierTwilioSendGridGoogle WorkspaceSlack APIAirtableNotion APITypeformMailchimpPayPalGoogle AnalyticsGoogle Maps APICalendlyWhatsApp Business API

what I fix

// 01

De-slop the UI

Kill the generic AI look. Typography, layout, and brand that feel intentional, not another card stack that could belong to anyone.

// 02

Lock down your data

Auth, RLS, secrets, API routes. Stop treating "it works in the demo" as a security model.

// 03

Stabilize what you vibe-coded

Tests where it hurts, seams where AI pasted chaos, so the next Cursor session doesn’t break production.

// 04

Rebuild what can't be saved

Keep the product idea. Replace the parts that are unmaintainable. Phased, not a six-month freeze.

known issues(5)

2 open2 in progress1 resolvedassigned to: edmel
next_steps.md// currently taking rescue projects