02 Project Memory
Initialize or refresh the project memory bank. Not for updating one memory file after it exists (use the learn skill) or editing a single rule (edit it directly).
Install
$ agentstack add skill-ai-driven-dev-framework-02-project-memory ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-ai-driven-dev-framework-02-project-memory) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Project Memory
Bootstraps the project's context layer: the AI context files with a memory block, the aidd_docs/ structure, and the memory bank.
Actions
| # | Action | Role | Input | | --- | ------------------- | --------------------------------------------------- | ----------------- | | 01 | init-context-file | Resolve the tools, then upsert the memory block | project root | | 02 | scaffold-docs | Create the aidd_docs/ structure | project root | | 03 | generate-memory | Detect the capabilities, generate the memory files | the memory dir | | 04 | review-memory | Review the memory files for consistency | the memory dir | | 05 | sync-memory | Fill the memory block in every context file | the context files |
Run the actions in order, 01 → 05, and run each action's ## Test before the next.
Transversal rules
- Capture the macro picture and the non-derivable: decisions, conventions, gotchas, the why. Never restate derivable detail (a full schema, a file tree). Prefer a pointer to the code over a copy.
- Keep each memory file small. Bullets stay short, code in backticks, no version number in a tech name (
React, notReact 19). - Memory files document the user's project, never AIDD's own scaffold.
- Reflect the current state only. Drop an unused section, no empty placeholder survives.
- Ask the user before including or excluding anything ambiguous. Never decide silently.
- Write files, never display their content.
Loading
The core concerns load always. The internal/ and external/ directories are listed for on-demand reading, never auto-loaded.
References
references/mapping-ai-context-file.md: the per-tool context-file path.references/capability-signals.md: the capabilities, their signals, and the concerns each gates.
Assets
assets/AGENTS.md: the context-file template.assets/README.md,assets/GUIDELINES.md,assets/CONTRIBUTING.md: theaidd_docs/doc templates.assets/templates/memory/: the memory templates, one folder per capability (corealways, the rest gated by signal).
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: ai-driven-dev
- Source: ai-driven-dev/framework
- License: MIT
- Homepage: https://www.ai-driven-dev.fr/
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.