メニュー
UI pattern catalog for frontend, dashboard, landing page, SaaS, fintech, ecommerce, developer tools, admin, marketplace, healthcare, mobile web, forms, tables, onboarding, settings, and empty states. Use when choosing product-specific interface patterns.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | ui-pattern-library |
| description | UI pattern catalog for frontend, dashboard, landing page, SaaS, fintech, ecommerce, developer tools, admin, marketplace, healthcare, mobile web, forms, tables, onboarding, settings, and empty states. Use when choosing product-specific interface patterns. |
Katalog pola UI untuk membantu agent memilih arah desain yang terasa seperti produk nyata. Gunakan sebagai inspirasi arsitektur UI, bukan template siap copy.
Cocok untuk: CRM, ERP, internal tools, ops dashboard, RBAC admin.
Cocok untuk: API platform, CLI dashboard, logs, deployments, observability.
Cocok untuk: payments, invoice, wallet, subscription, accounting.
Cocok untuk: product catalog, cart, merchant admin, order management.
Cocok untuk: patient dashboard, appointment, medical records, habit tracking.
Cocok untuk: chat, copilots, generation tools, review assistants.
Cocok untuk: marketing site, launch page, product homepage.
Cocok untuk: analytics, metrics, monitoring, business intelligence.
Cocok untuk: signup, setup wizard, KYC, config.
Cocok untuk: account, team, billing, notification, API keys.
## Pattern Choice
**Domain:** ...
**Selected pattern:** ...
**Why:** ...
**Rejected patterns:** ...
**Backend states shaping UI:** ...
Framework-agnostic website security audit and authorized pentest methodology (OWASP, red-team attacker mindset, white-hat reporting). Use for web pentest, vulnerability assessment, attack-surface review, bug bounty prep, or security audit of any web stack.
Critical path identification, risk-adjusted effort sizing, complexity detection, and execution strategy selection. Use when scoping a task, deciding direct-vs-planned execution, breaking down large work, or assessing how many steps something really needs.
Multi-phase workflows, state machines, DAG task execution, checkpoint/resume, and saga patterns for complex multi-step or multi-session work. Use when a task spans 5+ steps, multiple files, multiple sessions, or has irreversible phases.
Understanding legacy and unfamiliar code, git blame/history analysis, dependency archaeology, and reconstructing intent behind existing code. Use when working in unfamiliar codebases, investigating "why was this written this way", or before changing code you didn't write.
Retry strategies, rollback protocols, circuit breakers for delegations, escalation chains, and failure budgets. Use when verification fails, a fix doesn't work, a sub-agent returns weak output, or you are stuck in a failure loop.
Production incident triage, rollback procedures, blast radius assessment, severity classification, and post-mortem templates. Use when production is down, a deploy broke something, users are impacted, or you need to stabilize before fixing root cause.