Brainforge Standards (playbook)
The canonical filesystem path is knowledge/standards/. The repo root also has a standards/ symlink to this tree for shorter paths and compatibility with older links. Prefer knowledge/standards/ in new documentation and Cursor rules.
This tree is the central internal repository for writing workflows, AI-assisted productivity, prompts, templates, and reusable patterns across client work. It pairs with knowledge/ (internal transcripts, notes, and org context). Updates here are restricted to authorized contributors.
This tree is the single source of truth for:
- Standardized writing templates (SOWs, PRDs, SOPs)
- Best-practice examples and reference documents
- Company-wide prompts for Cursor and other LLM tools
- Onboarding guides for using GitHub, Markdown, and Cursor
- Consulting frameworks, sales patterns, and industry overviews
- Internal case studies and lessons learned
Client-specific content does not live here. Each client has their own isolated repo. Standards provide the reusable building blocks those repos rely on; internal working files live under knowledge/.
Why This Exists
Brainforge uses AI as a core lever for speed, clarity, and output quality. For AI assistance to work well across different projects and roles, the company needs:
- Consistent structure
- High-quality templates
- Reusable patterns
- Clear instructions
- A unified knowledge base
This repo solves these needs by centralizing everything that should be shared across clients while keeping sensitive material inside individual client repositories.
How to Use This Repository
For Non-Technical Team Members
Start with the how-to-use guides in the main folder:
- How to use Cursor as your main writing and working environment
- How to use GitHub with minimal technical background
Then move into the onboarding/ folder:
- How to write with AI and run quality checks
- How to quickly draft SOWs, PRDs, SOPs, and client documents
- Setup GitHub CLI - Configure gh CLI to create PRs from Cursor
- Connecting Github and Cursor to Linear and other software tools
You will be able to:
- Open a client repo in Cursor
- Reference templates from this Playbook
- Reference raw documentation (transcripts, notes, text documentation) from the Vault
- Ask Cursor to combine client context + Playbook patterns
- Write documents 5–10x faster with consistent structure and tone
For Technical Team Members
Use this repo to:
- Maintain and improve prompts
- Update templates as product and consulting practices evolve
- Consolidate patterns discovered across client work
- Ensure knowledge becomes reusable, not siloed
- Review Cursor Agent Best Practices - All agents should follow these official Cursor best practices
Repository Structure
standards/
Contains high-level overview and general How-To’s (lives in brainforge-platform).
onboarding/
Guides for setting up Cursor, using GitHub, understanding Markdown, and writing effectively with AI.
writing/
Writing templates, checklists, and examples for:
- SOWs
- PRDs
- SOPs
- Meetings
- Tickets
- Review
Each category includes:
- A template (
*-template.md) - A checklist (
*-checklist.md) - Example sanitized documents
prompts/
All official Brainforge prompts for:
- Writing (SOW, PRD, SOP)
- Reviewing and quality checks
- Meeting summarization
- Ticketing and action extraction
These prompts represent the standardized “voice” and reasoning patterns Brainforge expects in internal and external documents.
knowledge/
Reusable consulting frameworks, sales patterns, industry overviews, and AI usage guidelines.
How It Works With Client Repos
Each client repository contains sensitive, client-specific files:
- Real SOWs, PRDs, SOPs
- Meeting notes, transcripts, Slack-derived summaries
- Client architecture, plans, and internal discussions
When drafting documents in a client repo, you can use prompts that reference this Playbook for:
- Structure
- Writing style
- Domain patterns
- Example SOW or PRD structures
- Quality reviews
This keeps client data isolated while maximizing reuse of Brainforge’s best internal materials.
Contribution Guidelines
See CONTRIBUTING.md for:
- How to propose changes
- Rules for adding new templates or prompts
- Standards for sanitizing internal examples
- Documentation formatting and naming conventions
All contributions should follow the principle of reusability:
If something could help more than one client or teammate, it belongs in the Playbook.
Philosophy
This repository exists to:
- Make high-quality writing the default
- Leverage AI in a controlled, consistent, and powerful way
- Reduce duplicate work across teams
- Enable new hires to reach full productivity faster
- Capture institutional knowledge that previously lived in private documents or individual memory
The Playbook should evolve every week as Brainforge learns, improves, and scales.
Questions or Improvements
If you want to add a new template, improve a prompt, or share a reusable insight, open a pull request or talk with the team maintaining this repo. Every improvement compounds and benefits the entire company.
Welcome to the Brainforge Playbook.