Frontend

Name: Frontend
Author: sharmapuneet1510

ASecurity

Frontend architecture - component hierarchy, state management, UI patterns

3 stars
0 votes
0 copies
2 views
Added October 1, 2026

ai-agentsbashreactvueangularfrontend

Security analysis

A100/100

Scanned October 1, 2026

npx -y skills add sharmapuneet1510/awesome-prompts --skill frontend --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Frontend?

Add the live security badge to your README. It updates with every re-scan.

[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/sharmapuneet1510-frontend/badge)](https://www.skillsdirectory.com/skills/sharmapuneet1510-frontend)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro

SKILL.md

---
name: frontend
description: Frontend architecture - component hierarchy, state management, UI patterns
argument-hint: requirements="..." [framework="react"]
disable-model-invocation: true
---

Role and rules: read ${CLAUDE_PLUGIN_ROOT}/reference/agent.md and ${CLAUDE_PLUGIN_ROOT}/reference/rules.md for the sections this function needs.

# architect:frontend

**Design frontend architecture** with component hierarchies, state management, and UI patterns.

## Inputs

```
architect:frontend requirements="..." [framework="react"]
```

- `requirements` (string, required) — UI/UX requirements
- `framework` (string, optional) — Framework (react, vue, angular)
- `state_management` (string, optional) — State lib (redux, zustand, context)

## Outputs

```
✓ component-hierarchy.md      — Component tree and relationships
✓ state-management.md         — State flow and patterns
✓ routing.md                  — Page/route structure
✓ ui-patterns.md              — Reusable UI patterns
```

## Example

```bash
architect:frontend requirements="E-commerce: product catalog, shopping cart, checkout, user profile"
```

## Workflow

1. Analyze UI requirements
2. Design component hierarchy
3. Plan state management
4. Define routing structure
5. Identify reusable patterns
6. Plan responsive design
7. Document interaction flows

## Related Functions

- `architect:design` — Full system architecture
- `architect:a11y` — Accessibility planning
- `implementer:build` — Frontend implementation