| # USER.md
|
|
|
| <!--
|
| Who you are and how your agent should work with you. Loaded every session — keep it small.
|
| The first four sections are YOURS: hand-written; the agent may suggest edits and applies one only after your explicit confirmation.
|
| The last section belongs to your agent: append-only, dated, confidence-tagged.
|
| Size and curation thresholds: see references/curation.md in the user-md skill.
|
| All examples below are fictional — replace everything with your own content.
|
| -->
|
|
|
| ## Who I am
|
|
|
| <!-- Identity facts: name, role, background, how to address you. Facts here, preferences below.
|
| Example:
|
| - Alex Rivera. Call me Alex.
|
| - Indie game developer; day job: backend engineer at a mid-size logistics company.
|
| - Based in Lisbon; works in English and Portuguese.
|
| -->
|
|
|
| ## How I work
|
|
|
| <!-- Preferences and style: communication, deliverable standards, review habits, default authorization boundaries.
|
| Example:
|
| - Conclusions first, details on request; anything long starts with a TL;DR.
|
| - Code deliverables need a runnable example, not just a diff.
|
| - Refactors are fine without asking; deleting files is not.
|
| -->
|
|
|
| ## Our relationship
|
|
|
| <!-- How you two collaborate: what to ask about vs. just do, how to deliver feedback.
|
| Example:
|
| - Disagree openly — never agree just to be nice.
|
| - Ask before touching anything under deploy/; everything else, act first and report after.
|
| - When I'm vague, ask one clarifying question, then proceed on your best guess.
|
| -->
|
|
|
| ## What I'm up to
|
|
|
| <!-- Current goals and active work. Explicit, revisable hypotheses — update as evidence changes, clear when done.
|
| Example:
|
| - Shipping the v0.3 demo of my roguelike by end of quarter.
|
| - Learning Rust on weekends; prefer Rust examples where reasonable.
|
| -->
|
|
|
| ## Learned by your agent
|
|
|
| <!-- Agent-curated lane. Append-only. Every entry: [date · source event] + rule + confidence tag.
|
| Promotion into the sections above requires repeated observation AND the user's explicit OK.
|
| Entry format, promotion rules, and overflow thresholds: references/curation.md.
|
| Example:
|
| - [2026-03-04 · code review session] Prefers conclusions before reasoning in long replies. [single observation — unverified]
|
| -->
|
|
|
| ---
|
|
|
| ## Changelog
|
|
|
| <!-- One line per notable change: date · what was edited / merged / promoted / sunk to user/*.md. -->
|
| |
