Context Writing Best Practices
Learn how to write context that AI assistants actually understand and use effectively.
Do's and Don'ts
Do
Be specific about your expertise: 'Expert in React, TypeScript, and Node.js with 5 years experience'
Don't
Be vague: 'I know programming'
Do
Include preferences: 'Prefer concise code with clear variable names'
Don't
Leave out communication style preferences
Do
Add goals: 'Currently learning Rust for systems programming'
Don't
Skip context about what you're working on
Do
Use specific instructions: 'Always include TypeScript types in code examples'
Don't
Use generic instructions: 'Help me with code'
Key Principles
- Use clear sections: Name, Bio, Expertise, Goals, AI Instructions
- Keep each section focused on a single aspect
- Use bullet points for lists of skills or preferences
- Order sections by importance to AI assistants
- Mention specific technologies, tools, and frameworks
- Include years of experience where relevant
- State clear preferences: 'prefer X over Y'
- Add context about your current projects
- Use clear, simple language that AI can parse
- Avoid jargon or abbreviations without explanation
- Include keywords that relate to your expertise
- Keep your context under 2000 words for best results
- Specify your preferred response style (concise vs detailed)
- Mention if you prefer code examples
- State any formatting preferences
- Include your experience level for better-tailored responses
Example Context
{
"name": "Jane Smith",
"title": "Senior Software Engineer",
"bio": "Full-stack developer with 8 years of experience building scalable web applications. Passionate about clean code and developer experience.",
"expertise": [
"TypeScript/JavaScript (8 years)",
"React & Next.js",
"Node.js & Express",
"PostgreSQL & Redis",
"AWS & Docker"
],
"communication_style": {
"tone": "Professional but friendly",
"preferences": [
"Concise responses with code examples",
"Explain the 'why' behind suggestions",
"Include relevant documentation links"
]
},
"goals": [
"Learning Rust for performance-critical services",
"Building a developer tools startup"
],
"ai_instructions": "Prioritize practical solutions over theoretical perfection. Use TypeScript for all JavaScript examples. Consider scalability in architectural suggestions."
}Why this works:
- • Clear structure with logical sections
- • Specific years of experience for each skill
- • Communication preferences that guide AI behavior
- • Current goals provide context for suggestions
- • Actionable AI instructions with clear preferences
How We Score Context Quality
25%
Completeness
Are all important fields filled?
25%
Specificity
How specific and detailed is the content?
20%
Actionability
Can AI use this to help you better?
15%
Clarity
Is the writing clear and parseable?
15%
Structure
Is the context well-organized?
Ready to improve your context?
Use our validator to check your context quality and get specific suggestions.