Design Blade Component
Use when creating or refactoring Blade components, partials, and reusable view pieces.
Install
$ agentstack add skill-alizharb-agent-skills-design-blade-component ✓ 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-design-blade-component) 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
Design Blade Component
When To Use
Use this skill when a Blade view is getting repetitive, too large, or hard to reuse across the app.
Inputs Needed
- UI purpose, repeated markup, slots, props, localization needs, accessibility concerns, and tests.
Workflow
- Inspect existing Blade components and partials.
- Decide whether the UI belongs in a class-based component, anonymous component, or partial.
- Prefer the smallest reusable unit that removes duplication.
- Keep component APIs small and obvious.
- Localize labels and messages.
- Keep presentation logic out of the template whenever possible.
- Add tests when the component drives behavior or important UI states.
Files That May Be Created
- Blade component classes, component views, partials, and tests.
Files That May Be Modified
- Existing views, translation files, and tests.
Architecture Rules
- Blade should render presentation only.
- Shared markup belongs in shared components instead of repeated snippets.
- Keep templates small enough that they remain easy to scan.
Testing Requirements
- Test rendering, visible states, localization, and accessibility-sensitive behavior when relevant.
Review Checklist
- Is the component reusable?
- Is the public API small?
- Would a partial or slot make the code cleaner?
Common Mistakes to Avoid
- Duplicating the same markup across many views.
- Putting business logic in the template.
- Creating a component when a simple partial would be clearer.
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.