AGENT SKILL

ux-design-research

Researches external UI references for full-lane UI work. Use when full-lane work changes screens, components or a major redesign; not for non-UI or small interface changes.

License 许可
MIT
所属仓库
Eliyce/paqad-ai
最近更新
2026-11-13
Stars
★ 8
Forks
0

01 前言 Front Matter

name
ux-design-research
metadata
{ "cacheable": "false", "model_tier": "reasoning", "paqad-meta": "skill.meta.yaml", "output_format": "markdown" }
description
Researches external UI references for full-lane UI work. Use when full-lane work changes screens, components or a major redesign; not for non-UI or small interface changes.

02 资源文件 5

03 SKILL.md 正文

What It Does

Collects external and internal UI references for high-scope interface work, translating them into concrete guidance on flows, states, and interaction patterns rather than mood-board commentary.

Use This When

Only for full-lane work that also changes screens, components, or major redesigns. It should not activate for non-UI work or small graduated-lane interface adjustments.

Inputs

  • Read the request, current UI docs, and affected flow or screen inventory first.
  • Read references/research-capture-format.md before gathering examples so findings stay structured.
  • Read the stack-specific browser validation guide that matches the project surface.

Procedure

  1. Define the target interaction, user goal, and constraints before collecting references.
  2. Gather only sources that inform navigation, state handling, feedback, or visual hierarchy for the changed flow.
  3. Summarize each useful reference in terms of the concrete behavior it suggests, not just aesthetics.
  4. Translate findings into project-specific recommendations tied to states, flows, and validation needs.
  5. Call out any internal pattern conflict or accessibility concern revealed by the research.

Output Contract

  • Match assets/output.template.md: ## Research Targets, ## Reference Findings, ## Recommended Directions.
  • Every Reference Finding states Pattern and Why it matters here; never aesthetics-only.
  • Sources must be dated and quoted minimally: no long quotations.
  • Output must pass scripts/lint-output.sh (exit 0).

Escalate / Stop Conditions

  • Ask when the design goal or target user is too vague to choose meaningful references.
  • Warn when research points toward a pattern that conflicts with established product constraints or accessibility needs.
  • Do not present external inspiration as a mandate without mapping it to the project context.

Resources

  • references/research-capture-format.md
  • scripts/lint-output.sh
  • assets/output.template.md
  • runtime/capabilities/coding/stacks/laravel/references/tools/playwright.md
  • agents/openai.yaml

04 同仓库更多 Skills

Eliyce
Eliyce/paqad-ai

sample-skill

Sample bundled skill fixture

★ 8
Eliyce
Eliyce/paqad-ai

processing-invoices

Turns a supplier invoice into one ledger line. Use when a supplier invoice arrives and needs booking.

★ 8
Eliyce
Eliyce/paqad-ai

processing-invoices

Turns a supplier invoice into one ledger line. Use when a supplier invoice arrives and needs booking.

★ 8
Eliyce
Eliyce/paqad-ai

understand-idea

Chat and Claude Code: Step 1 of the discover journey: clarifies the goal, who benefits, success and constraints into the idea block. Use when the journey directs it to step 1, not directly.

★ 8
Eliyce
Eliyce/paqad-ai

size-work

Chat and Claude Code: Suggest a size for a ticket from comparable finished work, as a labelled suggestion the team still owns. Use it when someone asks "how big is this?", "roughly how much work is ABC-12?", or wants a backlog item sized. It finds the team's sizing scale at first use, picks two to five of the closest finished tickets with links, and gives a size or range with the drivers behind it and a confidence of low, medium or high, lowered and explained when the area's documents are template text. Every result is labelled a suggested size, never a date or a commitment. It writes nothing into the size field unless the user says "set it", and it refuses to overwrite an existing size unless the user asks to replace it. Produces the sizing block of the record.

★ 8
Eliyce
Eliyce/paqad-ai

refine-ticket

Chat and Claude Code: Improve one or more existing tracker tickets without losing the author's intent. Use it when someone wants a ticket read, diagnosed and tidied up ("this ticket is vague", "fix up ABC-12", "split this, it's too big"). It reads each ticket in full and snapshots it with its last-updated time, says what is wrong with evidence, and proposes a field-by-field before and after change set limited to summary, description, labels, parent, links and new child tickets on a split. It writes nothing until an explicit "apply it" bound to that exact change set, re-checks the ticket for conflicting edits just before writing, never replaces rich descriptions with plain text, never deletes or closes a ticket, and reads each ticket back after applying. Produces the existing and changes blocks of the record.

★ 8