@aiweline

core-command-codegen covers framework-safe cli command creation, code generation standards, and php 8.4 compatibility within weline conventions. emphasizes thin entry points, service layer separation, and windows command quoting discipline.

tech-lead-task-scheduling decomposes broad requests into bounded work packages with explicit ownership, dependencies, and validation gates, routing each to specialist skills within weline framework constraints.

unit-test-coverage guides focused regression testing for weline framework services, models, and helpers via phpunit or pest, emphasizing isolated test boundaries and behavior-driven assertions over brittle snapshots.

frontend-i18n-notification handles user-facing copy placement, translation wiring, and framework-safe notification patterns in view layers. covers text hardcoding prevention, attribute-safe i18n expressions, and browser dialog replacement with framework components.

e2e-ui executes lightweight route and ui smoke validation to confirm reachability and basic rendering after code changes, using http requests or minimal browser paths proportional to the change scope.

qa-quality-gate enforces multi-layer test validation at release boundaries, reviewing evidence against changed scope and issuing gate-by-gate acceptance decisions with residual risk tracking for technical leadership sign-off.

e2e-route-ui-smoke validates route registration and basic ui reachability through lightweight http and browser checks, catching wiring and rendering regressions before deeper acceptance work begins.

tech-lead-acceptance-progress handles first-line acceptance of specialist work by comparing implementation against plan, validating evidence quality, and tracking gaps before handoff to technical director review.

business-module-development covers bounded feature work within weline framework modules, including controllers, menus, setup flows, and route registration. focuses on module ownership and validated changes without framework internals coupling.

e2e-flow-test covers playwright-based browser automation for multi-step user journeys and cross-page interactions. focuses on narrowly-scoped regression validation tied to actual changed behavior rather than unit-testable fragments.

ci covers shell command safety and environment portability for windows, powershell, and php contexts. defines workflow for preventing quoting bugs and argument drift across ci automation paths.

ci-env-command-safety addresses shell quoting, windows portability, and php compatibility risks in ci automation. covers command composition safety and cross-environment execution validation.

common-development-standards establishes baseline engineering practices for weline framework work: change isolation, code quality, documentation duties, validation evidence, and cross-agent collaboration. provides workflow, rules, escalation protocol, and agent roster but lacks concrete, numbered procedural steps for typical development scenarios.

security-acl-admin handles backend permission wiring, menu visibility alignment, and admin access control within welineframework. covers acl design, menu.xml structure, and permission annotation consistency to prevent unintended admin exposure.

wls-wls handles WLS process lifecycle decisions including reload versus restart, worker stability, and process cleanup. requires lifecycle-aware diagnosis and dedicated test instance validation before changes.

core-routing-extension covers framework routing, event contracts, hooks, and extends-point design for weline. establishes env-driven registration patterns and extension-point stability across module integration.

docs-skill-index manages skill catalogs, routing references, and migration mappings for ai-facing documentation. covers repository reorganization, discoverability preservation, and validation of knowledge structure after refactors.

wls-process-stability covers worker lifecycle decisions, reload versus restart tradeoffs, and runtime-safe process control for long-lived wls environments. includes test isolation rules and lifecycle-aware diagnostics.

security-session-data covers session isolation, state leakage prevention, and sensitive data protection boundaries within a framework-driven workflow. it enforces area separation and requires validation across login/logout flows.

qa-test-strategy governs test layer selection, risk-based validation depth, and cross-role quality gates for delivery items. covers planning, coverage classification, and acceptance evidence definition across unit, http, e2e, and runtime checks.

business-config-cache-acl covers module-level configuration, cache integration, backend menu wiring, and permission scoping. workflow-driven but lacks concrete step validation and error handling specifics.

frontend-component-pagebuilder covers blocks, taglibs, widgets, and pagebuilder templates within the weline framework. workflow is documented but lacks actionable depth on registration paths, error handling, and specific component patterns.

Security engineer skill for backend ACL structure, menu visibility control, and administrative access safety.

CI release engineer skill for validation gating, release-readiness checks, and automation-safe delivery criteria.

E2E automation engineer skill for Playwright-driven flow validation, browser interaction coverage, and end-to-end regression checks.

QA lead skill for test strategy, coverage planning, risk-based validation design, and cross-role quality governance.

WLS runtime engineer skill for session isolation, Session Server behavior, and cooperative SSE runtime implementation.

CI release engineer skill for validation gating, release-readiness checks, and automation-safe delivery criteria.

Business module engineer skill for service-layer design, business logic extraction, and module-safe orchestration.

Frontend theme engineer skill for theme structure, source-template editing, layout-safe styling, and Weline view-layer conventions.

Unit test engineer skill for stable fixtures, edge-case data design, and regression-oriented test inputs in WelineFramework.

Documentation engineer skill for module docs, README updates, architecture notes, API change records, and repository-safe documentation placement.

Framework core engineer skill for ORM conventions, schema annotations, query patterns, and cross-module data access contracts.

Framework core engineer skill for low-level WelineFramework implementation and architectural guardrail compliance.

Shared engineering skill for i18n-compliant user text, translation files, and framework-safe user notification patterns.