design-system-review

星标0

分支0

更新时间2026年6月20日 17:10

Review Ultra RSS Reader UI changes for design-system compliance, reusable component routing, token usage, and interaction consistency.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

来源

jey3dayo

jey3dayo/ultra-rss-reader

打开 GitHub 仓库查看创作者相关仓库

下载

Design System Review

Use this skill after UI or component changes in Ultra RSS Reader.

Review Inputs

Read AGENTS.md, CLAUDE.md, DESIGN.md, and DESIGN_REVIEW.md.
Inspect the diff for files under src/design-system, src/components, src/styles, Storybook canvases, and UI tests.
Treat src/design-system/index.ts as the public component-library API.

Checklist

Public UI imports in feature, app, Storybook, and test code go through @/design-system.
src/components/ui and src/components/shared stay implementation owners for primitives and shared building blocks.
Repeated controls, rows, chips, shell surfaces, toolbar actions, empty states, and progress/status patterns use design-system exports instead of feature-local clones.
New colors, radius choices, shadows, motion timings, and semantic state styles use src/styles/global.css tokens or documented exception palettes.
Button, utility action, form row, shell, dialog, list, and navigation behavior follows DESIGN.md.
Keyboard focus, aria-* state, disabled behavior, tooltips, and loading/status labels stay intact after refactors.
Storybook UI Reference canvases continue to represent the shared components rather than feature-only copies.

Verification

Run the narrowest relevant checks first, then the repository gate before completion:

mise run test:unit:dom
mise run test:e2e
mise run check

For browser-visible changes, also run mise run app:dev:browser and exercise the reader, settings modal, command palette, and subscriptions workspace with click and keyboard flows.

Report Format

総合判定: OK | 調整推奨 | 大幅修正推奨

- Design-system routing: OK | 要修正
- Token usage: OK | 要修正
- Component reuse: OK | 要修正
- Interaction/a11y: OK | 要修正
- Storybook/tests: OK | 要修正

優先修正:
1. ...
2. ...
3. ...

同仓库更多 Skills

同仓库

tauri

jey3dayo/ultra-rss-reader

Tauri commands, permissions, capabilities, security config, path handling, cross-platform file ops, and native filesystem APIs. Use when mentioning Tauri, desktop apps, Rust commands, invoke, capabilities, permissions, ResourceId, file paths, or platform differences.

2026-07-160

tauri-icon-gen

jey3dayo/ultra-rss-reader

Use when an existing app image should be converted into Tauri-ready icons, including transparency cleanup, square source normalization, and `pnpm tauri icon` generation. Do not use for skill directory moves, path fixes, distribution, or marketplace packaging even if the path contains `tauri-icon-gen`; use `skill-creator` instead.

2026-07-090

tauri-webview-geometry

jey3dayo/ultra-rss-reader

Use when implementing, refactoring, or debugging a Tauri child webview (WebviewBuilder / add_child) embedded in a DOM UI — before writing overlay open/close/resize/bounds code — or when the native surface looks shifted, clipped, or too small, stays open after close, closes or fires twice, applies stale bounds after rapid resize or URL change, hangs the UI when a native command stalls, or when logical vs physical pixels are being mixed.

2026-07-090

release

jey3dayo/ultra-rss-reader

Use when cutting an Ultra RSS Reader release from `main`, choosing a semver bump, syncing versions across `package.json`, `src-tauri/Cargo.toml`, and `src-tauri/tauri.conf.json`, generating `CHANGELOG.md` and GitHub Release notes from commit history, tagging `v*`, pushing safely, and verifying the draft GitHub Release workflow.

2026-06-290

name	design-system-review
description	Review Ultra RSS Reader UI changes for design-system compliance, reusable component routing, token usage, and interaction consistency.

Design System Review

Use this skill after UI or component changes in Ultra RSS Reader.

Review Inputs

Read AGENTS.md, CLAUDE.md, DESIGN.md, and DESIGN_REVIEW.md.
Inspect the diff for files under src/design-system, src/components, src/styles, Storybook canvases, and UI tests.
Treat src/design-system/index.ts as the public component-library API.

Checklist

Public UI imports in feature, app, Storybook, and test code go through @/design-system.
src/components/ui and src/components/shared stay implementation owners for primitives and shared building blocks.
Repeated controls, rows, chips, shell surfaces, toolbar actions, empty states, and progress/status patterns use design-system exports instead of feature-local clones.
New colors, radius choices, shadows, motion timings, and semantic state styles use src/styles/global.css tokens or documented exception palettes.
Button, utility action, form row, shell, dialog, list, and navigation behavior follows DESIGN.md.
Keyboard focus, aria-* state, disabled behavior, tooltips, and loading/status labels stay intact after refactors.
Storybook UI Reference canvases continue to represent the shared components rather than feature-only copies.

Verification

Run the narrowest relevant checks first, then the repository gate before completion:

mise run test:unit:dom
mise run test:e2e
mise run check

For browser-visible changes, also run mise run app:dev:browser and exercise the reader, settings modal, command palette, and subscriptions workspace with click and keyboard flows.

Report Format

総合判定: OK | 調整推奨 | 大幅修正推奨

- Design-system routing: OK | 要修正
- Token usage: OK | 要修正
- Component reuse: OK | 要修正
- Interaction/a11y: OK | 要修正
- Storybook/tests: OK | 要修正

優先修正:
1. ...
2. ...
3. ...