frontend-design v1.0.0A

Immutable. This exact content is served forever at /api/v1/blob/28b579f95a01162e.

---
name: frontend-design
description: "Design and build production-grade frontends with bold, distinctive aesthetics."
version: "1.0.0"
metadata:
  author: CoWork OS Contributors <info@coworkosapp.com>
  source-author: "Anthropic"
---

# frontend-design

## Purpose

Design and build production-grade frontends with bold, distinctive aesthetics.

## Routing

- Use when: Use when the user asks to design and build production-grade frontends with bold, distinctive aesthetics.
- Do not use when: Do not use when the request is asking for planning documents, high-level strategy, or non-executable discussion; use the relevant planning or design workflow instead.
- Outputs: Outcome from frontend-design: task-specific result plus concrete action notes.
- Success criteria: Returns concrete actions and decisions matching the requested task, with no fabricated tool-side behavior.

## Trigger Examples

### Positive

- Use the frontend-design skill for this request.
- Help me with frontend-design.
- Use when the user asks to design and build production-grade frontends with bold, distinctive aesthetics.
- frontend-design: provide an actionable result.

### Negative

- Do not use when the request is asking for planning documents, high-level strategy, or non-executable discussion; use the relevant planning or design workflow instead.
- Do not use frontend-design for unrelated requests.
- This request is outside frontend-design scope.
- This is conceptual discussion only; no tool workflow is needed.

## Runtime Prompt

- Current runtime prompt length: 4071 characters.
- Runtime prompt is defined directly in `../frontend-design.json`.