shape

Shape UI screens into low-fidelity plans with ASCII layouts and state matrices.

Updated May 22, 2026
One-click install
npx skills add https://github.com/Nweremizu/ekklesia --skill shape-nweremizu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: shape
Source: https://github.com/Nweremizu/ekklesia/tree/main/.junie/skills/shape
Command: npx skills add https://github.com/Nweremizu/ekklesia --skill shape-nweremizu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents teams from jumping straight into polished UI code before the product shape is clear, reducing generic layouts, missing states, and ambiguous requirements.

Core Features & Use Cases

  • Clarify the brief: Forces the user to define the primary action, visibility rules, success criteria, and audience before any implementation starts.
  • Inventory content: Captures every piece of content and ranks it by priority so the screen structure reflects what must be seen first.
  • Map states and open questions: Calls out loading, empty, error, and other important states while surfacing unresolved decisions early.
  • Use case: Ideal for a new dashboard, onboarding flow, settings page, or any ambiguous product screen that needs a low-fidelity plan before code.

Quick Start

Ask me to shape the target screen so I can produce the content inventory, ASCII desktop and mobile layouts, state list, and open questions before any code is written.

Frequently Asked Questions about shape

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

FAQPage Schema
How do I plan a UI layout before writing frontend code?

To plan a UI layout before coding, generate a low-fidelity screen plan that includes prioritized content lists, ASCII desktop and mobile layouts, and a state matrix to clarify the product shape.

What is the best way to wireframe an ambiguous product discovery brief?

Wireframing an ambiguous brief requires defining the primary action, inventorying content by priority, and mapping loading and empty states to surface unresolved decisions before implementation.

How do I map UI states for a new dashboard or settings page?

Map UI states by creating a state matrix that explicitly calls out loading, empty, error, and other important conditions while surfacing open questions to resolve before coding begins.

Can I use ASCII layouts for mobile and desktop screen planning?

Yes, you can produce markdown-first artifacts featuring both ASCII desktop and mobile layouts to visualize layout regions and structure content before any visual design work starts.

Do I need design software to create a low-fidelity screen plan?

No design software is needed to create a low-fidelity screen plan because the output is a markdown-first artifact with ASCII layouts, requiring only a text editor to define content and states.

Why should I create a content inventory before building a UI?

Creating a content inventory before building a UI ensures the screen structure reflects what must be seen first, reducing generic layouts and ambiguous requirements during product discovery.