design-memory

Aggregate designer preferences into a continuous taste profile file.

234|55|Updated Mar 18, 2026
One-click install
npx skills add https://github.com/Owl-Listener/designpowers --skill design-memory
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-memory
Source: https://github.com/Owl-Listener/designpowers/tree/main/skills/design-memory
Command: npx skills add https://github.com/Owl-Listener/designpowers --skill design-memory

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Design memory captures and preserves a designer's recurring preferences and instincts across projects, so new work starts from a learned taste instead of repeating decisions.

Core Features & Use Cases

  • Aggregates preferences, patterns, and design convictions into a living taste profile that travels across projects.
  • Enables consistent decision-making at kickoff, during iterations, and at project completion by seeding agent guidance and reviews.
  • Supports a feedback loop where user overrides update the taste profile to evolve with experience.

Quick Start

Load or update your taste profile at the start of a project to ensure decisions reflect current preferences.

Frequently Asked Questions about design-memory

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I maintain design consistency across multiple projects?

To maintain design consistency across projects, you can aggregate recurring preferences and instincts into a continuous taste profile. This profile seeds initial decisions and influences agent recommendations, ensuring new work starts from learned design tastes instead of repeating past choices.

What is a design taste profile and how does it work?

A design taste profile is a living record of a designer's soft patterns, strong opinions, and anti-patterns. It works by storing these preferences in a markdown file, applying them at project kickoffs, and updating after corrections to evolve with user tastes.

How do I save and apply cross-project design preferences?

You save cross-project design preferences by loading and updating a taste profile at project starts. When you make corrections during iterations, the system updates the profile, allowing you to apply these evolving preferences to future project decisions.

Can I override design patterns for a specific project?

Yes, you can override design patterns for a specific project. The system supports per-project overrides alongside the global taste profile, allowing you to apply localized preferences while preserving your broader cross-project design instincts.

When should I update my design memory profile?

You should update your design memory profile at the start of a project to seed decisions and immediately after making corrections during iterations. This feedback loop ensures your taste profile evolves accurately with your current design instincts.