メニュー
Apply a combined UX design expert and NGO user evaluation lens to any UI component, screenshot, or interface description. Use when reviewing UI for usability, accessibility, and suitability for non-technical NGO users.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | design-review |
| description | Apply a combined UX design expert and NGO user evaluation lens to any UI component, screenshot, or interface description. Use when reviewing UI for usability, accessibility, and suitability for non-technical NGO users. |
Evaluate UI through two simultaneous lenses: professional UX design standards and the perspective of a non-technical NGO program manager. For Dalgo, you almost always need both perspectives since the platform serves non-technical NGO users.
Provide one or more of:
webapp_v2/components/dashboard/dashboard-list.tsx)Evaluate against Dalgo's design standards using checklist.md in this skill directory. Compare component usage, spacing, colors, and patterns against patterns.md.
Evaluate from the perspective of a non-technical NGO program manager:
Comprehension Test
Confidence Test
Daily Workflow Test
Trust Test
Independence Test
Jargon Alert
Structure your output as:
Summary of UX design findings with specific file references and line numbers. Priority: Critical / Important / Nice-to-Have
Summary of NGO user perspective findings. Priority: Blocks Adoption / Confuses Users / Could Be Simpler
Prioritized, actionable list combining both perspectives. Lead with items that are both design issues AND user experience issues.
Refer to patterns.md in this skill directory for established Dalgo UI patterns to compare against.
Generate, update, or review Dalgo user-facing documentation. Use when the user asks to document a feature, write a docs page, update existing docs, or after a PR ships to refresh affected docs.
Draft a new Dalgo release notes entry on dalgo_docs from the latest release tags of DDP_backend and webapp_v2. Use when the user asks to write, publish, or update release notes after a release ships.
Use when implementing a feature plan end-to-end across the Dalgo backend (DDP_backend, Django) and frontend (webapp_v2, Next.js). Triggers on "execute this plan", "implement this feature", "build this from the plan", working from a plan.md / tasks.md.
Use when the user wants to create a Linear issue from a feature plan document (plan.md) generated by /engineering/plan-feature or /engineering/ship-feature. Triggers on: "create linear issue from plan", "post this to linear", "make an issue for this plan", "communicate this plan on linear".
Transform messy ideas into structured PRDs that get stakeholder alignment before engineering starts building. Use when: write prd, product requirements, requirements document, feature spec.
Writing rules for plans, specs, research notes, and any user-facing explanation in Dalgo. Use whenever producing a plan.md, research.md, spec.md, or explaining a feature/decision to the user — so the reader (a non-technical NGO program manager, a first-time engineer on the codebase, or a busy reviewer skimming on a phone) can follow without backfilling jargon. Triggered by the planning, spec-writing, and design-handoff commands; also invoke directly when the user says "explain in simple language", "give me an example", or asks you to rewrite something more plainly.