Most vibe coders don't know this:

You can radically reduce errors, cut credits, enable an agent to learn, and make vibe engineering a breeze.

Just give your agent a memory.

I'm really impressed by Claude Skills (instructions/scripts/resources). But those need to be managed by humans.

You can push things even further by using .md files an agent can edit (works even in Lovable).

Ask your coding agent to:

• Document an existing solution

• Compare the current implementation to documentation

• Refer to those documents when starting a new task

• Ask an agent to translate a PRD into a set of tasks as .md files

My current /documentation/*.md for accredia[.]io you can steal and adjust to your domain:

• analytics.md - Documents the analytics system for tracking certificate and profile interactions across student, public, and admin areas with privacy-focused event logging and real-time dashboards.

• architecture.md - Comprehensive guide to the application's secure backend-first architecture using Clerk authentication, Supabase Edge Functions, and JWT-based authorization with organization scoping.

• cron.md - Details the automated hourly sync jobs for organizations, user profiles, and email reconciliation between Clerk, Postmark, and the Supabase database.

• database.md - Central reference for all database table schemas including organizations, profiles, courses, certificates, analytics events, email notifications, and API keys.

• design.md - Complete design system defining typography, color palette, component standards, interaction patterns, toast variants, and accessibility guidelines for consistent UI/UX.

• emails.md - Describes the queue-based email notification system using Postmark for certificate delivery with retry logic, webhooks, reconciliation, and template management.

• fuckups.md - Tracks development mistakes and lessons learned including authentication errors, user experience issues, and best practices to avoid repeating them.

• permissions.md - Defines the role hierarchy (admin, member, student, anonymous) and access control rules for all endpoints with detailed permission matrices and security enforcement patterns.

• security.md - Outlines XSS protection, Content Security Policy, authentication security, file upload validation, input sanitization, and quiz anti-cheating measures.

• socialsharing.md - Documents the hybrid edge architecture for social media previews using Netlify and Supabase Edge Functions with bot detection, image generation, and multi-layer caching.

• todo.md - Lists pending improvements including human-friendly database error messages and creating a reusable DatePicker component to reduce code duplication.

• variables.md - Comprehensive guide to all environment variables and secrets across frontend, Netlify edge functions, Supabase vault, and database functions with security best practices.

The best part?

I haven’t touched any of those documents - they were all created, updated, and managed by an agent.

Hope that helps!

—

P.S. Enjoy this? You might like the rise of vibe engineering: productcompass.pm/p/vib…