Skip to content
Skills Library
Design & UX · Writing

remember

/remember

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.

Repository
ui-craft ↗
Licence
MIT
Last repository change
19.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
1
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 19.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What to check before installing
  • SKILL.md zawiera komentarze HTML (1). Nie widać ich w podglądzie Markdown, a model je czyta.

What it does and when to use it

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.

Triggers from the description

remember
Original author 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.

How it works

  1. Step 1: Capture the constraint
  2. Step 2: Write it to the brief
  3. Step 3: Cross-project reach (optional)
  4. Step 4: Confirm
Original SKILL.md headings · 37 lines, 334 words
SKILL.md preview
---
name: remember
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."
---

<!-- HARNESS MIRROR — do not edit here. Canonical source: skills/ or commands/. After editing source, copy into cli/assets/<harness>/ and repo-root harness mirrors. -->

**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/brief.md` (sections 6 + Self-Correction) before proceeding.

## 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. 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: Write it to the brief

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

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

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 3: Cross-project reach (optional)

If the user signals this should apply to **all** their projects ("in all my projects", "whenever you work with me"), 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.

## Step 4: Confirm

Report in one line where it landed and what it changes, e.g.:
> Recorded in the brief (learned constraint): never gradients on a hero here.

**Next step:** Keep working. The constraint now lives in the brief, so every future session reads it (rung 2).

Versions

RepositoryScoreLicence
This page · educlopez/ui-craft100MIT
yonatangross/orchestkit100MIT
langchain-ai/deepagents100MIT
zereight/gitlab-mcp100MIT
stxrmik/antigravity-plus100MIT
rohitg00/agentmemory100Apache-2.0
eleboucher/memini100AGPL-3.0
ffMathy/hey-jarvis100MIT
alirezarezvani/claude-skills100MIT

Identical content appears in 6 other GitHub folders. We show one copy with the highest score.

Database snapshot: 13.11.2026 · package version cd15bc1972c4 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100tokens
    Audit or establish the project's 3-layer token spine. Invoke when the user asks for tokens on their UI, or mentions 'tokens' alongside design / UI / frontend work.
  • 100brief
    Write or update the project's durable design brief at .ui-craft/brief.md. Invoke when the user asks for brief on their UI, or mentions 'brief' alongside design / UI / frontend work.
  • 100traceary-memory-remember
    Use ONLY when the user explicitly asks to remember a specific durable fact, decision, constraint, or preference. Trigger phrases — "覚えておいて", "remember that", "for the record", "save this as", "記憶しておいて", "メモして". Do NOT use for generic notes, status updates, or session summaries.…
  • 100design-context
    Use when writing or updating PRODUCT.md or DESIGN.md, or when design-ui needs product or visual context that does not exist yet.
  • 100learned
    Extract and persist learnings, corrections, and patterns from the current session to memory. Invoke immediately after any user correction or rejected suggestion, after validation of a non-obvious choice, when the user says "remember this" / "catat ini", when a new preference,…
  • 100mnemon-remember
    Distil the current conversation into durable memory. Use when the user says remember this, keep this, don't forget, from now on, or asks you to save what was just decided — and after a turn that produced a decision, a preference, a measurement or a correction worth keeping.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.