Agent Skills
› NeverSight/learn-skills.dev
› pvecloud-basic-admin
pvecloud-basic-admin
GitHub用于处理 pveCloud 基础管理历史文档与当前页面范围的冲突。当任务涉及旧版 basic-admin 笔记、阶段计划或前后端范围混淆时启用，强制以当前所有者文档为准，防止用历史记录覆盖现有配置。
Trigger Scenarios
任务明确提及 historical basic-admin foundation
存在旧阶段笔记与当前 admin 表面之间的漂移
涉及已移除或重新打开的管理页面
Install
npx skills add NeverSight/learn-skills.dev --skill pvecloud-basic-admin -g -y
SKILL.md
Frontmatter
{
"name": "pvecloud-basic-admin",
"description": "Use only when the task explicitly mentions the historical basic-admin foundation, basic-admin plan\/progress docs, or drift between old stage notes and the current admin surface. This helper forces current page scope back to owner docs instead of historical phase notes."
}
pveCloud Basic Admin
Purpose
This skill is a narrow historical-scope helper. It prevents old basic-admin notes from being treated as the current admin contract.
Project truth still lives in:
docs/admin/architecture.mddocs/admin/pages/README.mddocs/admin/routing-permissions.mddocs/server/api/docs/server/database/design.mdserver/migrations/docs/progress/- the task-relevant analysis or plan document that explicitly mentions basic-admin
Boundary
- Historical basic-admin progress, gap, or plan notes can explain why a scope changed.
- They do not override current owner docs, migrations, API docs, or config examples.
- Current admin page scope must come from
docs/admin/pages/README.md. - Current route and permission semantics must come from
docs/admin/routing-permissions.md. - Removed or not-yet-opened admin pages must not be recreated unless owner docs are updated first and the maintainer confirms reopening them.
When This Skill Applies
Use this helper only when the task explicitly touches the historical basic-admin stage, including:
- removed admin pages, reopened admin menus, or confusion between backend capability, historical phase notes, and current frontend page scope
- basic-admin gap, plan, or progress documents
Do not load this helper for unrelated current-stage work or ordinary admin implementation tasks. Historical progress can explain why a scope changed, but current contracts still live in the owner docs and machine contracts.
When this helper applies, read:
AGENTS.md.codex/skills/pvecloud-document-first/SKILL.mddocs/progress/MASTER.md- The task-mentioned basic-admin analysis, plan, or progress document
docs/admin/pages/README.mdwhen page scope mattersdocs/admin/routing-permissions.mdwhen route or permission scope matters- The relevant server or admin frontend architecture docs
Working Rules
- Keep backend and frontend scope separate in your head.
- Do not confuse "backend capability still exists" with "frontend page should still exist".
- Keep the admin frontend aligned with the current documented surface unless docs explicitly reopen it.
Verification Baseline
Backend work:
cd server
go test ./...
Admin frontend work:
cd admin
bun run build
Version History
- e0220ca Current 2026-07-05 23:35
