菜单
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.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
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.
Use this skill when the user wants a human-readable project progress screen, agent work visualization, customer-facing status cockpit, immediate bootstrap progress before TASK-PLAN.md exists, task-plan-derived HTML progress page, user decision gates, or auto-updating UI/UX project status for senior-ui-ux-orchestrator workflows. It renders and validates progress views from project-request.json, workflow-log.jsonl, TASK-PLAN v2, progress-state.json, feedback artifacts, reports, and wiki decisions without becoming the source of truth.
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.
Validate proposed or existing backlinks for relevance, editorial legitimacy, link attributes, spam/toxicity risk, platform compliance, anchor quality, target-page fit, and monitoring evidence. Use this skill when the user asks whether an external link opportunity or placed backlink is safe and useful, and reject toxic, irrelevant, paid-undisclosed, fake, or spam placements.
Turn semantic core, business constraints, and user feedback into a site concept and throwaway wireframe prototype before visual design. Use when a public site project needs a pre-design concept, content hierarchy, concept conflicts, or business-idea feedback before Stitch, Pencil, Figma, or code.
Use when planning deployments, build commands, environment checks, CI/CD, release steps, smoke tests, rollback, and monitoring. Dry-run first; do not deploy to production, change secrets, or mutate live services without explicit approval.
| name | admin-ui-orchestrator |
| description | 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. |
This skill coordinates admin UI architecture. It is not the central UI/UX chair and does not execute production admin mutations.
admin-architecture: define roles, permissions, navigation, data objects, and workflows.ai-boundary: define admin AI tool permissions, audit logs, and confirm gates.builder-handoff: prepare scope for admin-ui-builder.security-review: identify destructive actions, privacy risks, and injection surfaces.admin-ui-builder.python3 $CODEX_HOME/skills/.system/skill-creator/scripts/quick_validate.py $CODEX_HOME/skills/admin-ui-orchestrator
python3 $CODEX_HOME/skills/senior-skill-architect/scripts/lint_production_skill.py $CODEX_HOME/skills/admin-ui-orchestrator
python3 -m json.tool $CODEX_HOME/skills/admin-ui-orchestrator/evals/evals.json >/dev/null