agentsclimarketplace

Wireframer

Skill gridi-ai/gridi-skills/skills/wireframer

A skill for generating wireframes based on user stories. Analyzes user story documents and creates ASCII or Mermaid diagram-based wireframes as markdown files. Use this skill for wireframe creation, UI design, or screen structure design requests.From its SKILL.md

Install
npx -y skills add gridi-ai/gridi-skills --skill wireframer

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

4.5 KB, as published. Nobody here has run it

🌐 Language

All output documents and user-facing messages must be written in the language specified by crew-config.json β†’ preferences.language. If not set, default to English.

Wireframer

Analyzes user stories and generates wireframes for each screen.

Workflow

1. Receive User Story Input

Receive the path to the user story document.

Example inputs:
- "Generate wireframes based on docs/user-stories/account-user-stories.md"
- "Draw wireframes for US-001 through US-005"

2. Analyze User Stories

  1. Read the user story document
  2. Group by screen (bundle stories handled on the same screen)
  3. Identify the navigation flow between screens

3. Generate Wireframes

Generate ASCII-based wireframes for each screen.

Wireframe Format

## WF-001: [Screen Name]

**Related stories**: US-001, US-002

### Screen Structure

β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚  Header                      [Logo] β”‚
β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€
β”‚                                     β”‚
β”‚  β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”   β”‚
β”‚  β”‚  Email                      β”‚   β”‚
β”‚  β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜   β”‚
β”‚                                     β”‚
β”‚  β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”   β”‚
β”‚  β”‚  Password                   β”‚   β”‚
β”‚  β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜   β”‚
β”‚                                     β”‚
β”‚  [ Log In ]                         β”‚
β”‚                                     β”‚
β”‚  Forgot Password | Sign Up          β”‚
β”‚                                     β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜

### Component Description

| ID | Component | Type | Description |
|----|-----------|------|-------------|
| 1 | Email input | Input | Email format validation |
| 2 | Password input | Input | Masked input |
| 3 | Log in button | Button | Primary action |
| 4 | Forgot password | Link | Navigate to password reset screen |
| 5 | Sign up | Link | Navigate to sign-up screen |

### State-Specific Screens

- **Error state**: Red error message displayed below the input field
- **Loading state**: Spinner on the button, inputs disabled

4. Generate Screen Flow Diagram

Visualize the navigation flow between screens using Mermaid.

flowchart TD
    A[Login] -->|Login success| B[Dashboard]
    A -->|Sign up click| C[Sign Up]
    A -->|Forgot password| D[Password Reset]
    C -->|Registration complete| A
    D -->|Reset complete| A

5. File Output

{project-root}/docs/{backlog-keyword}/wireframes.md

Directory rule: All deliverables are stored under the backlog-keyword directory.

Wireframe Writing Principles

1. Simplicity

  • Exclude unnecessary decorative elements
  • Include only essential UI elements
  • Clear layout structure

2. Consistency

  • Use the same representation for the same component
  • Use standard symbols (reference: references/wireframe-symbols.md)

3. Completeness

  • All user stories must be mapped to a screen
  • Specify key states (default, error, loading, empty state)

4. Navigation

  • Clearly indicate navigation paths between screens
  • Visualize user flows

Component Types

TypeRepresentationDescription
Inputβ”Œβ”€β”€β”€β”β””β”€β”€β”€β”˜Text input field
Button[ Text ]Clickable button
LinkUnderlined textNavigation link
Checkbox[x] / [ ]Checkbox
Radio(o) / ( )Radio button
Dropdown[Select β–Ό]Dropdown menu
CardBox + contentCard component
List- ItemList item
TableGrid structureTable
ModalCentered boxModal/Dialog

References

Keep looking

Skills are one crate of 627,801. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.