shape

Plans UX and produces a design brief without implementation.

Updated Jul 10, 2026
One-click install
npx skills add https://github.com/noticesfromchat/macos-app-digest --skill shape-noticesfromchat
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: shape
Source: https://github.com/noticesfromchat/macos-app-digest/tree/main/.agents/skills/shape
Command: npx skills add https://github.com/noticesfromchat/macos-app-digest --skill shape-noticesfromchat

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often jump into building features before clarifying the user experience, leading to rework and misaligned expectations. This Skill structures the upfront thinking by planning the UX and delivering a design brief before any code is written. ## Core Features & Use Cases - UX Planning: Shapes the user experience for a proposed feature before implementation begins. - Design Brief Delivery: Produces a concise design brief as the output, not working code. - Use Case: Before building a new settings panel, invoke the skill with the feature idea to receive a structured design brief covering the intended UX, which engineers and designers can then review and implement. ## Quick Start Ask the agent to shape the UX for your feature, for example: shape a new onboarding flow for first-time users.

Frequently Asked Questions about shape

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

FAQPage Schema
How do I plan UX for a feature before coding?

Invoke the shape skill with a description of the feature you want to build. It plans the user experience and returns a design brief you can review with your team before any implementation starts.

What does a design brief from the shape skill contain?

The skill delivers a design brief describing the planned UX for the requested feature. It intentionally stops at the brief stage and does not produce implementation code.

Does the shape skill write any code?

No. The skill explicitly plans UX and delivers a design brief without implementation. Coding happens later as a separate step after the brief is reviewed.

When should I not use the shape skill?

Skip it when the feature is trivial, the UX is already agreed upon, or you need working code immediately. It adds the most value for features where the user experience is still undefined.