blade-components-and-layouts
Blade Components And Layouts
Use this skill when a Laravel task involves blade components and layouts.
When the app has multiple menus/pages, also use module-per-menu: keep one Blade view per page or page state, share layout/components, and avoid a single Blade file full of menu-condition blocks.
When the Blade work includes UI/UX design, frontend implementation, browser inspection, or backend contract alignment, also use ui-agent-browser. Keep this skill focused on template structure, component boundaries, slots, layouts, and rendering purity.
This skill is adapted to the personal Laravel standards in this repository. It maps the public blade-components-and-layouts topic from jpcaparas/superpowers-laravel into the local blade-components-and-layouts catalog without copying third-party skill body text.
Syarif Defaults
- Follow Laravel conventions before introducing custom abstractions.
- Prefer project-local patterns when they are explicit and tested.
- Keep controllers focused on HTTP orchestration.
- Put validation, authorization, transactions, side effects, and integrations at clear boundaries.
- Keep client names, credentials, internal URLs, provider secrets, and project-specific business rules out of reusable standards.
- Verify important behavior with the smallest meaningful tests and quality checks.