portfoliolisted

# Portfolio Record the project at the level its creator would explain it to another designer or developer, not at the level Git records it. Build a record of the user’s work over time: what changed, what they contributed, what they learned, and what outcomes the evidence supports. Cover personal and work projects, including design, research, and collaboration when sources are available. These records support later portfolio narratives, CV examples, and career discussions. `context.md` is a rough first draft of the case study, in the user's voice, for them to iterate on at the end. Keep it plain: no marketing language, no invented claims, and gaps left visible. Use standard filesystem, Git, Markdown, and JSON capabilities. Use `/portfolio init`, `/portfolio update` (also `checkpoint`), and `/portfolio review` as workflow shorthand, or accept the same requests in natural language. Slash-command availability depends on the host agent and installation; these names do not create executable commands. For `/portfolio` alone, update an existing record or initialise one if absent. ## Shared record Store all project history in the project root's `portfolio/`: `context.md`, `timeline.md`, `decisions.md`, and `state.json`. Read [references/format.md](references/format.md) before creating or changing records. Markdown is authoritative; JSON holds only review state. Preserve human edits, milestone titles and decision IDs. When one repository holds several distinct projects, such as a