lowfi-prototype-generator

Generates low-fidelity prototype specification documents from page specs and ASCII layouts.

Updated Jun 5, 2026
One-click install
npx skills add https://github.com/fen-zx/NovelToScript --skill lowfi-prototype-generator-fen-zx
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: lowfi-prototype-generator
Source: https://github.com/fen-zx/NovelToScript/tree/main/.agents/skills/lowfi-prototype-generator
Command: npx skills add https://github.com/fen-zx/NovelToScript --skill lowfi-prototype-generator-fen-zx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning confirmed page layouts into actionable prototype inputs for tools like Figma, Excalidraw, or Whimsical requires manually listing components, mapping interactions, and enumerating page states, which is repetitive and error-prone. This Skill automates that middle layer between layout confirmation and visual prototyping. ## Core Features & Use Cases - Component Inventory Generation: Infers components, types, and properties (placeholders, options, column widths) from page specs or ASCII layouts. - Interaction Flow Diagrams: Produces ASCII flow charts covering trigger, request, success/failure branches, and UI responses for each feature. - Page State Matrix: Covers at least 8 states (initial, loading, populated, empty, no-results, network error, modal, confirmation) with per-region behavior. - Use Case: After confirming an ASCII layout for a user management page, generate a complete prototype spec with component tree, edit/delete interaction flows, and a state matrix that frontend and backend teams can align on before Figma work begins. ## Quick Start Provide the page specs or ASCII layout for your page and ask the Skill to generate a low-fidelity prototype document with component list, interaction flows, and state matrix.

Frequently Asked Questions about lowfi-prototype-generator

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

FAQPage Schema
How do I generate a low-fidelity prototype from an ASCII layout?▼

Provide the ASCII layout diagram with module names and arrangement to the Skill. It infers components per region (e.g., a search area becomes Input, Select, and Button components), then outputs a component list, interaction flows, state matrix, and component tree in Markdown.

What inputs does a low-fidelity prototype generator need?▼

It accepts page specs from a design generator containing component suggestions and data sources, ASCII layout diagrams with module ordering, or requirement analysis JSON with feature points. Page specs produce the most accurate component inference.

Can the output be used directly in Figma or Excalidraw?▼

Yes, the output includes adaptation guidance for each tool. Component lists map to Figma Component Sets, the state matrix maps to Variants, and interaction flows map to Prototype connections or Excalidraw arrows with annotations.

What page states should a prototype specification cover?▼

The Skill covers at least eight states: initial, loading, populated, empty data, no search results, network error, modal open, and confirmation dialog. Empty data and no search results are treated as distinct states with different UI copy.

What are the limitations of low-fidelity prototype documents?▼

Low-fidelity specs describe only what components exist, how they interact, and which states occur. They deliberately exclude colors, border radius, shadows, and animations, which belong to high-fidelity design work.