ba-mockup-prompt-gen-detail

Generate detailed UI screen prompts from ERD data for multi-screen workflows.

Updated Apr 12, 2026
One-click install
npx skills add https://github.com/Yukine5377/common --skill ba-mockup-prompt-gen-detail
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ba-mockup-prompt-gen-detail
Source: https://github.com/Yukine5377/common/tree/main/.cursor/skills/ba-mockup-prompt-gen_detail
Command: npx skills add https://github.com/Yukine5377/common --skill ba-mockup-prompt-gen-detail

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines generating detailed prompts for UI screen content from ERD/data, ensuring outputs strictly describe the screen area without any app chrome, navigation, or brand guidelines.

Core Features & Use Cases

  • Multi-screen prompt generation: produces detailed prompts for multiple screens within a single file.
  • Scope discipline: enforces prompts to include only the screen content area; excludes menus, sidebars, headers, and any chrome outside the screen. It also ensures no brand guidelines are embedded in outputs.
  • Guided usage: requires ERD/data and a list of screens to drive prompt creation, with optional per-screen purpose (pain points, data relationships, or flow context).

Quick Start

Provide ERD/data and the screen list; generate per-screen prompts that focus solely on the detailed content area of each screen, with no app chrome or brand guidelines.

Frequently Asked Questions about ba-mockup-prompt-gen-detail

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

FAQPage Schema
How do I generate UI screen prompts from ERD data for AI-driven design?

To generate UI screen prompts from ERD data, provide your entity-relationship data and a list of screens. The system outputs standalone prompts focusing solely on the detailed screen content area, strictly excluding app chrome and brand guidelines.

What is the scope of AI prompts generated from database ERD for multi-screen workflows?

The scope of AI prompts generated from database ERD is limited to the detailed content area of each screen. This multi-screen workflow ensures outputs exclude menus, sidebars, headers, and any app chrome outside the specific screen boundary.

How to create standalone UI prompts for multiple screens without including app chrome or brand guidelines?

To create standalone UI prompts for multiple screens, input your ERD data and screen list. The process enforces scope discipline by automatically stripping out app chrome, navigation elements, and brand guidelines from the final prompt outputs.

Can I use ER diagrams to drive detailed prompt generation for separate application screens?

Yes, you can use ER diagrams to drive detailed prompt generation by supplying the ERD data alongside a screen list. Optional per-screen context like pain points, data relationships, or flow context can be added to guide the prompt creation process.

Why do my AI-generated UI prompts from ERD data include unwanted layout and style constraints?

Unwanted layout and style constraints in AI-generated UI prompts occur when scope discipline is not enforced. This system specifically prevents brand guidelines, layout constraints, and app chrome from being embedded in the detailed screen content outputs.