A reusable way to build

One foundation. Many SaaS products.

Use the same structured starting point across client MVPs and SaaS products. Your agent follows the same rules while you focus on what makes each product different.

Build what makes the product different

Start past the recurring setup. Put your attention into the workflows, experience, and details that make each product worth building.

Your agent knows where new code belongs

Give Cursor, Claude Code, Copilot, Windsurf, and other agents the same rules, examples, and place for every feature.

Keep the code easy to review and hand over

Keep the complete TypeScript source inside a structure you can review, explain, and pass to the next developer.

How the foundation works

Your agent knows where new code belongs.

Every coding agent starts with the same project rules and working examples. Features have a clear home, reusable Skills guide common work, and provider code stays separate from the product built on top.

VS Code showing Frontend Accelerator agent instructions, Agent Skills, feature folders, and provider adapters
Agent instructions, reusable Skills, feature folders, and provider separation—all inside the codebase your agent works in.
View full-size image

AGENTS.md

One set of project rules

Cursor, Claude Code, Copilot, and Windsurf start from the same instructions and checks.

.agents/skills/

Reusable Skills

Agents can load repo-local guidance for Next.js, Stripe, testing, accessibility, and other recurring work.

src/features/<feature>/

A clear home for each feature

New product behavior has a known place instead of spreading through whichever file was convenient.

src/lib/**/adapters/

Payments, data, and AI stay separate

Provider code stays away from the product features that use it, so changes are easier to trace.

The recurring work

... and the common SaaS systems are already connected.

These are not the whole product. They are a working example of how the structure fits together—and a head start you do not have to rebuild for each new project.

Authentication

Google, GitHub, Facebook, and email magic links

Payments

Stripe or Lemon Squeezy, including payment webhooks

Database

Choose Firestore or MongoDB while provider code stays separate

Roles and access

Admin and member access with protected admin routes

Dashboard

Working profile, product, user, and content areas

Content and SEO

Blog, glossary, metadata, related content, and sitemaps

Localization

Ready for multiple languages

Email

SMTP support for sign-in and application email

UI foundations

Responsive marketing, sign-in, and dashboard components