메뉴
Add a NiceGUI admin page for an existing domain while keeping config and page routing separated and masking sensitive fields.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | add-admin-page |
| description | Add a NiceGUI admin page for an existing domain while keeping config and page routing separated and masking sensitive fields. |
| metadata | {"short-description":"Add admin page"} |
implement (approach options upstream conditional — required for sensitive fields or new admin auth surfaces)/test-domain {name} run (verify) → /security-review (self-review) if sensitive fields exposed/plan-feature from inside this skillBaseAdminPage instances — they inherit the design
system automatically (the base class renders via the component builders).admin.components builders (c.page_header,
c.card, c.stat_card, c.data_grid, c.confirm_dialog, …) — never raw
ui.card / ui.aggrid / ui.dialog for those shapes, and never hardcoded
color classes or inline grid heights (AST-guarded).@admin_error_boundary(...) + require_auth* as the first statement.components/, not an inline page helper.Read docs/ai/shared/skills/add-admin-page.md for detailed steps and code templates.
Refer to docs/ai/shared/admin-design-system.md for the component catalog + DO/DON'T,
and docs/ai/shared/project-dna.md §11 for the admin page DI pattern.
Inspect drift between code, shared workflow references, and Claude, Codex, or Antigravity harness assets after architecture or workflow changes.
This skill should be used when the user asks to "sync guidelines", "document inspection", "check skill updates", "update project-dna", "sync patterns", "verify code-document consistency", or after architecture changes to verify Skills/AGENTS.md/CLAUDE.md match the actual code.
Guide a feature from requirements interview through architecture analysis, security check, and task decomposition.
This skill should be used when the user asks to "plan feature", "design feature", or wants to plan and design a new feature before implementation.
Audit a domain or the full repository for architecture compliance using the shared architecture checklist and repository rules.
Review a pull request or local diff against the repository's shared Review Protocol (correctness, regression, stability, contract, architecture, security, governance).