Prompt Engineering

Build Project Memory for AI

Stop re-explaining your project in every new chat. Capture it once as a context profile the AI keeps across every conversation — stack-inferred conventions and all.

Overview

The opening of every new chat is the same three paragraphs: what the app is, the stack it runs on, the rules the team follows. Project memory ends that. This setup builds a full context profile for Helmsman, a multi-tenant SaaS dashboard — the overview, the stack (React, TypeScript, Node, PostgreSQL, Prisma), the team conventions, and a glossary — then the engine adds the conventions and never-assume rules the stack implies. Paste it once into a Claude Project (or any tool's persistent instructions) and the AI starts every chat already knowing the project.

Workflow

Describe the project once
Name, overview, mode, and stack — the facts you keep retyping into new chats.
Let the engine fill the rest
The stack you typed becomes naming rules, conventions, and never-assume lines automatically.
Paste it where it persists
Drop the profile into your tool's project instructions; every new chat starts informed.

Why This Works

The profile is loaded once and applies to every chat — no more re-explaining the basics
Stack detection turns "React, TypeScript, Postgres" into the conventions those tools imply
The never-assume section stops the model guessing the things it always gets wrong

Best for

Teams tired of re-explaining the same project
Multi-tenant SaaS codebases
Anyone setting up a Claude Project or custom instructions

Not for

A one-off task persona — that's the System Prompt Generator
Carrying an in-progress task to a new chat — that's the Context Handoff Builder

Use cases

Teams tired of re-explaining the same project
Multi-tenant SaaS codebases
Anyone setting up a Claude Project or custom instructions

Customize This Resource

Opens this project in Project Context Builder. Build to get the full context profile — then adjust the mode, stack, glossary, and output target.

Open in Project Context Builder

Prompt Template

# Project Context: Helmsman

> Paste this into your Claude Project: open the project, Edit, and add it to the project instructions.

## Project Overview
Helmsman is a multi-tenant SaaS dashboard that lets agencies manage client ad campaigns from one place. Each agency is a tenant with isolated data and per-seat billing.

## Core Facts
- Project type: SaaS Product
- Primary stack: React, Tailwind CSS, Express, Node.js, PostgreSQL, Prisma
- This is a multi-tenant SaaS product — tenant data isolation and uptime are non-negotiable.

## Tech Stack
- React
- Tailwind CSS
- Express
- Node.js
- PostgreSQL
- Prisma
- TypeScript

## Team Conventions
- Every API route is covered by an integration test.
- Feature flags gate anything not GA yet.
- Money is stored in integer cents, never floats.
- Function components with hooks only — no class components; keep components pure and side effects in effects. (React)
- Style with Tailwind utility classes; reach for custom CSS only when no utility fits. (Tailwind CSS)
- Keep route handlers thin; put logic in services and use middleware for cross-cutting concerns. (Express)
- Prefer async/await over callbacks; never block the event loop with sync I/O in request paths. (Node.js)
- Change the schema through `schema.prisma` and migrations; use the generated client, not raw SQL, unless necessary. (Prisma)
- No `any` — prefer `unknown` with narrowing; keep `strict` mode on and types honest. (TypeScript)

## Naming Rules
- Database: snake_case for tables and columns; plural table names. (PostgreSQL)
- camelCase for variables and functions, PascalCase for types and components. (TypeScript)

## Architecture Principles
- Every data access is scoped to a tenant — never return one tenant's data to another.
- Treat billing, auth, and data-isolation code as critical paths; changes there need extra scrutiny.
- Design for graceful degradation — a failing feature must not take the whole product down.

## Glossary
- **Tenant** — a paying agency account; the top-level data boundary.
- **Seat** — one billable user within a tenant.
- **MRR** _(abbreviation)_ — monthly recurring revenue.
- **Workspace** — a client account owned by a tenant.

## Always Remember
- Production data is never used in development or tests.
- All timestamps are stored in UTC.
- This profile is the source of truth for project facts — prefer it over general assumptions.

## Never Assume
- Do not assume a feature is generally available — check the feature flag.
- Do not assume a component is class-based — the codebase uses function components and hooks.
- Do not add a global stylesheet or CSS-in-JS — styling is utility-first with Tailwind.
- Do not assume the schema — reference the migrations or schema file before writing a query.
- Do not hand-write SQL when a Prisma query exists — and do not edit generated client code.
- Do not assume a value's type — check the type definition before changing a signature.
- Do not assume a request is for a single global dataset — it is tenant-scoped unless stated otherwise.
- Do not assume the current user has access to a resource — authorization is checked explicitly.
- When a fact is missing from this profile, ask — do not invent it.

## AI Usage Notes
- In Claude, project instructions apply to every chat inside the project — paste this once and start new chats freely.
- This profile is project KNOWLEDGE, not behavior — for a task persona (role, tone, escalation rules), build a System Prompt in the System Prompt Generator.
- It is durable project identity, not work state — to continue an in-progress task in a new chat, use the Context Handoff Builder.
- Profile completeness: 100/100 (Complete) — bracketed gaps, if any, mark missing info that was never invented.

Related Resources

Explore more resources that work well with this one.