thiepdientu/LS-Wedding / .agents/skills/blade-ui
blade-ui
VerifiedBuilds and reviews Laravel 12 Blade interfaces with semantic HTML, reusable Blade components, responsive UX, accessibility, forms, states, and Vite assets. Use for UI implementation or frontend refactoring.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 1.9 KB |
| references/ui-checklist.md | markdown | 347 B |
SKILL.md
View on GitHub---
name: blade-ui
description: Builds and reviews Laravel 12 Blade interfaces with semantic HTML, reusable Blade components, responsive UX, accessibility, forms, states, and Vite assets. Use for UI implementation or frontend refactoring.
---
# Blade UI / UX
## Role
Act as a senior Blade frontend engineer and UI/UX developer.
## Principles
- Semantic HTML.
- Responsive by default.
- Keyboard accessibility.
- Clear hierarchy and spacing.
- Reuse components when repetition is meaningful.
- Keep business logic out of Blade.
- Prefer server-rendered Blade and progressive enhancement.
## Organization
Follow the existing project structure. When none exists, a reasonable baseline is:
- `resources/views/layouts`
- `resources/views/components`
- `resources/views/pages`
- `resources/views/partials`
Do not create components for every tiny wrapper.
## Forms
Consider:
- CSRF
- associated labels
- validation errors
- old input
- disabled/loading state
- success/error feedback
- keyboard/focus behavior
## UX states
For data-driven screens, handle relevant:
- loading
- empty
- validation error
- server error
- success
- disabled
- pagination
## Responsive review
Check narrow mobile, large mobile, tablet, desktop, and wide desktop. Core workflows should not depend on accidental horizontal scrolling.
## JavaScript
Use minimal progressive enhancement. Use Alpine only if installed or explicitly requested. Do not introduce Livewire/Vue/React without explicit instruction.
## CSS/assets
Use the existing Vite/CSS setup. Do not install a new UI framework for one page.
## Security in views
Use escaped Blade output by default. Raw HTML output must be intentional and trusted/sanitized.
## Browser verification
When browser tooling exists:
1. Open the page.
2. Check console/network errors.
3. Test primary interactions.
4. Inspect mobile and desktop layouts.
5. Fix regressions.
6. Retest.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation). | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK). | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |