SuperAPI AI Directory

wireframe

General & other

View repository

Updated 10-16 09:29

About this skill

Wireframe: Spec → HTML Wireframe

Generates an HTML wireframe from the spec document. Applies a minimal gray-tone style with Tailwind CDN + CSS variables.

Step 1: Prerequisites

After extracting the feature name from $ARGUMENTS, artifacts/<feature>/spec.md check for existence. If it does not exist, output "First run /spec <feature>." and exit.

Step 2: Scenarios → Screen Grouping + Layout Structure

spec.md의 ### N. Parse the scenarios and group them into visually distinct screen states.

  • One screen = one visually distinct UI state
  • Scenarios that share the same base and differ only in small state variations are grouped into one
  • Completely visually different states are separated into separate screens

For each screen, write the Layout Structureas an indented tree.

Screen: 기본 보드 [col]
├── Header [row] — 로고, 다크모드 토글
├── Toolbar [row] — 검색 input, Priority 필터, Tag 필터
└── Board [row, 1:1:1]
    ├── Column: Todo [col] — 카드 목록 + 추가 입력
    ├── Column: In Progress [col] — 카드 목록
    └── Column: Done [col] — 카드 목록

Layout Structure rules:

  • [row] / [col]: layout direction
  • 1:1:1 and other ratio hints: size ratios between child elements
  • — followed by a summary of the key content of that area

Show the grouping result + Layout Structure to the user and get approval with AskUserQuestion.

Step 3: Generate the full wireframe

  1. assets/template.htmlto obtain the HTML boilerplate

  2. references/style-guide.mdto check the component patterns and color rules

  3. Generate all screens at onceand write them to artifacts/<feature>/wireframe.html:

    • template.html의 <!-- NAV_BUTTONS --> Insert a nav button for each screen at the position
    • template.html의 <!-- SCREEN_CONTENT --> Insert content for each screen at the position
    • {{FEATURE_NAME}}with the actual feature name
    • Display the mapped scenario number at the top of each screen
    • Write the HTML using the component patterns from style-guide.md
    • Use concrete example data from spec.md
  4. Open the file in the browser:

    • macOS: open artifacts/<feature>/wireframe.html
    • Linux: xdg-open artifacts/<feature>/wireframe.html
    • If it does not work, provide the file path
  5. AskUserQuestionto collect feedback

  6. If there is feedback, revise and regenerate, then open it in the browser again

Step 4: Verify scenario coverage

Check whether every scenario number in spec.md is mapped to a screen in the wireframe.

  • For each screen, check the (scenarios: ...) notation
  • If any scenarios are missing, notify the user and ask whether to add them

Step 5: Done

Deliverable: artifacts/<feature>/wireframe.html

Next step guidance: "To start implementation, switch to plan mode."