remember
starsforks
How to install remember?
educlopez/ui-craft/remember
$npx -y skills add educlopez/ui-craft --skill rememberRecord 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.
SKILL.md
| 1 | <!-- HARNESS MIRROR — do not edit here. Canonical source: skills/ or commands/. After editing source, copy into cli/assets/<harness>/ and repo-root harness mirrors. --> |
| 2 | |
| 3 | **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. |
| 4 | |
| 5 | Load `references/brief.md` (sections 6 + Self-Correction) before proceeding. |
| 6 | |
| 7 | ## Step 1: Capture the constraint |
| 8 | |
| 9 | From the argument (or the immediately preceding correction in the conversation), capture: |
| 10 | - **What** changed or is preferred — the concrete rule. |
| 11 | - **Why** — the reason. Mandatory; without it the constraint can't generalize. If it isn't stated, ask one short question. |
| 12 | - Phrase the rule so a future build can apply it without this conversation's context. |
| 13 | |
| 14 | ## Step 2: Write it to the brief |
| 15 | |
| 16 | Append a dated entry to **section 6 (Learned constraints)** of `.ui-craft/brief.md`: |
| 17 | |
| 18 | ```markdown |
| 19 | - **YYYY-MM-DD** — <the rule>. *Why:* <reason>. |
| 20 | ``` |
| 21 | |
| 22 | 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. |
| 23 | |
| 24 | ## Step 3: Cross-project reach (optional) |
| 25 | |
| 26 | 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: |
| 27 | - If an external memory service is available to the agent, mirror the constraint there so other projects inherit it. |
| 28 | - If not, record it in this brief and note that cross-project recall would need such a service. |
| 29 | |
| 30 | ## Step 4: Confirm |
| 31 | |
| 32 | Report in one line where it landed and what it changes, e.g.: |
| 33 | > Anotado en el brief (constraint aprendida): nunca gradientes en hero aquí. |
People who liked this also viewed
6 picksType
- web-design-guidelinesReview UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".SkillsJul 2026
- lark-slides飞书幻灯片：创建和编辑幻灯片。创建演示文稿、读取幻灯片内容、管理幻灯片页面（创建、删除、读取、局部替换）。当用户需要创建或编辑幻灯片、读取或修改单个页面时使用。当用户给出 doubao.com 的 /slides/ URL/token 时，也应直接使用本 skill，不要因为域名不是飞书而回退到 WebFetch；路由依据是 URL 路径模式和 token，而不是域名。不负责：云文档内容编辑（走 SkillsJul 2026
- design-taste-frontendTaste-Skill - gives your AI good taste. stops the AI from generating boring, generic slop SkillsJul 2026
- ui-ux-pro-maxUI/UX design intelligence for web and mobile. Searchable local database with 84 styles, 192 color palettes, 74 font pairings, 192 product types, 98 UX guidelines, 104 icon entries, 16 GSAP motion presSkillsJul 2026
- caveman-helpQuick-reference card for all caveman modes, skills, and commands. One-shot display, not a persistent mode. Trigger: /caveman-help, "caveman help", "what caveman commands", "how do I use caveman".SkillsJul 2026
- codebase-designShared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-nSkillsJul 2026
