git:20260623.8eda6ef to git:20260623.15e7503

19 added, 17 removed. Audit A to A.

---

name: remember

- description: "Record a UI convention or correction into memory — project-scoped or across all your projects. Invoke when the user asks for remember on their UI, or mentions 'remember' alongside design / UI / frontend work."

+ description: "Record a learned design constraint from a correction into the project brief. Invoke when the user asks for remember on their UI, or mentions 'remember' alongside design / UI / frontend work."

---

**Context:** this sub-skill is one lens of the broader `ui-craft` skill. If the `ui-craft` skill is also installed, read its SKILL.md first for Discovery + Anti-Slop + Craft Test, then apply the specific lens below.

- Load `references/memory.md` for the memory contract before proceeding.

+ Load `references/brief.md` (sections 6 + Self-Correction) before proceeding.

- ## Step 1: Capture the fact

+ ## Step 1: Capture the constraint

From the argument (or the immediately preceding correction in the conversation), capture:

- **What** changed or is preferred — the concrete rule.

- - **Why** — the reason. This is mandatory; without it the memory can't generalize. If the why isn't stated, ask one short question.

- - **Apply** — phrase it as an instruction a future build can follow without this conversation's context.

+ - **Why** — the reason. Mandatory; without it the constraint can't generalize. If it isn't stated, ask one short question.

+ - Phrase the rule so a future build can apply it without this conversation's context.

- ## Step 2: Choose the reach

+ ## Step 2: Write it to the brief

- - **User/global** (`~/.ui-craft/memory/`) if the user signals it applies everywhere: "in all my projects", "en todos mis proyectos", "siempre que trabajes conmigo", "as a rule for me". It's about the user's taste, not this brand.

- - **Project** (`.ui-craft/memory/`) if it's tied to this codebase/brand, or there's no cross-project signal — this is the default.

- - If it's clearly personal taste but the reach is ambiguous, ask once: "¿solo en este proyecto o en todos los tuyos?"

+ Append a dated entry to **section 6 (Learned constraints)** of `.ui-craft/brief.md`:

- ## Step 3: Write the atomic memory

+ ```markdown

+ - **YYYY-MM-DD** — <the rule>. *Why:* <reason>.

+ ```

- 1. Create the dated file in the chosen store: `<store>/YYYY-MM-DD-<slug>.md` with frontmatter (`id`, `type`, `scope`, `status: active`, `date`, `supersedes`, `tags`) + body (fact, **Why**, **Apply**) per `references/memory.md`.

- 2. If it contradicts an existing memory, set the old one's `status: superseded`, add its id to this entry's `supersedes`, and update the old INDEX line.

- 3. Add a one-line hook to that store's `INDEX.md` (id, hook, tags). Create `INDEX.md` (and `profile.md` for the project store) if absent.

+ Create the brief (run `/brief`) or the section 6 heading if absent. If the new constraint contradicts an existing principle or constraint, mark the old one deprecated with a dated reason (brief is append-mostly) rather than deleting it. Never store a rule that breaches the accessibility/correctness floor — record the closest compliant interpretation and say so.

- ## Step 4: Confirm

+ ## Step 3: Cross-project reach (optional)

- Report in one line where it landed and what it will change, e.g.:

- > Anotado en memoria de proyecto (`.ui-craft/memory/`): nunca gradientes en hero aquí.

+ If the user signals this should apply to **all** their projects ("in all my projects", "siempre que trabajes conmigo"), that's general memory, outside the brief's project scope:

+ - If an external memory service is available to the agent, mirror the constraint there so other projects inherit it.

+ - If not, record it in this brief and note that cross-project recall would need such a service.

- If the correction would breach the hard floor (a11y/correctness), do **not** store it as-is — store the closest compliant interpretation and say so.

+ ## Step 4: Confirm

+ Report in one line where it landed and what it changes, e.g.:

+ > Anotado en el brief (constraint aprendida): nunca gradientes en hero aquí.