plan-ui-change

Decompose Blazor UI features into components with data flows and ownership.

Updated May 28, 2026

Search Tags:#software design #programming #Blazor #component decomposition #UI planning

Ready to run

npx skills add https://github.com/ojrojas/AgentsInstructions --skill plan-ui-change

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: plan-ui-change
Source: https://github.com/ojrojas/AgentsInstructions/tree/main/.claude/skills/dotnet-blazor/skills/plan-ui-change
Command: npx skills add https://github.com/ojrojas/AgentsInstructions --skill plan-ui-change

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the challenge of planning and structuring complex Blazor UI features, especially for applications with multi-section layouts or extensive interactive components.

Core Features & Use Cases

Component Decomposition: Decompose UI features into composable components.
Data Flow Analysis: Designate data flow between components and determine state ownership.
Quick Implementation Guidance: Provide a workflow to implement planned components quickly and efficiently.

Quick Start

Generate a component plan for the 'DashboardPage' feature by running the 'plan-ui-change' skill.

Frequently Asked Questions about plan-ui-change

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

FAQPage Schema

How do I plan Blazor component decomposition for a complex UI feature?▼

To plan Blazor component decomposition, you break down complex UI features into manageable components, defining the component hierarchies, data flows, and state ownership specifically tailored for the Blazor framework and .NET environments.

What is the best way to structure data flow and state ownership in Blazor applications?▼

Structuring data flow in Blazor applications involves designating data flow between components and determining state ownership during the planning phase, ensuring your interactive components are composable and efficiently managed.

How do you break down a multi-section Blazor layout into composable components?▼

Breaking down a multi-section Blazor layout involves decomposing the UI feature into composable components and mapping out a component hierarchy, which provides a workflow to implement the planned components quickly and efficiently.

When do I need to use UI planning for Blazor component architecture?▼

You need UI planning for Blazor component architecture when structuring complex UI features, especially for applications with multi-section layouts or extensive interactive components that require clear data flow and state ownership.

Can I use this component planning approach for any .NET environment?▼

Yes, this component planning approach is tailored for use with the Blazor framework and .NET environments, helping you design component hierarchies and data flows effectively within that specific ecosystem.

What are the limitations of planning Blazor UI changes without component decomposition?▼

Without component decomposition, planning complex Blazor UI changes becomes challenging, making it difficult to manage multi-section layouts, define clear data flows, and determine state ownership across extensive interactive components.