project-memorylisted

# Project Memory Use this skill to set up and maintain concise repo-level memory for Codex sessions. It is generic for software projects and repositories; do not assume WordPress or any specific framework unless the project evidence supports it. ## Memory Files Maintain these files in the project root: - `AGENTS.md`: short practical instructions for future agents. - `docs/PROJECT_CONTEXT.md`: stable facts about the project, architecture, workflows, and constraints. - `docs/DECISIONS.md`: dated append-only technical or product decisions. - `docs/TASKS.md`: current tasks, blockers, and next actions. - `docs/CHANGELOG_WORK.md`: dated append-only work log for files, behavior, docs, config, dependencies, and tooling changes. Never store secrets, passwords, API keys, private tokens, credentials, database dumps, or sensitive personal data in project memory. ## Memory Quality Bar Project memory is guidance, not the source of truth. Keep only facts that are stable, meaningful, and likely to affect future implementation decisions. Do not record temporary task progress, obvious implementation details, one-off debugging notes, routine changes, raw command output, secrets, credentials, or private user data. When memory conflicts with a higher-authority source, follow the higher-authority source and update memory if the correction is durable. Authority order: 1. Current user instruction. 2. Current spec or task requirements. 3. Existing code and tests. 4. Project memory. 5. Gener