What's inside Stacks Commands Memory Pricing

Ship fast.
Stay clean.

A complete set of markdown files that turns Claude Code into a senior architect — applying DDD, CQRS, and clean architecture from day one.

Get the BoilerPlateClau — €9.99 See what's inside ↓

~/my-startup

$ cp -r boilerplate/. .

$ claude

✓ Reading CLAUDE.md...

✓ Detected stack: NestJS + Prisma

✓ Loaded core/ conventions

✓ Ready. DDD + CQRS enforced.

$ /new-feature "user subscription cancellation"

// what's inside

Everything Claude needs
to build it right.

Drop these files into any project. Claude reads them on startup and applies your architecture automatically — no repeated instructions. See the files

🏛️

Architecture Core

DDD, CQRS, bounded contexts, layering rules, and a decision framework. Agnostic to stack or language.

⚡

5 Workflows

Step-by-step processes for new features, services, bugs, refactors, and large codebase searches.

🧩

12 Design Patterns

Each pattern with startup-specific guidance: when to use it, when to skip it, and anti-patterns to avoid.

📐

Language Conventions

Opinionated rules for Node.js/NestJS, PHP/Symfony, and Go/Gin — naming, structure, testing, tooling.

🎨

Frontend System

React + Tailwind design tokens, component rules, and page structures. Claude fills in your style collaboratively.

⌨️

5 Slash Commands

/new-feature, /new-service, /ddd-review, /bug-investigation, /search-context — one command, full workflow.

// philosophy

Ship as fast as possible
with scalability.

01 —

Full DDD from day one

Not after product-market fit. Not after the rewrite. Bounded contexts, aggregates, and domain events from the first commit. Shortcuts get a TODO: [DDD] tag — never silent.

02 —

CQRS everywhere

Commands mutate state. Queries read from separate read models. Always. The read model is updated via domain events — never directly from a handler.

03 —

Tests after, but always

No TDD by default — iterate fast. But a feature isn't done until the tests are written. Domain layer at 100%. Application layer at least 80%.

04 —

Stop and ask, never guess

If a requirement is unclear, Claude stops and asks. It never makes silent assumptions on business logic. Ambiguity surfaces early — not after three layers of wrong implementation.

// supported stacks

Three stacks.
One architecture.

Core principles are language-agnostic. Language-specific files handle the rest.

TypeScript

frameworkNestJS

ormPrisma

testingVitest / Jest

lintESLint + Prettier

PHP

frameworkSymfony 6+

ormDoctrine

testingPHPUnit

lintPHP CS Fixer

frameworkGin

dbsqlc

testingtesting + testify

lintgolangci-lint

// slash commands

One command.
Full workflow.

Type a command in Claude Code. The entire workflow runs — domain modeling, layering, tests, review.

/new-feature "description"Runs the full feature workflow — 6 clarifying questions, domain first, application layer, infrastructure, interface, tests, self-review.

/new-service "BoundedContext"Scaffolds a complete bounded context from scratch — aggregate, commands, queries, repository, read model, controller stubs.

/ddd-review "path/to/module"Audits code for DDD/CQRS violations. Returns PASS, PASS WITH WARNINGS, or FAIL with specific issues and suggested fixes.

/bug-investigation "description"Systematically traces the bug through all layers, identifies root cause, writes the missing test first, then fixes it.

/search-context "topic"Explores the codebase and stores structured findings in .context/topic-searched.md — reused in future sessions automatically.

// file structure

34 files.
Every layer covered.

Drop the folder in your project root. Claude reads it on startup — no setup, no config.

core/ 6 files

architecture.md

ddd-patterns.md

cqrs-guide.md

testing-strategy.md

api-design.md

error-handling.md

workflows/ 5 files

new-feature-workflow.md

new-service-workflow.md

bug-investigation-workflow.md

refactor-workflow.md

large-search-workflow.md

patterns/ 13 files

index.md ← decision tree

creational/

factory-method · builder · singleton

structural/

adapter · facade · proxy · decorator

behavioral/

strategy · observer · command · …

frontend/ 6 files

project-style.md ← per-project

tokens.md

components.md

pages/

landing · dashboard · auth

node-ts/ · php/ · go/

per stack, 3 files each:

CLAUDE.md

conventions.md

testing.md

entry + memory

CLAUDE.md ← reads first

.claude/commands/

5 slash commands

.context/

session memory · committed to git

// session memory

Claude remembers.
Across every session.

Claude has no memory between sessions — unless you give it one. The BoilerPlateClau ships with a .context/ folder: a set of markdown files Claude writes to and reads from, so knowledge about your codebase accumulates over time instead of evaporating.

how it works

You run /search-context "payments"

Claude reads your codebase — controllers, services, events, handlers — building a structured map of how payments work in your system.

Claude writes .context/payments-searched.md

The findings are saved in a structured markdown file: bounded context, key aggregates, event flow, open questions, and files to watch.

You commit .context/ to git

The whole team shares the same knowledge base. New devs onboard instantly. Claude never starts from zero again.

✓

Next session — Claude already knows

CLAUDE.md instructs Claude to read .context/ on startup. Your codebase context is loaded before the first message.

example .context/ files

.ctx

payments-searched.md

Stripe integration map, PaymentAggregate structure, webhook handler chain, known edge cases with 3DS.

.ctx

auth-searched.md

JWT + refresh token flow, UserAggregate, session invalidation strategy, OAuth providers wired.

.ctx

notifications-searched.md

Event-driven dispatch via NotificationSent domain event, email + push channels, retry logic.

.md

CLAUDE.md reads .context/ on start

The entry point. Instructs Claude to load all context files before the first response in every session.

                        # in CLAUDE.md

                        ## Session Memory

                        On startup, read all files in .context/.
These are your long-term memory across sessions.

// pricing

One price.
Yours forever.

No subscription. No per-seat. No tiers. Pay once, use on every project.

one-time

BoilerPlateClau

€9.99

one-time payment

✓ 34 markdown files, ready to use
✓ DDD + CQRS + clean architecture
✓ Node.js, PHP, and Go conventions
✓ 12 design patterns with startup guidance
✓ 5 slash commands for Claude Code
✓ Frontend system (React + Tailwind)
✓ Free updates forever
✓ Memory management

Get the BoilerPlateClau →

·Secure checkout·Instant download

// get started

Stop explaining architecture.
Just ship.

Drop 34 files into your project. Open Claude Code. Start building — with a senior architect that never forgets the rules.

Get BoilerPlateClau — €9.99 →

Everything Claude needsto build it right.

Ship as fast as possiblewith scalability.

Three stacks.One architecture.

One command.Full workflow.

34 files.Every layer covered.

Claude remembers.Across every session.

One price.Yours forever.

Stop explaining architecture.Just ship.

Everything Claude needs
to build it right.

Ship as fast as possible
with scalability.

Three stacks.
One architecture.

One command.
Full workflow.

34 files.
Every layer covered.

Claude remembers.
Across every session.

One price.
Yours forever.

Stop explaining architecture.
Just ship.