ZAidBinAsifZAidBinAsif/flutter-ai-starter/.cursor/skills/save-context/SKILL.md

save-context

Skill0 starsChanged 5 months agoMITView on GitHub

Persist research and decisions to context/ across sessions

2 other projects use a version of this.

Adopted by

Most recently taken up by

eranw2000/multi-phase-skills-frameworktheir own version, first seen Oct 25, 2026
rustimacc/context-ledger-skillstheir own version, first seen Apr 15, 2026

Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
eranw2000/multi-phase-skills-framework★ 10same name
rustimacc/context-ledger-skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository26 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .cursor/rules/000-project.mdcCursor rule
- .cursor/rules/accessibility.mdcCursor rule
- .cursor/rules/api-integration.mdcCursor rule
- .cursor/rules/architecture.mdcCursor rule
- .cursor/rules/dart-style.mdcCursor rule
- .cursor/rules/design-system.mdcCursor rule
- .cursor/rules/flutter-ui.mdcCursor rule
- .cursor/rules/security.mdcCursor rule
- .cursor/rules/state-management.mdcCursor rule
- .cursor/rules/testing.mdcCursor rule
- doubt-reviewSkill
- fix-dependenciesSkill
- flutter-componentSkill
- flutter-implementSkill
- generate-mocksSkill
- grind-until-greenSkill
- implement-tddSkill
- monitor-terminalSkill
- plan-featureSkill
- repo-navigatorSkill
- review-codeSkill
- suggest-ruleSkill
- write-commitSkill
- write-readmeSkill

The file

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 4 are distinctive, and 4 are very specific to this project.

≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Very specific:
Read context/ — files relevant to the current task
line 12
Very specific:
Read context/project.md if it exists (project identity)
line 13
Very specific:
Read docs/DECISIONS.md for stack/architecture ADRs
line 14
Very specific:
Read docs/ARCHITECTURE.md when touching app structure
line 15
Distinctive:
Do ask permission: before new skills or rules
line 33
Distinctive:
Keep files scannable; date entries that accumulate
line 52
Distinctive:
Don't save trivial re-derivable facts
line 53
Distinctive:
Check existing files before creating duplicates
line 54

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.

Files

SKILL.md

Saving Workspace Context

Build institutional memory in this repo's paths only.

At session start

Read context/ — files relevant to the current task
Read context/project.md if it exists (project identity)
Read docs/DECISIONS.md for stack/architecture ADRs
Read docs/ARCHITECTURE.md when touching app structure

Where to save

Signal	Location
Stack / architecture decision	`docs/DECISIONS.md` (dated ADR)
Research, spikes, domain notes	`context/{topic-slug}.md` (dated entries)
Project identity (what/who/constraints)	`context/project.md`
New component catalog entry	`docs/DESIGN.md`
Repeatable workflow	New skill in `.cursor/skills/` (ask first)
Persistent code constraint	New rule in `.cursor/rules/` (ask first)

Link from context/ to ADRs — do not duplicate.

How to save

Don't ask permission for small context/ appends — mention what you saved
Do ask permission before new skills or rules
Append with dated entries (newest first); don't overwrite history

Context file format

# {Topic}

## {Date} — {Brief title}

{What was learned or decided}

End of session

Save anything painful to redo: research, discovered patterns, deferred decisions.

Rules

Keep files scannable; date entries that accumulate
Don't save trivial re-derivable facts
Check existing files before creating duplicates

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

It worked
Partly
It didn't

What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free