skills.rest
Athos1972
Athos1972COMMUNITY
Explore all skills by this author →
WebsiteGitHub

designer

Convert fuzzy feature requests into design-spec documents with user flows and acceptance criteria.

Updated Apr 7, 2026
Search Tags:#workflow#design#documentation#handoff#spec#ux#feature-request
One-click install
npx skills add https://github.com/Athos1972/pundo_frontend --skill designer-athos1972
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: designer
Source: https://github.com/Athos1972/pundo_frontend/tree/main/.claude/skills/designer
Command: npx skills add https://github.com/Athos1972/pundo_frontend --skill designer-athos1972

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Convert fuzzy feature requests into precise, design-spec documents ready for architectural review.

Core Features & Use Cases

  • Translates user descriptions and project context into a structured design document.
  • Produces user flows, screen/component inventory, and acceptance criteria for handoff to architects.
  • Applies to UI/UX changes and feature enhancements where no code changes are made by this skill.

Quick Start

Provide a user feature description and project context to generate the designated spec file at specs/<feature-slug>/01-design.md

Frequently Asked Questions about designer

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

FAQPage Schema
How do I convert a fuzzy feature request into a structured design spec?▼

To convert a fuzzy feature request into a design spec, provide the user description and project context to generate a structured document with user flows, screen inventory, and acceptance criteria at specs/<feature-slug>/01-design.md.

What should a UX design document include for architectural review?▼

A UX design document for architectural review should include detailed user flows, a screen and component inventory, and clear acceptance criteria to ensure precise handoff from design to architecture.

How do I document UI changes and acceptance criteria without writing application code?▼

You can document UI changes and acceptance criteria without writing application code by generating a single design specification file that enforces an autonomous workflow, leaving implementation untouched.

Does this design spec workflow output multiple files or modify existing code?▼

The design spec workflow does not output multiple files or modify code, strictly emitting only one file at specs/<feature-slug>/01-design.md to enforce autonomous spec generation without application code changes.

When do I need to generate a design spec for a feature enhancement?▼

You need to generate a design spec for a feature enhancement when UI changes or UX problems require documented user flows, component inventory, and acceptance criteria before proceeding to architectural review.

Can I use this to create handoff documentation for architects from raw project context?▼

Yes, you can create handoff documentation for architects by translating raw user descriptions and project context into a precise design-spec document containing user flows and acceptance criteria.

Related Skills

Explore More Design & Creative Skills→
Yoriichi-DangYoriichi-Dang

feature-design-assistant

Translate vague feature ideas into structured design documents and specifications.

Community
Basic
matchojeckimatchojecki
1

spec-writing

Create SPEC documents with templates, checklists, and phased implementation plans.

Community
Advanced
ulpi-ioulpi-io
13

frontend-design-ui-ux

Translate UX concepts into design specs, tokens, and component briefs for Next.js and React handoff.

Official
Advanced
Vivekmano27Vivekmano27

project-requirements

Generate complete project specification documents from a concise project brief.

Community
Advanced