sergekostenchuk/ui-ux-agent-skill-system

webapp-ui-skill

Build, refactor, audit, and validate dense web application UI.

ソースを見る

使い方

  1. インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
  2. 必要なツール、認証情報、対応環境を原文で確認します。
  3. 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/sergekostenchuk/ui-ux-agent-skill-system --skill webapp-ui-skill

開始前の確認

  • 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
  • スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
リポジトリの原文

見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。

Web App UI Skill

Use this specialist for product UI surfaces: dashboards, admin tools, internal workflows, CRM screens, settings, data tables, and state-heavy app screens.

Operating Modes

  • build: create or refactor app UI.
  • audit: review an existing app screen and produce a fix brief.
  • state-coverage: inspect loading, empty, error, disabled, focus, selected, submitting, and success states.
  • verify: run available local evidence checks and report gaps.

Required Workflow

  1. Read references/dashboard-patterns.md for product UI layout decisions.
  2. Read references/state-model.md before changing app flows or components.
  3. Use assets/state-matrix.template.md and assets/implementation-report.template.md when a stable output artifact is useful.
  4. Use ../../shared/privacy-policy.md before any external service or screenshot handling.
  5. Use ../../shared/visual-verification.md for material UI changes.
  6. If source files are available, run scripts/check_state_coverage.ts or report why it was skipped.
  7. If a URL is available, run scripts/visual_smoke_test.mjs or report why it was skipped.
  8. Return concise implementation notes with Ran, Skipped, Planned, and Manual.

Design Doctrine

  • Prioritize scanning, comparison, and repeated action over marketing composition.
  • Use compact headings, stable grids, predictable navigation, and explicit state handling.
  • Keep cards for repeated items, modals, and genuinely framed tools.
  • Do not add decorative hero sections, nested cards, one-note palettes, or viewport-scaled typography.
  • Buttons, controls, and tables must have stable dimensions and readable labels.

Tool Contracts

  • State coverage: node scripts/check_state_coverage.ts --root "$PROJECT_ROOT" --out reports/state-coverage.json.
  • Visual smoke: node scripts/visual_smoke_test.mjs --url "$URL" --out reports/visual-smoke.
  • Optional cloud generation is never default. It requires explicit approval and a data-transfer note.

Validation

bash
python3 $CODEX_SKILLS_DIR/.system/skill-creator/scripts/quick_validate.py $CODEX_SKILLS_DIR/webapp-ui-skill
python3 $CODEX_SKILLS_DIR/senior-skill-architect/scripts/lint_production_skill.py $CODEX_SKILLS_DIR/webapp-ui-skill

Output Shape

text
Surface:
Primary workflow:
State coverage:
Ran:
Skipped:
Manual findings:
Files changed or proposed:
Verification required:
Risks:

タスクに関連する項目

同じリポジトリから

関連する Skills

すべての Skills
sergekostenchuk
コミュニティ

admin-ui-builder

Use when admin/CMS/back-office screens need to be built or specified after admin-ui-orchestrator defines roles, permissions, workflows, and safety gates. Covers tables, forms, editors, moderation queues, dashboards, CRUD surfaces, and state coverage without production destructive actions.

導入数
1
GitHub Stars
32
更新日
9月13日
sergekostenchuk
コミュニティ

admin-ui-orchestrator

Use when a project needs admin/CMS/back-office UI architecture: roles, permissions, content workflows, AI assistant boundaries, audit logs, destructive-action confirmations, and builder handoff. Planning only; do not perform production admin actions or expose secrets.

導入数
1
GitHub Stars
32
更新日
9月13日
sergekostenchuk
コミュニティ

analytics-setup-architect

Use when a website or web app needs privacy-aware analytics architecture: GA4, Yandex Metrica, self-hosted analytics, consent, UTM, event taxonomy, funnels, dashboards, and launch verification. Do not mutate real analytics accounts or store credentials without explicit approval.

導入数
1
GitHub Stars
32
更新日
9月13日
sergekostenchuk
コミュニティ

figma-canvas-editor

Create and edit native Figma canvas objects with MCP when explicitly scoped. Use this skill when the user asks to add or change frames, sections, components, instances, auto layout, variables, styles, FigJam objects, connectors, Slides objects, or selected nodes in Figma, and when the task requires mutation evidence, rollback-aware scope, and design-system consistency.

導入数
1
GitHub Stars
32
更新日
9月13日