frontend-brief

Name: frontend-brief
Availability: InStock
Author: seemseam

Transform frontend requests into structured briefs with constraints and acceptance criteria.

17|2|Updated Jun 2, 2026

Search Tags:#workflow #frontend #constraints #briefing #request clarification

Ready to run

npx skills add https://github.com/SeemSeam/agent-roles-spec --skill frontend-brief

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: frontend-brief
Source: https://github.com/SeemSeam/agent-roles-spec/tree/main/roles/frontend-engineer/skills/frontend-brief
Command: npx skills add https://github.com/SeemSeam/agent-roles-spec --skill frontend-brief

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the challenge of handling vague or screenshot-based frontend requests by providing a structured brief that outlines the necessary details for implementation.

Core Features & Use Cases

Request Clarification: Transforms a loose request into a detailed brief.
Workflow Outline: Provides a clear workflow for product surface, user audience, and success criteria.
Constraints and Acceptance Criteria: Defines constraints and acceptance criteria for implementation.
Use Case: When a frontend designer receives a vague request for a new feature, this Skill can help create a detailed brief that includes user requirements, constraints, and verification steps.

Quick Start

Use the frontend-brief skill to generate a brief for a new feature request.

Frequently Asked Questions about frontend-brief

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I clarify a vague frontend request before implementation?▼

To clarify a vague frontend request, you can generate a structured brief that explicitly outlines the product surface, user audience, workflow, constraints, and acceptance criteria needed for implementation.

What is a frontend brief and what details should it include?▼

A frontend brief is a structured document that transforms loose requests into detailed workflows, defining product surfaces, user audiences, constraints, acceptance criteria, and verification scope for implementation.

Can I use a structured brief for Figma-based or screenshot-based frontend requests?▼

Yes, structured briefing is specifically designed for new, screenshot-based, or Figma-based frontend requests that require clarification before implementation to ensure all workflow details are captured.

What is the best way to outline acceptance criteria and verification scope for a new frontend feature?▼

The best way to outline acceptance criteria and verification scope is to transform the initial request into a structured brief, ensuring all workflow constraints and user requirements are explicitly defined before development.

Why does my frontend workflow fail when I start implementation from a loose request?▼

Implementation fails from a loose request because missing details regarding product surface, user audience, and constraints lead to ambiguity, which a structured brief prevents by defining verification scope and acceptance criteria.