External/open-design
1
0
Fork 0
mirror of https://github.com/nexu-io/open-design.git synced 2026-10-27 09:51:12 +01:00
Code Issues Packages Projects Releases Wiki Activity
Files
codex/motion-hyperframes-retirement
open-design/plugins/_official/examples/pm-spec/SKILL.md
T
pftom c12c816a44 feat(design-systems): add new design systems for Agentic, Airtable, Ant, Apple, Application, Arc, and Artistic 
- Introduced comprehensive design documentation and JSON configurations for multiple design systems, including Agentic, Airtable, Ant, Apple, Application, Arc, and Artistic.
- Each design system includes detailed guidelines on visual themes, color palettes, typography, spacing, layout, components, and interaction principles.
- Enhanced the overall design framework to support diverse user interfaces and improve consistency across applications.

This update significantly enriches the design resources available for developers, enabling them to create visually cohesive and user-friendly applications.
2026-05-12 15:18:16 +08:00

1.5 KiB
Raw Permalink Blame History

name, description, triggers, od
name description triggers od
pm-spec Product spec / PRD as a single page — problem, success metrics, scope, user stories, design notes, rollout plan, open questions. Use when the brief mentions "PRD", "spec", "product spec", "feature brief", or "需求文档".
prd
spec
product spec
feature brief
feature doc
需求文档
mode platform scenario preview design_system example_prompt
prototype desktop product
type entry
html index.html
requires sections
true
color
typography
layout
components
Write me a PRD for adding two-factor auth to our SaaS app — problem, scope, milestones, open questions.

Product Spec Skill

Produce a one-page product spec / PRD.

Workflow

  1. Read the active DESIGN.md.
  2. Identify the feature + audience from the brief.
  3. Layout:
    • Header strip: title, status pill (Draft / Review / Approved), date, owner.
    • Three-line summary at the top — what, who, why now.
    • "Problem" panel with one paragraph and a quote from a customer or internal partner.
    • "Goals & non-goals" two-column block.
    • "Success metrics" table with metric / target / measurement.
    • "User stories" list with as-a / I-want / so-that format.
    • "Scope" milestone tracker (3–4 phases).
    • "Open questions" with assignee chips.
  4. One inline <style>, semantic HTML, accent used twice max.

Output contract

<artifact identifier="spec-name" type="text/html" title="Spec Title">
<!doctype html>...</artifact>
Reference in New Issue View Git Blame Copy Permalink