skills.rest
akiramei
akirameiCOMMUNITY
Explore all skills by this author →
GitHub

vsa-boundary-modeler

Automate boundary modeling for UI-enabled Blazor features with Intent and CanXxx design.

1|Updated Oct 28, 2025
Search Tags:#UI#DDD#Blazor#CanXxx#boundary-modeling#boundary-pattern
One-click install
npx skills add https://github.com/akiramei/blazor-enterprise-architecture-poc --skill vsa-boundary-modeler
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: vsa-boundary-modeler
Source: https://github.com/akiramei/blazor-enterprise-architecture-poc/tree/main/catalog/skills/vsa-boundary-modeler
Command: npx skills add https://github.com/akiramei/blazor-enterprise-architecture-poc --skill vsa-boundary-modeler

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Blazor VSA の UI 機能設計では、Boundary パターンの境界を見落としがちです。このスキルは UI を持つ機能で、Entity.CanXxx() の設計・Intent の定義・BoundaryService の責務分離を促し、境界の設計を自動的に想起させます。結果として、UI の操作可否判断を正しく Entity に委譲し、複雑性を低減します。

Core Features & Use Cases

  • Boundary モデリングの自動補助: UI ある機能における Boundary の設計を支援します。
  • Intent 定義の標準化: UI の操作 Intent を列挙して CanXxx() を導出します。
  • BoundaryService の委譲明確化: BoundaryService はデータ取得と委譲だけを担当します。
  • Use Case: 例えば注文のキャンセル可否を UI から判定するケースで、Order.CanCancel() を UI から直接参照できる形にします。

Quick Start

ユーザーが「注文のキャンセルが可能か」を判断する機能を設計する場合、UI を持つエンティティの Boundary モデルを作成するようAIに指示します。指示内容には、関連する Intent、CanXxx()、BoundaryService の委譲先を明記します。

Frequently Asked Questions about vsa-boundary-modeler

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

FAQPage Schema
How do I design boundary patterns for Blazor UI forms and screens?▼

Boundary modeling for UI automates the separation of concerns in Blazor forms and detail screens. Define Intent from UI operations, implement Entity.CanXxx() methods for business logic, and delegate data retrieval to BoundaryService, ensuring UI state correctly reflects entity permissions.

What's the best way to determine if a user can perform an action in Blazor UI?▼

Derive CanXxx() methods from UI operation intents and place business logic inside entities rather than BoundaryService. BoundaryService retrieves data and delegates to Entity.CanXxx(), returning BoundaryDecision outcomes that UI consumes directly.

How should I separate responsibilities between Entity and BoundaryService in DDD?▼

Entity.CanXxx() encapsulates all business rules; BoundaryService handles only data retrieval and delegation. This pattern clarifies domain logic boundaries in UI-driven features like order cancellation, reducing complexity and preventing logic leaks into service layers.

Can I use boundary pattern modeling with Blazor component design?▼

Yes. Boundary modeling automates Intent definition and Entity.CanXxx() design for Blazor UI components—forms, lists, and detail screens. It ensures UI operations map correctly to entity capabilities and business constraints.

What problems does the boundary pattern solve in UI-driven features?▼

Boundary pattern design prevents blurred responsibilities between UI state, entity rules, and service logic. It ensures permission checks reside in Entity.CanXxx(), not scattered across BoundaryService, keeping business logic cohesive and UI decision-making accurate.

Related Skills

Explore More Software Engineering Skills→
musujmusuj

phase-1-schema

Define project terminology, entities, relationships, and data structures.

Community
Intermediate
michaelvolzmichaelvolz

rm-guide-blazor

Enforce Blazor component best practices for lifecycle and render correctness.

Community
Basic
akirameiakiramei
1

vsa-implementation-guard

Enforce anti-mistake rules during C# code generation for Blazor VSA implementations.

Community
Advanced
saranskumarsaranskumar

express-api-designer

Plan Express APIs with route groups, middleware boundaries, and service layering.

Community
Intermediate