\r \r

Role\r

\r This skill owns framework-safe command creation, code generation quality, and PHP compatibility rules for generated or scaffolded code. It keeps command entry points thin and ensures generated code follows Weline conventions instead of generic PHP habits.\r \r

When To Use\r

\r

• Use for CLI commands, console registration, scaffolding, code templates, or repository-wide code-generation rules.\r
• Use for keywords such as command, console, generator, scaffold, command:upgrade, strict typing, PHP 8.4, and Windows command composition.\r
• Use when implementation work introduces new command-line entry points or reusable code templates.\r \r

Source Material\r

\r

• AI-ENTRY.md\r
• CLAUDE.md\r
• dev/ai/skills/create-framework-command/SKILL.md\r
• dev/ai/skills/code-generation-standards/SKILL.md\r
• dev/ai/skills/php84-performance/SKILL.md\r
• dev/ai/skills/windows-command-quoting/SKILL.md\r \r

Responsibilities\r

\r

• Build commands that orchestrate work cleanly without burying business logic inside console handlers.\r
• Keep generated code aligned with Weline object access, i18n, and testability expectations.\r
• Apply PHP 8.4-safe null handling and type declarations where appropriate.\r
• Prevent command-line quoting errors on Windows-sensitive execution paths.\r \r

Workflow\r

\r

1. Confirm whether the task is command creation, command repair, or code-template generation.\r
2. Check existing command patterns before introducing new framework APIs or signatures.\r
3. Implement the command entry point and keep business logic in services.\r
4. Register or refresh command metadata through the framework command upgrade flow.\r
5. Apply code-generation guardrails, typing rules, and i18n rules to the produced code.\r
6. Validate on the intended platform, especially when shell composition or Windows quoting is involved.\r
7. Report command usage, dependencies, and any environment assumptions.\r \r

Weline Rules\r

\r

• Do not edit generated/ directly.\r
• Run php bin/w command:upgrade after creating or changing command registration.\r
• Do not hardcode user-facing text; use i18n-aware patterns.\r
• Do not use declare(strict_types=1) inside .phtml.\r
• In WLS-sensitive code, do not use sleep, die, or exit.\r \r

Inputs Required\r

\r

• Command purpose and expected inputs or flags.\r
• Owning module and related service layer.\r
• Target environment, including Windows-specific command behavior if relevant.\r
• Validation path for the command and any generated files.\r \r

Expected Output\r

\r

• A command or generated-code change that follows Weline conventions.\r
• Registration and execution validation evidence.\r
• Notes about platform assumptions, quoting safety, and affected services.\r \r

Validation\r

\r

• Run php bin/w command:upgrade when command registration changes.\r
• Run the new or updated command with a focused scenario.\r
• Check for PHP 8.4-safe null and typing behavior in changed code.\r
• Check that command handlers do not absorb domain logic that belongs in services.\r \r

Constraints\r

\r

• Do not leave command registration stale after implementation.\r
• Do not invent helper APIs that are not present in the repository.\r
• Do not put complex business rules directly inside console execute methods.\r
• Do not build fragile Windows command strings without explicit quoting discipline.\r \r