Manage Frontend Styling
Use when creating or updating Tailwind CSS 4, Flux, or Blade UI patterns and shared components.
Install
$ agentstack add skill-alizharb-agent-skills-manage-frontend-styling ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-alizharb-agent-skills-manage-frontend-styling) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Manage Frontend Styling
When To Use
Use this skill for Blade UI, Tailwind styling, Flux controls, shared components, RTL behavior, dark mode, and accessibility-sensitive presentation.
Inputs Needed
- Screen, user flow, responsive needs, locale requirements, design tokens, and reuse opportunities.
Workflow
- Inspect existing Blade, Flux, Tailwind, and component conventions.
- Prefer shared components or partials when markup repeats.
- Keep templates small and role-focused.
- Use Tailwind 4 utilities and class sorting with Prettier.
- Use only
oklch()theme colors in app-owned CSS tokens. - Make layouts work in both light and dark modes.
- Make layouts work in both LTR and RTL.
- Localize all user-facing strings.
- Keep accessibility in mind: semantics, labels, focus states, keyboard use, and contrast.
- Add tests or snapshots when UI behavior is important.
Files That May Be Created
- Blade components, partials, stylesheets, translation files, and tests.
Files That May Be Modified
resources/views/**resources/css/**- translation files
- component classes
- frontend tests
Architecture Rules
- Keep presentation code thin and reusable.
- Avoid logic that belongs in Actions, Services, DTOs, or controllers.
- Do not let template files become dumping grounds.
Testing Requirements
- Test responsive behavior, accessibility-sensitive interactions, and localization when relevant.
Review Checklist
- Is the markup shared instead of duplicated?
- Are classes sorted and readable?
- Does the UI remain usable in RTL and dark mode?
- Are strings translated?
Common Mistakes to Avoid
- Hardcoded colors or copy.
- Repeating the same component markup many times.
- Writing heavy Blade files with too much logic.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: AlizHarb
- Source: AlizHarb/agent-skills
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.