Skip to content

thiepdientu/LS-Wedding / .agents/skills/blade-ui

blade-ui

Verified

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.
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: 319kUpdated Claude CodeCodexVerifiedInstall
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: 196kUpdated Claude CodeCodexVerifiedInstall
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: 196kUpdated Claude CodeCodexVerifiedInstall
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: 196kUpdated Claude CodeCodexVerifiedInstall