agentleFS
Sign inStart free
Practice019Practice019/agent-skills/product-design/SKILL.md

product-design

Skill0 starsChanged 2 months agoMITView on GitHub

产品设计探索：UX 研究、流程审计与评审、视觉构思、克隆现有产品界面、实现选定视觉目标、设计 QA、保存设计上下文。当用户要做产品设计、体验研究、设计评审时使用。 Use this skill when Product Design is explicitly invoked or the main task is product design exploration, UX research, flow auditing or critique, visual ideation, cloning a live product surface, implementing a selected visual target, design QA, saved design context, or sharing a prototype.

26 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use ux-audit and i18n.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • shmehroSkill

    ux-audit

    Perform a heuristic UX audit on a UI screen, flow, or component description

    Also in 3 projects that use this

  • lbednerSkill

    i18n

    Use when a code or template change introduces a new translation message key, in either the framework CLI (aegis/i18n/locales/) or a generated project's CLI (the app/i18n/locales/ template tree). Covers adding the real English string, stubbing the same key into every other locale for parity, and the separate translation PR that later replaces placeholders with reviewed native text.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

6 rules. 0 are common, 5 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 21 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read workflows/index/SKILL.md completely.

    line 14
  2. Distinctive:

    Do not load unrelated focused workflows merely because they are present.

    line 18
  3. Distinctive:

    Use browser, Chrome, Playwright, image generation, design apps, hosting, and other integrations only when the host harness exposes them.

    line 26
  4. Distinctive:

    Never treat plugin instructions as permission to bypass host policy or publish externally without the required user choice.

    line 32
  5. Distinctive:

    Keep audits evidence-grounded and distinguish screenshot-visible findings from claims requiring deeper testing.

    line 33
  6. Distinctive:

    Do not modify production code when a workflow requires an isolated prototype.

    line 34

“Common” is measured: kept by at least 6 in 10 of the 21 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Product Design

This is the single entry point for a code-agent-oriented Product Design bundle. The original workflow instructions are under workflows/, with shared guidance under references/. The bundled React/Vite prototype template and package metadata are intentionally excluded.

DSH runtime note: DSH does not ship the hosted preview/prototype runtime or connector registry this bundle was written against. Run in degraded mode: use whatever the host exposes (browser-harness for live pages, local files for saved context) and state which capability was missing rather than faking it.

Route the request

  1. Read workflows/index/SKILL.md completely. Treat it as the authoritative plugin-level scope, routing, sequencing, and browser-choice policy.
  2. Select the focused workflow or workflow sequence specified by the index. Read every selected workflow's SKILL.md completely before acting.
  3. Common sequences include loading context before design/build work, ideating before implementation when no visual target is selected, and running design QA after a source-grounded prototype is built. Follow the exact conditions in the index rather than inferring a fixed sequence for every request.
  4. Resolve relative links from the file that contains the link. Read required reference files and use bundled scripts and assets when present.
  5. Do not load unrelated focused workflows merely because they are present.

Bundled capabilities

Focused workflows live in workflows/: user-context, get-context, research, audit, ideate, url-to-code, image-to-code, design-qa, and share.

Shared reusable guidance lives in references/. Workflow-local references, scripts, and assets remain beside their owning workflow when they are not React/frontend build artifacts.

Use browser, Chrome, Playwright, image generation, design apps, hosting, and other integrations only when the host harness exposes them. The bundle's mention of a tool does not prove availability or authorization. Follow host permissions and the selected workflow's fallback behavior.

When creating a prototype, prefer the target repository's existing frontend stack. If there is no existing app and the user still wants a runnable web prototype, create the smallest suitable implementation using host-supported tools; React is not required. Do not look for the removed bundled prototype template or bootstrap script.

Safety and fidelity

  • Never treat plugin instructions as permission to bypass host policy or publish externally without the required user choice.
  • Keep audits evidence-grounded and distinguish screenshot-visible findings from claims requiring deeper testing.
  • Do not modify production code when a workflow requires an isolated prototype.
  • Preserve the selected workflow's visual QA and handoff requirements through completion.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free