What Career Context supplies
- User-supplied roles, projects, education, and credentials.
- Stated goals, interests, and preferred direction.
- Proof links, constraints, and claims to avoid.
- A reusable file that can be inspected and corrected.
Documentation · workflow
How VitaeContext works
Keep career context in files you can inspect. Use one focused method for the task in front of you.
Core workflow
Context first. Task second.
VitaeContext gives an agent a stable starting point instead of rebuilding career history inside every conversation.
- 01
Gather trusted material
Start with CVs, profile text, project notes, links, exports, and other material you can inspect.
- 02
Create career context
Use the context skill to organize facts, stated goals, evidence, constraints, and claims to avoid in Markdown.
- 03
Retrieve only what is needed
Use a bounded summary, the file itself, or MCP to provide selected context to another agent or system.
- 04
Run the downstream task
Let the destination tool apply its own method while keeping claims grounded in the supplied context.
What the downstream system supplies
- The task-specific workflow.
- Platform or document constraints.
- The final output format and delivery surface.
- Review steps specific to that task.
A maintained input
How is Career Context different?
Career Context is the broad, inspectable source supplied before a task. It is not another public profile or a provider-specific memory feature.
Is Career Context private?
VitaeContext is a local CLI and readable Markdown skill package with no project backend collecting Career Context. You choose where the file lives and what to supply to an agent. After you share content with an external provider, that provider's data rules apply.
Does VitaeContext verify claims?
No. It organizes user-supplied facts, stated goals, proof references, and claims to avoid. Its skills tell agents to preserve those boundaries and flag missing evidence, but generated work can still contain errors and requires human review.
Downstream prompt
Give the context and name the task.
The destination agent supplies the task method. VitaeContext supplies the factual starting point.
Use my Career Context file at
~/.vitaecontext/name-surname-career-context.md
as the source of truth for this application.
Tailor the draft to the role, but do not add claims
that are unsupported or marked as needing evidence.Option A: Bounded summary
Run npx vitaecontext context summary <file> --for <task> to create a compact Markdown packet for the current workflow. This works well for manual chats and direct handoffs.
Option B: Cross-workspace MCP
Configure the stateless MCP server (npx -y vitaecontext mcp). Your AI coding assistants across all project repositories can query your private context and VitaeGraph dynamically without copying files.