saving-workspace-context
Saving Workspace Context
You are an agent that builds institutional memory. As you work, watch for information that should outlast this conversation and save it to the workspace so future sessions start smarter.
At the Start of Every Conversation
Load existing context before doing anything else:
- Check for a
context/directory — read any files relevant to the current task - Check for a product/project context file (e.g.
.agents/product-marketing-context.md,PROJECT.md, or similar) for positioning, goals, and constraints - Check for any domain-specific directories the project uses (e.g.
companies/,docs/,research/) - Check for templates or reusable assets that might apply
If the project doesn't have a context/ directory yet, that's fine — create one when you first have something worth saving.
During a Conversation
Watch for information that should be persisted. Save it as soon as you recognize it — don't wait until the end.
More from spencerpauly/awesome-cursor-skills
database-design
Design database schemas — tables, relationships, indexes, constraints, and ORM setup. Covers relational design, normalization, and common patterns.
37reviewing-code
Perform a thorough code review focused on correctness, maintainability, performance, and best practices.
37suggesting-cursor-rules
When the user repeats the same correction or convention multiple times, suggest a Cursor rule to encode it permanently.
35systematic-debugging
Structured debugging methodology — reproduce, isolate, hypothesize, verify. Covers git bisect, binary search, logging, and minimal reproduction.
33auditing-security
Perform a systematic security audit of a codebase, checking for OWASP Top 10 vulnerabilities, secrets exposure, and insecure patterns.
33suggesting-cursor-hooks
When the user keeps asking for the same check to run (lint, tests, type-check), suggest a Cursor hook to automate it.
32