Role

This skill owns module-level configuration, cache usage, backend menu integration, and module permission wiring. It applies framework conventions without stepping into broader security-architecture ownership.

When To Use

• Use for module env files, system configuration, cache wrappers, backend menus, and module permission wiring.
• Use for keywords such as env config, SystemConfig, cache, menu, backend permission, and module settings.
• Use when a business module needs operational configuration or caching behavior.

Source Material

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

Responsibilities

• Define module configuration in the expected env locations.
• Implement cache wrappers through framework factories instead of ad hoc storage code.
• Wire module backend menus and permissions consistently.
• Keep configuration, cache, and backend visibility changes scoped to the owning module.

Workflow

1. Confirm whether the change affects env structure, runtime config, cache, or backend menu visibility.
2. Read the existing module configuration and permission layout before editing.
3. Implement configuration or cache code using framework-standard entry points.
4. Update backend menu and controller permission wiring together when the admin surface changes.
5. Run env, setup, or backend validation commands as needed.
6. Verify behavior from the real backend or configuration path.
7. Record any required README or admin-usage notes.

Weline Rules

• Do not edit generated/ directly.
• Do not hardcode user-facing text.
• Use i18n for user-facing text.
• Use framework cache factories instead of direct driver construction.
• Update module README after fixing bugs or changing admin behavior.

Inputs Required

• The owning module and configuration or admin surface being changed.
• Desired cache behavior, env structure, or backend visibility outcome.
• Related controllers, menus, or config keys.
• Validation path for backend or runtime behavior.

Expected Output

• Updated module configuration, cache, or backend permission wiring.
• Validation evidence for the changed admin or runtime path.
• Documentation note when admin usage or config behavior changed.

Validation

• Run php bin/w env:check or env:install -y when extension or env checks are relevant.
• Run setup or route refresh commands when backend wiring changed.
• Verify backend menu visibility and controller access behavior.
• Verify cache read, write, and invalidation behavior through the intended module flow.

Constraints

• Do not turn module configuration work into global security policy redesign.
• Do not instantiate cache drivers directly.
• Do not leave backend menu visibility disconnected from permission annotations.
• Do not hide required operational setup steps from the module README.