up-interface-design

Design technology-agnostic UP interface blueprints with screens, forms, lists, and reports.

3|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/apolosan/unified_process_pi_extension --skill up-interface-design
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: up-interface-design
Source: https://github.com/apolosan/unified_process_pi_extension/tree/main/skills/up-interface-design
Command: npx skills add https://github.com/apolosan/unified_process_pi_extension --skill up-interface-design

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a technology-agnostic blueprint to design user interfaces within the Object-Oriented Unified Process, outlining screens, forms, lists, and reports without tying to a specific framework.

Core Features & Use Cases

  • Defines six interface units: Index/Menu, Data Unit, Multidata Unit, Entry Unit, Selection Unit, and Operation Unit.
  • Describes standard navigation flows (CRUD, report, and functional processes) and uses Mermaid diagrams to visualize transitions.
  • Generates design artifacts and guidance to drive implementation, including field definitions, listing configurations, and form specifications.

Quick Start

Create the interface blueprint for a UP module and generate docs/up/08-interface-design.md.

Frequently Asked Questions about up-interface-design

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

FAQPage Schema
How do I design technology-agnostic interface blueprints for UP systems?

To design technology-agnostic interface blueprints for UP systems, define screens, forms, lists, and reports without tying to specific frameworks. The approach outlines six interface units and standard navigation flows to drive implementation.

What are the six interface units used in UP module design?

The six interface units in UP module design are Index/Menu, Data Unit, Multidata Unit, Entry Unit, Selection Unit, and Operation Unit. These units categorize standard screens and functional components across the system.

How do I visualize navigation flows and CRUD processes for interface design?

Visualize navigation flows and CRUD processes for interface design using Mermaid diagrams. The design specifies standard transitions for CRUD, report, and functional processes to map screen-to-screen workflows.

Does this interface design approach generate field definitions and form specifications?

Yes, this interface design approach generates artifacts including field definitions, listing configurations, and form specifications. These outputs provide the necessary guidance to drive subsequent implementation.

Can I use Mermaid flowcharts to document workflows in a UP interface blueprint?

Yes, you can use Mermaid flowcharts to document workflows in a UP interface blueprint. The design process applies Mermaid to visualize navigation transitions and functional processes across the defined interface units.

What is the best way to document a UP interface design for a module?

The best way to document a UP interface design is to generate a structured markdown file, such as docs/up/08-interface-design.md. This captures the module's field definitions, navigation diagrams, and interface unit specifications.