Skip to content
cccskills
FreePublished on GitHub

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.

The English summary is being prepared. Showing the original description.

educlopez/ui-craft
See how to install

Files included (1)

  • SKILL.md2.3 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

<!-- 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:

- **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).

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

adapt

Free

Responsive layout pass covering breakpoints, touch targets, safe areas, and fluid type. Use when the UI has layout or touch issues on mobile/tablet, when adding a new screen that hasn't been tested across viewports, or when the user says "make it responsive" / "fix mobile layout". Invoke when the user asks for adapt on their UI, or mentions 'adapt' alongside design / UI / frontend work.

The English summary is being prepared. Showing the original description.

educlopez/ui-craft390Updated Oct 14, 2026

animate

Free

Motion design pass — adds purposeful animations or removes excessive ones, respecting MOTION_INTENSITY and the project's animation stack. Use when the user asks to add animation, "make it feel smoother", fix janky transitions, or trim motion that's distracting. Invoke when the user asks for animate on their UI, or mentions 'animate' alongside design / UI / frontend work.

The English summary is being prepared. Showing the original description.

educlopez/ui-craft390Updated Oct 14, 2026

audit

Free

Technical UI audit — a11y, performance, responsive. Produces a prioritized findings table. Invoke when the user asks for audit on their UI, or mentions 'audit' alongside design / UI / frontend work.

The English summary is being prepared. Showing the original description.

educlopez/ui-craft390Updated Oct 14, 2026

bolder

Free

Amplify personality — raises layout variance and motion, strengthens typography and one signature detail, without slop. Use when the UI works but feels safe, flat, or "template-y", or when the user says "bolder", "more personality", "more creative", or "make it pop" (still professional). Invoke when the user asks for bolder on their UI, or mentions 'bolder' alongside design / UI / frontend work.

The English summary is being prepared. Showing the original description.

educlopez/ui-craft390Updated Oct 14, 2026

brief

Free

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.

The English summary is being prepared. Showing the original description.

educlopez/ui-craft390Updated Oct 14, 2026

clarify

Free

UX copy review across buttons, errors, empty states, and form hints — critiques by default, applies only on request. Use when copy feels vague, generic, or AI-sounding, or when the user says "fix the labels", "improve error messages", or "review the copy". Invoke when the user asks for clarify on their UI, or mentions 'clarify' alongside design / UI / frontend work.

The English summary is being prepared. Showing the original description.

educlopez/ui-craft390Updated Oct 14, 2026

See all skills by educlopez

Report a problem with this skill