Less repetition
You do not need to explain your education, projects, links, and goals in every new conversation.
A concrete example
What goes inside a career context file?
A short, fictional example you can inspect before creating your own.
The idea
Give the agent facts it can reuse.
The file is a private, editable record of your professional context. It tells an agent what is verified, what you want to do next, and which claims it should avoid. You update the file when something changes and reuse it across tasks.
Fewer invented details
Evidence boundaries and claims to avoid give the agent clear limits before it starts writing.
More consistent work
Your CV, profiles, portfolio, and application drafts can all start from the same maintained facts.
Sample file
A useful file can stay simple.
This fictional example is deliberately short. A real file can contain more roles, projects, education, links, and proof, but the structure remains readable Markdown.
- Quick reference gives the agent the facts it needs most often.
- Goals describe direction without pretending it is completed experience.
- Roles and projects connect claims to concrete work.
- Output preferences define tone and safety rules.
Keep your completed file private. The example below is fictional and contains no real personal data.
# Alex Morgan — Backend developer focused on reliable web services
## QUICK REFERENCE
```yaml
name: Alex Morgan
current_location: Bologna, Italy
target_roles:
- Backend Developer
- Platform Engineer
work_mode: remote or hybrid
positioning_summary: "Backend developer with experience building APIs,
internal tools, and observable web services."
current_focus: reliable services and developer tooling
growth_direction: platform engineering
claims_to_avoid:
- senior-level ownership
- people management
top_skills:
- TypeScript
- Node.js
- PostgreSQL
- Docker
- REST APIs
github: https://github.com/alexmorgan
portfolio: https://alexmorgan.dev
```
## GOALS AND TARGETING
**Ideal role:** Backend or platform engineer on a product team.
**Want to work on next:** service reliability, internal platforms, and CI/CD.
**Evidence boundary:** Production API work is verified. Platform engineering
is a direction supported by personal projects, not a past job title.
## [ROLE] Backend Developer Intern | Northstar Labs | Mar–Sep 2025
Built and maintained Node.js API endpoints for an internal operations tool.
- Added request validation and integration tests to three existing endpoints.
- Reduced a recurring report from a manual spreadsheet process to one API call.
- Worked with TypeScript, PostgreSQL, Docker, and GitHub Actions.
## [PROJECT] QueueWatch
Repository: https://github.com/alexmorgan/queuewatch
A small dashboard for inspecting background-job failures.
- Built with TypeScript, Fastify, PostgreSQL, and OpenTelemetry.
- Includes setup instructions, architecture notes, and a local Docker stack.
- Do not describe it as production software; it is a maintained personal project.
## EDUCATION
**BSc Computer Science | University of Bologna | 2025**
Relevant coursework: databases, distributed systems, software engineering.
## OUTPUT PREFERENCES
- Use plain language and short sentences.
- Prefer specific examples over broad claims.
- Ask before adding a metric that is not written in this file.
- Keep goals separate from completed experience.
<!-- This is a fictional, shortened example. Replace every value with your own
verified information and keep the completed file private. -->Use it in a normal prompt
The file supplies context. Your prompt supplies the task.
Use the attached personal career context file.
Use the agentkit-seo-github skill to review my GitHub profile.
Tell me what to change first and do not add claims that are not in the file.The same pattern works for a CV, LinkedIn profile, portfolio, application answer, interview preparation, or any other task that needs your professional background.