memoria-de-projeto

Maintains a portable Markdown project memory file preserving preferences, lessons, and conventions across sessions.

1|Updated Jul 7, 2026
One-click install
npx skills add https://github.com/codjeremias-cell/Orquestrador-fable --skill memoria-de-projeto-codjeremias-cell
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: memoria-de-projeto
Source: https://github.com/codjeremias-cell/Orquestrador-fable/tree/main/skills/memoria-de-projeto
Command: npx skills add https://github.com/codjeremias-cell/Orquestrador-fable --skill memoria-de-projeto-codjeremias-cell

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve? AI assistants do not remember previous conversations between sessions, forcing users to re-explain preferences, past decisions, and recurring conventions every time. This Skill solves that with a single portable Markdown file — the project memory — that the user keeps alongside the project and attaches at the start of each new session, so durable context accumulates session after session under full user control. ## Core Features & Use Cases - Three-phase workflow: Load the memory file at session start, capture new preferences, lessons, and conventions during the conversation, then consolidate and version the updated file at the end or on demand. - Strict content boundaries: A 7-day test separates durable facts (preferences, decisions, lessons) from ephemeral task progress, which is routed to a project-state file instead of polluting the memory. - Security-aware consolidation: Facts from untrusted content are recorded with their origin attached, imperative instructions are rejected in favor of declarative facts, and no secrets or credentials are ever stored. - Use Case: At the end of a working session where the user corrected a recurring mistake and set a new reporting convention, ask for a memory consolidation and receive an updated, versioned MEMORIA-PROJETO.md to reattach next session. ## Quick Start Use the memoria-de-projeto skill to consolidate what we learned in this session into the project memory file and prepare the handoff for next time.

Frequently Asked Questions about memoria-de-projeto

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I preserve context between Claude sessions?▼

Keep a portable Markdown memory file (MEMORIA-PROJETO.md) with your project and attach it at the start of each session. The assistant reads it first, captures new preferences and lessons during the conversation, and returns an updated, versioned file at the end.

What should go into a project memory file?▼

Record only durable facts: user preferences, decisions with their reasons, reusable lessons, and recurring conventions. Apply the 7-day test — if a fact will be stale within a week, such as task status or next steps, it belongs in a project-state file instead.

What is the difference between project memory and project state?▼

Project memory stores how the team works — durable preferences, decisions, and lessons that stay valid for weeks or months. Project state stores where tasks stand right now — status, pending items, and next steps — which ages quickly and lives in a separate state file.

Can a memory file store API keys or credentials?▼

No. The Skill explicitly forbids recording passwords, tokens, API keys, or personal data. Only the convention around them is recorded, such as noting that keys live in environment variables, never the values themselves.

How does the memory file stay safe from prompt injection?▼

Facts originating from untrusted content must carry their source, imperative instructions are rejected in favor of declarative facts, and sessions that processed untrusted material close with a review of everything added to memory.

When should I use a handoff file instead of compacting context?▼

Use a portable handoff file only when moving to another harness, directory, or person, or when branching a side task mid-phase. Within the same environment at a phase boundary, compacting the context is the default choice.