← ClaudeAtlas

guidelines-loglisted

Keep a project's standing rules alive across sessions. When the user gives a new instruction, preference, best practice or correction that should apply from now on ("always do X", "never Y", "from now on", "remember this", "this is a rule", or confirms a non-obvious approach), record it in the same turn as a dated entry in docs/guidelines/GUIDELINES_LOG.md and, if it is a lasting rule, fold it into the project's main guidelines file; also read the newest entries before starting a UI or feature task. Also, when needed, enforce must-never-break rules with a script or hook, split bloated rule files, and audit rule files. Use at the start of work in any repo that has such a log, and whenever the user states a rule, convention or lesson learned, even in passing.
zohaibmushwani/agent-skills · ★ 0 · Web & Frontend · score 72
Install: claude install-skill zohaibmushwani/agent-skills
# guidelines-log Agents forget between sessions; a repository does not. Rules the user states once should be written where the next session will read them, in the same turn they were given, or they are lost. ## Setup (once per repo) If the repo has no log, create `docs/guidelines/GUIDELINES_LOG.md` and `docs/guidelines/GUIDELINES.md` from `templates/`, and add two lines to the repo's agent instructions file (`CLAUDE.md` / `AGENTS.md`): read the guidelines and the newest log entries before any UI or feature task; record new rules in the same turn. If the log already exists but the instructions file lacks those two lines, add them too (ask first if the file is shared or managed by others). ## When the user states a rule 1. Decide if it is **durable** (applies to all future work: "colours only through theme tokens") or **one-off** (this task only: "make this button blue"). One-off instructions are not logged. Also record a **confirmed non-obvious approach** ("yes, exactly like that"), not only corrections; skip things obvious from the code and temporary debugging notes. 2. Append an entry at the **top** of the log (newest first): `YYYY-MM-DD - <short title>`, the rule in one or two sentences, **Why** (the defect or preference behind it), **How to apply** (where it bites). 3. If durable, also fold it into the matching section of `GUIDELINES.md` (edit the section; do not append a duplicate). If it contradicts an existing rule, replace the old rule and say so in the log entry. 4