3 Professional Templates — Free

Give Your AI
Deep Context About You

Stop explaining yourself every time you open a new chat. One Brainfile gives Claude, ChatGPT, or Gemini everything it needs to think like your closest collaborator.

3
Free Templates
15 min
To Customize
Every AI
Claude, GPT, Gemini

No spam. Unsubscribe anytime.

💻

The Developer Brainfile

Coding style, tech stack, architecture preferences. AI that codes the way you code.

📊

The Executive Brainfile

Role, company, strategic context. AI that gives advice calibrated to your actual situation.

✍️

The Creative Brainfile

Voice, tone, audience. AI that writes in your style — not generic content-mill prose.

Templates Unlocked

Scroll down — all three templates are now fully visible. Copy the one that fits your role and paste it at the start of any AI conversation.

Brainfile Templates
Works with Claude, ChatGPT, Gemini, Grok
Plain text — no app, no login needed
Customize in 15 minutes
Template 01
The Developer Brainfile
For software engineers. Give your AI full context about your coding style, architecture preferences, tech stack, and how you like to review code — so it stops suggesting patterns you hate.
Developer
developer.brainfile.txt
# ── DEVELOPER BRAINFILE ──────────────────────────────────────────────
# Paste this at the start of any AI conversation. Customize the values.
.
role:
title: Senior Software Engineer
focus: Full-stack product engineer, primarily backend-heavy features
experience_years: 8
.
tech_stack:
primary_language: TypeScript
secondary_languages: [Python, Go]
frontend: React 18, Next.js 14 (App Router), Tailwind CSS
backend: Node.js, Express, tRPC, Prisma
databases: [PostgreSQL (primary), Redis (cache), S3 (assets)]
infra: [Vercel, AWS (Lambda + RDS), Docker, GitHub Actions]
.
coding_style:
prefer: Functional over class-based where practical
error_handling: Explicit Result types over uncaught exceptions
naming: Descriptive, no abbreviations except industry-standard (id, url, api)
comments: Explain WHY, not WHAT — code is self-documenting
tests: Unit for pure functions, integration for API routes, skip trivial getters
.
architecture_preferences:
prefer: Co-location (feature folders, not layer folders)
avoid: [Premature abstraction, over-engineering, global state]
api_style: REST for external, tRPC for internal client-server
state_management: Server state via React Query, minimal client state (zustand)
.
ai_context:
when_reviewing_code: Flag security issues first, then performance, then style
when_writing_code: Match my existing patterns — ask before introducing new deps
when_debugging: Give me the root cause + fix, skip the obvious diagnostic steps
response_style: Concise. Show me code, not lengthy explanations before code.
.
common_tasks:
- Building new API endpoints with validation and error handling
- Reviewing PRs for correctness and edge cases
- Migrating legacy Express routes to tRPC
- Writing database migration scripts (Prisma)
- Debugging production incidents from logs + stack traces
.
do_not:
- Suggest class-based React components (use functional + hooks)
- Add console.log for debugging — use structured logging (pino)
- Use any as a TypeScript escape hatch — use proper types or unknown
- Recommend jQuery, Lodash, or other utility libs that bloat bundles
Enter email to see full template
Code Review
Architecture Decisions
Debugging
PR Writing
Template 02
The Executive Brainfile
For business leaders and managers. Give your AI full context about your role, company stage, strategic priorities, and decision-making style — so it stops giving you generic MBA-speak.
Executive
executive.brainfile.txt
# ── EXECUTIVE BRAINFILE ──────────────────────────────────────────────
# Paste this at the start of any AI conversation. Customize the values.
.
role:
title: VP of Product
company_stage: Series B, 85 employees, $8M ARR
industry: B2B SaaS, HR tech
.
strategic_context:
current_quarter_goal: Ship self-serve onboarding; reduce time-to-value from 14d to 3d
biggest_challenge: Converting trials to paid — 22% conversion, want 35%
key_metric_i_own: Product-qualified leads (PQLs) and activation rate
competitors_to_watch: [Workday (enterprise), Rippling (mid-market), Lattice (adjacent)]
.
my_team:
direct_reports: 6 PMs + 1 UX researcher
eng_partner: CTO (Sarah). She values data over gut, move fast with evidence.
design_partner: Head of Design (Marcus). Strong opinions on UX — involve early.
.
decision_making_style:
prefer: Options with explicit tradeoffs, not single recommendations
risk_tolerance: Medium — will ship imperfect if we learn faster
framework: Reversible decisions fast, irreversible decisions deliberate
what_changes_my_mind: Customer data > internal opinions, always
.
communication_style:
up: Concise — CEO gets a 3-bullet summary max; board gets narrative + data
down: Context-heavy with PMs; outcomes-focused with engineers
writing_tone: Direct, confident, no hedging. No corporate jargon.
async_preferred: Loom for complex context, Slack for decisions under 5 minutes
.
ai_context:
when_I_ask_for_analysis: Give me signal, not noise. Lead with the insight.
when_I_ask_for_drafts: Match my tone (direct, punchy). No filler sentences.
when_I_ask_for_strategy: Challenge my assumptions before agreeing with me.
response_length: Short answers unless I ask to go deep. I value my time.
.
common_tasks:
- Writing product strategy memos for the board
- Preparing for difficult stakeholder conversations
- Analyzing qualitative customer research for themes
- Drafting job descriptions and leveling criteria
- Thinking through org design and team structure decisions
.
do_not:
- Give me a wall of text — I skim, I need structure
- Say "great question" or any sycophantic opener
- Recommend frameworks without explaining which situation they're for
- Assume I have unlimited resources — budget and headcount are always constrained
Enter email to see full template
Strategy Memos
Stakeholder Prep
Decision Briefs
1:1 Prep
Template 03
The Creative Brainfile
For writers, content creators, and designers. Give your AI your voice, tone, audience, and brand constraints — so it writes with you, not instead of you.
Creative
creative.brainfile.txt
# ── CREATIVE BRAINFILE ───────────────────────────────────────────────
# Paste this at the start of any AI conversation. Customize the values.
.
role:
title: Content Strategist & Writer
focus: Long-form thought leadership, newsletter, brand voice
platform: Substack (12K subscribers) + LinkedIn (28K followers)
.
audience:
primary: Founders and senior operators at 50-500 person companies
sophistication: High — they can spot generic advice from 10 feet away
pain_points: [Information overload, imposter syndrome, scaling without losing culture]
what_they_value: Specificity, honesty, counterintuitive takes with evidence
.
voice_and_tone:
overall: Confident but not arrogant. Direct but not abrasive. Warm but not soft.
sentences: Short. Punchy. Vary length for rhythm — then one that's longer to land the point.
vocabulary: Plain English. Industry terms OK when they earn their place. No buzzwords.
perspective: First person. Opinionated. I have a point of view — state it clearly.
humor: Dry, occasional. Self-deprecating over punching down. Never try-hard.
.
style_rules:
headlines: Specific over clever. Promise something the reader actually wants.
openings: Never start with "In today's..." or rhetorical questions. Hook immediately.
evidence: Real examples and data over hypotheticals. Name names when I can.
structure: Premise → Insight → Evidence → Implication. In that order.
endings: End with a clear takeaway or question. Not a summary.
.
brand_constraints:
never_say: [leverage, utilize, synergy, paradigm shift, game-changer, disruptive]
avoid: Passive voice, hedge words (maybe, perhaps, might), listicles with more than 5 items
visual_style: Minimal formatting. Bold only for emphasis, not decoration. Rare headers.
.
ai_context:
when_drafting: Capture my voice, not generic content-writer voice. Reread my examples first.
when_editing: Tell me what's weak and why. Don't soften feedback.
when_brainstorming: Give me the unconventional angle I haven't considered yet.
response_style: Show me the draft, then one line on your choices. I'll iterate.
.
common_tasks:
- Writing and editing weekly newsletter issues (1,200-1,800 words)
- Repurposing long-form pieces into LinkedIn posts (3-5 key ideas)
- Headline testing — writing 10 variants for A/B testing
- Developing content ideas from notes, conversations, and observations
- Ghostwriting essays in my voice for client executives
.
do_not:
- Write in a voice that sounds like an AI — if I can tell, I'll rewrite it anyway
- Use em-dashes in every sentence — they've become a giveaway
- Add a "conclusion" section — my pieces end when the last insight lands
- Suggest adding more content — help me cut to the essential 10%
Enter email to see full template
Newsletter
LinkedIn
Brand Voice
Ghostwriting

Unlock All 3 Full Templates

Enter your email to see the complete Developer, Executive, and Creative Brainfiles — plus get new templates as they ship.

Free. No credit card. Unsubscribe anytime.

How to Use Your Brainfile
1

Copy the template that fits your role

Pick Developer, Executive, or Creative. Copy the full template text — it's plain text, no special format needed.

2

Customize the values to match you

Replace the placeholder content with your actual context — your real stack, your real company, your real voice. Takes about 15 minutes.

3

Paste it at the start of any AI conversation

Works in Claude, ChatGPT, Gemini, Grok — any AI with a chat interface. Paste your brainfile before your first message, or set it as a custom instruction / system prompt.

4

Get responses calibrated to your actual situation

The AI now knows your preferences, constraints, and style. No more explaining your tech stack. No more generic advice. No more fixing the AI's tone after every response.