weline-framework-core

To structure a new module in the Weline Framework, follow the established guardrails for module, controller, and model development. These references provide centralized workflow guidance to align your coding conventions with core framework practices.

Registering routes and validating HTTP requests in WelineFramework requires following defined routing practices and dev workflow guardrails. You must execute `php bin/w setup:upgrade` for verification to ensure route registration meets workflow validation requirements.

Yes, you can configure environment and i18n settings when extending the framework core. The Skill organizes core contributions around consistent env/config and i18n practices, providing structured guidance for these specific framework extensions.

Yes, you need to run `php bin/w setup:upgrade` after modifying controllers or models. This command serves as the verification step required by the WelineFramework dev workflow to validate changes and ensure proper route registration.

The limitation when editing generated assets during Weline module development is that you must not edit them. The framework's frontmatter-based metadata standards and workflow validation requirements explicitly prohibit modifying generated assets to maintain repository integrity.