菜单
SIKESRA admin UI/UX workflows. Use when building or reviewing SIKESRA admin pages, route safety, registry wizard, verification queues, access screens, audit screens, Kumo components, privacy states, accessibility, i18n, or UI tests.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | sikesra-admin-ui-workflows |
| description | SIKESRA admin UI/UX workflows. Use when building or reviewing SIKESRA admin pages, route safety, registry wizard, verification queues, access screens, audit screens, Kumo components, privacy states, accessibility, i18n, or UI tests. |
Use this skill for SIKESRA admin UI, UX flows, React components, route safety, accessibility, privacy states, page contracts, and UI tests.
Read these before changing SIKESRA admin UI:
awcmsmicro-dev/packages/plugins/awcms-micro-sikesra/docs/UI_UX_DESIGN_STANDARD.md.awcmsmicro-dev/packages/plugins/awcms-micro-sikesra/docs/TECHNICAL_PRD.md.awcmsmicro-dev/packages/plugins/awcms-micro-sikesra/docs/IMPLEMENTATION_GOVERNANCE.md.awcmsmicro-dev/packages/plugins/awcms-micro-sikesra/docs/MERMAID_DIAGRAMS.md.awcmsmicro-dev/AGENTS.md for Kumo, Lingui, RTL-safe Tailwind, and testing rules..opencode/skills/frontend-ui-ux/SKILL.md for general frontend guardrails./_emdash/admin/plugins/awcms-micro-sikesra/.All pages should fit this journey:
Configure -> Input or Import -> Validate -> Verify -> Publish Aggregate -> Report or Export -> Audit or Govern
Every page should define the relevant part of that journey and show where the operator is in the flow.
Prefer this structure unless the page has no matching workflow need:
Page header
Purpose description
Primary action area
Filters or search
Status summary
Main content table, card, or form
Context panel or detail drawer
Audit or status footer
Empty, loading, and error states
Use SIKESRA_PAGE_PATTERN_CONTRACTS in src/admin/ui-standards.ts when page contracts exist or must be extended.
Represent sensitive data as state without exposing the value. Use stable labels such as:
Masked
Sensitive
Restricted
Public Safe
Suppressed
Needs Review
Permission Denied
ABAC Denied
Audit Required
Public aggregate UI must explain suppression and small-cell protection.
en) and Indonesian (id) plugin PO catalogs aligned for changed user-facing copy.SIKESRA_ACCESSIBILITY_CHECKLIST where tests can enforce it.pnpm --filter @awcms-micro/plugin-sikesra typecheckpnpm --filter @awcms-micro/plugin-sikesra testpnpm --filter @awcms-micro/plugin-sikesra awcms:sikesra:check-routespnpm --filter @awcms-micro/plugin-sikesra awcms:sikesra:check-admin-pagesbash scripts/validate-awcmsmicro-boundaries.shUse when updating `docs/prd`, adding or revising Mermaid diagrams, synchronizing AI-ready issue docs/templates, or aligning `README.md`, `AGENTS.md`, and root docs with the latest active Satu Sehat Kobar PRD package and MVP scope.
Implement Satu Sehat Kobar end-to-end/UAT tests, the consolidated UAT/demo seed (17 roles + full sample flow), and the deployment + smoke + rollback runbook. Use for EPIC-16 issues.
Implement Satu Sehat Kobar backend & integration foundations — inter-plugin service contracts (SC-01..11), cross-plugin domain events / cache invalidation, notification channel abstraction, external integration adapter boundary, shared API middleware, observability, and migration ordering. Use for EPIC-14 issues.
Implement Satu Sehat Kobar master-data foundation — official/local region, health facilities, organization units, document numbering, signatories, holidays, transport, and personnel (employees/positions/supervisors). Use for EPIC-13 issues (addenda doc 21/22/23).
Implement the Satu Sehat Kobar duty-travel approval engine — DB-configured multi-step chain, finance auto-skip, finance ABAC scope, in-app notifications, return/reject, and the approver queue. Use for EPIC-04 issues.
Implement the Satu Sehat Kobar dashboard aggregate endpoint with KV caching and the 12-indicator SPM tracker. Use for EPIC-08 issues (satusehat-dashboard / spm-health).