メニュー
Implement a landing page in the current frontend stack using the established brief, strategy, and design tokens. Use when building or fixing the actual landing UI.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | landing-ui-build |
| description | Implement a landing page in the current frontend stack using the established brief, strategy, and design tokens. Use when building or fixing the actual landing UI. |
Build or repair the landing using the current frontend conventions. The implementation should stay grounded in run artifacts, not re-invent the brief in code.
briefs/landing_brief.jsondesign/tokens.jsondesign/layout-spec.jsoncontent/landing-copy.mdplans/build_status.jsonplans/build_status.json:
ui_status to implementedentry_filesClinic-safe frontend UI/UX audit, planning, and improvement workflow for this medical management app. Use when working on Admin, Doctor, Registrar, Cashier, Lab, dashboard, form, table, route-view, empty/loading/error, accessibility, responsive, visual consistency, or design-system tasks in the clinic frontend.
Project-specific master UI/UX skill for this clinic management frontend. Use for UI/UX audits, visual consistency, design-system convergence, role panels, dashboards, forms, tables, navigation, route views, empty/loading/error/forbidden states, accessibility, responsive behavior, browser visual QA, and safe frontend UI improvements across Admin, Doctor, Registrar, Cashier, Lab, Patient, queue, payment, EMR, and reporting workflows.
Security guidelines for writing secure code. Use when writing code, reviewing code for vulnerabilities, or asking about secure coding practices like 'check for SQL injection' or 'review security'. IMPORTANT: Always consult this skill when writing or reviewing any code that handles user input, authentication, file operations, database queries, network requests, cryptography, or infrastructure configuration (Terraform, Kubernetes, Docker, GitHub Actions) — even if the user doesn't explicitly mention security. Also use when users ask to 'review my code', 'check this for bugs', or 'is this safe'.
Create production-ready FastAPI projects with async patterns, dependency injection, and comprehensive error handling. Use when building new FastAPI applications or setting up backend API projects.
Project-specific workflow for designing or implementing BFF-lite screen/read-model endpoints inside the existing FastAPI backend after SSOT contract repair. Use for FastAPI UI endpoints, screen APIs, read-model services, Registrar workbench, Queue join, Queue board, Lab workbench, Admin audit/dashboard, Telegram admin dashboard, or questions about whether to add BFF-lite versus a separate BFF service.
Project-specific workflow for OpenAPI, API DTO, schema-shape, and frontend/backend contract review in this FastAPI + React clinic system. Use when adding or changing API endpoints, /api/v1/ui screen/read-model DTOs, generated OpenAPI shape, frontend API adapters, contract tests, or schema assertions.