SmarterContext
Issue #001 · Thu, Jun 25, 2026
Your AI keeps forgetting what you told it. Learn to fix that. |
Structuring a context.md so the AI actually uses it
A wall of text gets skimmed. Headers and bullets get obeyed. |
Models attend to structure. A context file written as a paragraph blob gets compressed and half-ignored; the same facts under clear headers (Identity, Constraints, Glossary, Don'ts) get retrieved far more reliably. Put your hardest rules in a short Don'ts list — negative constraints are the single most-forgotten thing, so make them impossible to miss. Lead with what matters; the top of the file gets the most attention. |
▸ The template
# context.md — the canonical skeleton
## 1. Identity
Who I am, audience, voice in one line each.
## 2. Domain glossary
- ARR = annual recurring revenue
- "the gateway" = our Stripe proxy service, NOT Cloudflare
## 3. Hard constraints
- Stack is fixed: Python 3.11, no new dependencies.
- All money handled in integer cents, never floats.
## 4. Don'ts (read these twice)
- Don't invent API endpoints — ask if unsure.
- Don't rewrite working code I didn't ask you to touch.
## 5. Current task
- (one line, swapped per session) |
▸ Level it up
New to this: Add four headers to your context: Identity, Glossary, Constraints, Don'ts. Just those four.
Vibe coder: Front-load the file — put your most-violated rule in the first 10 lines, because that's where the model attends most.
Advanced: Template the skeleton across every project and lint it in CI: a pre-commit check that fails if a context.md is missing the Don'ts or Glossary section. |
Takeaway: Structure is instruction — headers and a Don'ts list get obeyed, paragraphs get skimmed. |
|
|
|
Know someone fighting the same context problem?
Forward it. Refer 3 friends and we'll send you our private context-template pack.
Refer & get the template pack → |
|
|
|
|