One-click install
npx skills add https://github.com/saranskumar/anti-slop --skill screen-planner
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: screen-planner
Source: https://github.com/saranskumar/anti-slop/tree/main/archive/skills-legacy/screen-planner
Command: npx skills add https://github.com/saranskumar/anti-slop --skill screen-planner

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plan screens, views, and page responsibilities for a product flow by turning user journeys into a structured screen inventory with clearly defined purposes and ownership.

Core Features & Use Cases

  • Screen inventory: capture every screen in the flow with its purpose and responsibilities.
  • State and surface mapping: define key states, transitions, and component-level responsibilities without committing to visuals.
  • Reusability and patterns: identify shared surfaces and patterns to streamline design and development.

Quick Start

Inventory the current user journeys and map each flow into screens with explicit purposes and states.

Frequently Asked Questions about screen-planner

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

FAQPage Schema
How do I create a screen inventory from existing user journeys?

To create a screen inventory from user journeys, map each flow step into distinct screens with explicit purposes, key states, and component responsibilities. This structured planning defines data inputs, primary actions, and failure states across multi-surface product flows.

What is screen planning in product design and UX?

Screen planning is the process of defining page responsibilities and screen definitions before visual design. It transforms user journeys into a structured inventory that captures screen purpose, transitions, data requirements, and reusable patterns to streamline UX design and development.

How do I define component responsibilities across multi-surface flows?

Define component responsibilities by mapping state and surface transitions within your screen inventory. Specify requirements for each screen's data inputs, primary actions, and failure states to ensure clear ownership and identify reusable patterns across the product flow.

Can I use screen planning for multi-surface product flows without committing to visuals?

Yes, screen planning applies to multi-surface flows without committing to visuals by focusing on state and surface mapping. It captures every screen's purpose, key states, and transitions, establishing guardrails and reusability patterns before visual design begins.

What's the best way to plan screen states and transitions for a product flow?

The best way to plan screen states is to inventory current user journeys and map each flow into screens with explicit purposes. Define key states, transitions, and component-level responsibilities to establish clear guardrails and shared surfaces.

When do I need a structured screen inventory for UX design?

You need a structured screen inventory when planning complex product flows that require clear ownership. It helps UX teams define screen purposes, failure states, reusable patterns, and component responsibilities before committing to visual design or development.