design-memory

design-memory is a skill for Claude Code from Owl-Listener/designpowers. It costs 91 tokens per session (2,192 once invoked), scanned A, original, MIT.

A record of a designer’s past choices, such as styles, habits, and recurring preferences across projects. It is intended as an observation journal, not as instructions for future work.

In plain words
What is it for?
Use it at the beginning and end of design projects to observe and record decisions, styles, and working patterns.
Why use it?
It preserves useful context about how design decisions were made while keeping past preferences from silently directing a new project.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the designpowers plugin — 36 skills, 10 agents, 1 hook shipped together

Good fit Use it at the beginning and end of design projects to observe and record decisions, styles, and working patterns.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/owl-listener/designpowers/design-memory
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add Owl-Listener/designpowers --skill design-memory
Clone the repo
git clone --depth 1 https://github.com/Owl-Listener/designpowers

Made for: Claude Code.

Or install designpowers, the plugin that ships this one along with the rest of its 36 skills, 10 agents, 1 hook.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for design-memory

README.md
[![agentmods](https://agentmods.dev/badge/skills/owl-listener/designpowers/design-memory/github.svg)](https://agentmods.dev/skills/owl-listener/designpowers/design-memory)
Your own site
<a href="https://agentmods.dev/skills/owl-listener/designpowers/design-memory"><img src="https://agentmods.dev/badge/skills/owl-listener/designpowers/design-memory/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for design-memory

Your own site · 80×15
<a href="https://agentmods.dev/skills/owl-listener/designpowers/design-memory"><img src="https://agentmods.dev/badge/skills/owl-listener/designpowers/design-memory.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 91 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,192 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00091 $0.02192
Opus 5.5 $0.00036 $0.00877
Sonnet 5.5 $0.00018 $0.00438
Haiku 4.5 $0.00009 $0.00219

Measured 1mo ago against content hash d09bcc4ee549, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

design-memory scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/design-memory/SKILL.md · 162 lines

How it starts

The opening of the file, as written. The whole thing — 162 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Design Memory

Design memory is an observational record of how you design — the decisions you make, the styles you reach for, the habits and inclinations that show up across projects. It is a mirror, not a controller. It notices what you do and reflects it back to you out of curiosity. It does not steer future work.

The one rule that defines this skill

Design memory is descriptive, never prescriptive. It records what you did; it is not applied to drive new projects. The current project's direction comes from what you tell the team now (design-taste) and from any brand spec you provide (design-md / DESIGN.md) — never from this record. Observation that never feeds back into the work cannot mis-steer it, which is exactly why a record built across many different clients stays safe and honest: it's a journal, not a set of orders.

If you ever want to act on an observation, that's your call to make explicitly in the moment — the system will not quietly apply your past decisions to a new client's project.

Welcome Gate

BEFORE reading or updating design memory, check whether the Designpowers welcome sequence has been shown this session. If the user has not yet seen the welcome (the bird, the greeting, and the walkthrough offer), you MUST invoke the using-designpowers skill FIRST and complete the welcome sequence before returning here. The bird must appear before any work begins. No exceptions.

When to Use

  • At project completion — observe the project's decisions and add them to the record
  • When the user asks "how do I design?", "what are my habits?", "what's my style?" — produce the report
  • When the user makes a notably characteristic choice — note it as an observation
  • It is not loaded to constrain a new project. (Loading at project start is only to show the user their report if they want it, not to feed preferences into the pipeline.)

The Record (taste-profile.md)

Lives at ~/.designpowers/taste-profile.md (cross-project). It is a journal of observations about how the user works — not a rulebook. Every entry is phrased as something observed, with evidence, never as an instruction for future work.

Read the full file on GitHub · 162 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 1mo ago First seen · 162 lines · 91 tokens per session scan A d09bcc4ee549

Subscribe to this mod's changes

design-memory is a skill published in the GitHub repository Owl-Listener/designpowers (254 stars, last pushed 4mo ago), licensed MIT. It adds 91 tokens to every session and 2,192 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

semantix

Install and use the semantix memory kernel as a middleware in your agent: extract user preferences / workflows / experience from past sessions, retrieve and inject them on demand. One binary + your agent's own tools.

Gnosil/semantix · 47 tokens

anti-slop-frontend

A mechanical, countable anti-slop checklist for AI-generated frontend. Catches the specific signatures an undirected model defaults to: AI-purple glows, Inter-everywhere, em-dashes, div-based fake screenshots, eyebrow-on-every-section, beige+brass "premium" palettes, generic Jane Doe / Acme data. Advisory layer that…

BlackBeltTechnology/pi-agent-dashboard · 147 tokens

craft-studio

Router for the ArtCraft craft apps (PhotoCraft, VectorCraft, FilmCraft, LightCraft, PdfCraft, EffectCraft, DesignCraft, FigCraft, WordCraft, SoundCraft, DeckCraft, CADCraft, GridCraft) driven headless via pi-craft. Use to choose which app fits a job and run the discover-execute-save-verify loop - "which craft app…

BlackBeltTechnology/pi-agent-dashboard · 103 tokens

craft-brand-kit

Build a brand kit from a logo with ArtCraft apps - trace or take the vector logo, colour/mono variants, PNG/TIFF set, one-page brand sheet, PDF package; verified and resumable. Starts from the user's logo; generated concepts only on explicit request. Use for "make a brand kit from this logo", "export my logo in all…

BlackBeltTechnology/pi-agent-dashboard · 88 tokens

accessibility-a11y

Semantic HTML, keyboard navigation, focus states, ARIA labels, skip links, and WCAG contrast requirements. Use when ensuring accessibility compliance, implementing keyboard navigation, or adding screen reader support.

BlackBeltTechnology/pi-agent-dashboard · 44 tokens

anti-slop-image-direction

Opt-in, paid reference images for marketing or new-site work: plan one image per section, confirm count, backend and cost, generate with pi-nano-banana, then distill a written direction brief for the mockup loop. Images are direction, never source. Never for product UI. Triggers: "generate design references", "image…

BlackBeltTechnology/pi-agent-dashboard · 86 tokens