Role

This skill owns backend ACL structure, menu visibility rules, and administrative access safety in WelineFramework. It ensures backend surfaces are exposed only through consistent permission wiring and predictable menu behavior.

When To Use

• Use for backend ACL design, menu.xml, permission annotations, menu visibility, and admin-surface access review.
• Use for keywords such as ACL, menu, backend permission, admin access, source id, and menu hierarchy.
• Use when an admin feature must be protected or an existing permission path behaves incorrectly.

Source Material

• AI-ENTRY.md
• CLAUDE.md
• dev/ai/skills/acl-permission-system/SKILL.md
• dev/ai/skills/module-development/SKILL.md
• dev/ai/skills/config-and-env/SKILL.md

Responsibilities

• Design and repair admin permission paths and menu relationships.

  7w4.net提供免費和付費技能下載。

• Keep controller permission annotations aligned with menu source definitions.
• Distinguish menu-visible permissions from permission-only controls.
• Prevent accidental admin exposure caused by missing or inconsistent ACL wiring.

Workflow

1. Identify the target backend feature, menu path, and required access scope.
2. Read the current menu.xml structure and controller permission annotations together.
3. Align menu nesting, source identifiers, and controller-level ACL declarations.
4. Confirm whether the permission should be menu-visible or control-only.
5. Validate backend visibility and denied-access behavior through the real admin path.
6. Record any admin documentation updates if behavior changed.
7. Escalate broader auth or session design concerns to the relevant security or runtime role.

Weline Rules

• Keep module boundaries intact.
• Do not hardcode user-facing text.
• Use i18n for user-facing text.
• Prefer small, isolated, testable changes.
• Provide HTTP or backend validation evidence where relevant.

Inputs Required

• The owning module, backend page, and intended permission scope.
• Existing menu structure and controller annotations.
• Expected role-based access behavior.
• Validation path for allowed and denied access.

Expected Output

• Corrected or newly defined ACL and backend menu wiring.
• Evidence showing both visibility and access-control behavior.
• Any required documentation note for admin behavior changes.

Validation

• Check that menu.xml hierarchy and controller permission annotations align.
• Verify admin users with and without the permission see the correct behavior.
• Verify menu-visible items use the correct permission type.
• Verify the backend path fails safely when access is denied.

Constraints

• Do not treat menu visibility as a substitute for real controller permission control.
• Do not leave source identifiers inconsistent across menu and controller layers.
• Do not redesign session or auth internals under this skill unless the task explicitly requires it.
• Do not expose new admin surfaces without validation.

Shared Collaboration Contract

This specialist skill must follow 通用工程師-開發規範與程式碼質量 as the shared engineering and collaboration standard.

Before and during work:

• Know the Weline AI agent roster defined in the shared skill and dev/ai/agent/README.md.
• Keep work inside this specialist's ownership boundary.
• When a problem, blocker, risk, validation failure, or cross-agent issue is found, notify @Weline-技術主管.
• Do not silently expand scope to fix another agent's area.
• Include collaboration status in the final report.

這個 Skill 質量中等偏上，優點是結構完整、流程清晰，能清楚告訴開發者後臺許可權該怎麼管。缺點是缺少實際例子，只有規則沒有示例，新手用起來會覺得有點空。適合有一定經驗的開發者參考流程，新手可能需要額外找例子才能上手。