workspace-blazor-mvvm
Guide for implementing LionFire workspace documents with Blazor MVVM patterns, including ObservableDataView component usage, workspace-scoped service injection, and reactive persistence. Use this skill when creating Blazor pages for workspace documents, fixing workspace service scoping issues, or implementing list/detail views with ObservableReader/Writer.
What this skill does
# Workspace Blazor MVVM Patterns
## When to Use This Skill
Use this skill when:
- Creating Blazor pages for workspace-scoped documents
- Using `ObservableDataView` component for list views
- Implementing detail pages with workspace services
- Debugging "Unable to resolve service for type 'IObservableReader'" errors
- Working with reactive persistence (`IObservableReader/Writer`) in Blazor
- Setting up workspace document types with CRUD UI
**Keywords**: workspace, ObservableDataView, IObservableReader, IObservableWriter, workspace services, CascadingParameter, Blazor MVVM, workspace scoping, workspace documents
---
## Quick Reference
### Critical Concept: Workspace Service Scoping
**The Problem**: `IObservableReader/Writer` services are **workspace-scoped**, not in the root DI container.
**The Solution**: Use `CascadingParameter` to get `WorkspaceServices` and resolve services manually.
```csharp
[CascadingParameter(Name = "WorkspaceServices")]
public IServiceProvider? WorkspaceServices { get; set; }
var reader = WorkspaceServices.GetService<IObservableReader<string, BotEntity>>();
```
**See**: `references/service-scoping.md` for complete explanation.
---
## Two Primary Patterns
### Pattern 1: ObservableDataView (List Views)
**When**: Displaying a list/grid of workspace documents with CRUD operations.
**Code** (~20-30 lines):
```razor
<ObservableDataView TKey="string"
TValue="BotEntity"
TValueVM="BotVM"
DataServiceProvider="@WorkspaceServices">
<Columns>
<PropertyColumn Property="x => x.Value.Name" />
</Columns>
</ObservableDataView>
@code {
[CascadingParameter(Name = "WorkspaceServices")]
public IServiceProvider? WorkspaceServices { get; set; }
}
```
**See**: `examples/list-view-example.razor` for complete example.
### Pattern 2: Manual VM Creation (Detail Views)
**When**: Displaying/editing a single workspace document with custom layout.
**Code** (~60-80 lines):
```razor
@code {
[CascadingParameter(Name = "WorkspaceServices")]
public IServiceProvider? WorkspaceServices { get; set; }
private ObservableReaderWriterItemVM<string, BotEntity, BotVM>? VM { get; set; }
protected override async Task OnParametersSetAsync()
{
var reader = WorkspaceServices.GetService<IObservableReader<string, BotEntity>>();
var writer = WorkspaceServices.GetService<IObservableWriter<string, BotEntity>>();
VM = new ObservableReaderWriterItemVM<string, BotEntity, BotVM>(reader, writer);
VM.Id = BotId;
}
}
```
**See**: `examples/detail-view-example.razor` for complete example.
---
## Step-by-Step Workflows
### Workflow 1: Fix "Unable to Resolve Service" Error
When encountering:
```
InvalidOperationException: Unable to resolve service for type
'IObservableReader`2[System.String,MyEntity]'
```
**Steps**:
1. **Identify the issue**: Component trying to inject workspace-scoped services from root container
2. **Check current pattern**:
```csharp
// ❌ WRONG: Tries to inject from root
@inherits ReactiveInjectableComponentBase<ObservableReaderWriterItemVM<string, BotEntity, BotVM>>
```
3. **Fix with CascadingParameter**:
```csharp
// ✅ RIGHT: Get workspace services via cascading parameter
[CascadingParameter(Name = "WorkspaceServices")]
public IServiceProvider? WorkspaceServices { get; set; }
protected override async Task OnParametersSetAsync()
{
var reader = WorkspaceServices.GetService<IObservableReader<string, BotEntity>>();
var writer = WorkspaceServices.GetService<IObservableWriter<string, BotEntity>>();
VM = new ObservableReaderWriterItemVM<string, BotEntity, BotVM>(reader, writer);
VM.Id = ItemId;
}
```
4. **Verify registration**:
```csharp
// In Program.cs, ensure:
services
.AddWorkspaceChildType<BotEntity>() // ← Must have this!
.AddWorkspaceDocumentService<string, BotEntity>();
```
**For detailed explanation**: Load `references/service-scoping.md`.
---
### Workflow 2: Create List Page for Workspace Documents
**Goal**: Display a reactive grid of workspace documents with CRUD operations.
**Steps**:
1. **Verify entity and VM are defined**:
```csharp
[Alias("Bot")]
public partial class BotEntity : ReactiveObject
{
[Reactive] private string? _name;
}
public class BotVM : KeyValueVM<string, BotEntity>
{
public BotVM(string key, BotEntity value) : base(key, value) { }
}
```
2. **Verify registration**:
```csharp
services
.AddWorkspaceChildType<BotEntity>()
.AddWorkspaceDocumentService<string, BotEntity>()
.AddTransient<BotVM>();
```
3. **Create list page** using `ObservableDataView`:
- Load `examples/list-view-example.razor`
- Adapt for your entity type
- Key: Set `DataServiceProvider="@WorkspaceServices"`
4. **Customize columns** as needed (PropertyColumn, TemplateColumn)
5. **Add navigation** to detail page:
```razor
<MudButton Href="@($"/bots/{context.Item.Key}")">Edit</MudButton>
```
**For complete pattern details**: Load `references/blazor-mvvm-patterns.md`.
---
### Workflow 3: Create Detail Page for Workspace Document
**Goal**: Display/edit a single workspace document.
**Steps**:
1. **Create page with route parameter**:
```razor
@page "/bots/{BotId}"
@code {
[Parameter]
public string? BotId { get; set; }
}
```
2. **Get workspace services**:
```razor
@inject ILogger<Bot> Logger
@inject IServiceProvider ServiceProvider
@code {
[CascadingParameter(Name = "WorkspaceServices")]
public IServiceProvider? WorkspaceServices { get; set; }
}
```
3. **Resolve reader/writer and create VM**:
- Load `examples/detail-view-example.razor`
- Adapt service resolution pattern
- Create `ObservableReaderWriterItemVM`
4. **Bind UI to VM.Value**:
```razor
<MudTextField @bind-Value="VM.Value.Name" Label="Name" />
```
5. **Implement Save**:
```csharp
private async Task Save() => await VM.Write();
```
**For complete pattern details**: Load `references/blazor-mvvm-patterns.md`.
---
### Workflow 4: Add New Workspace Document Type
**Goal**: Add a new document type (e.g., Portfolio) to existing workspace application.
**Steps**:
1. **Define entity**:
```csharp
[Alias("Portfolio")]
public partial class PortfolioEntity : ReactiveObject
{
[Reactive] private string? _name;
// ... other properties
}
```
2. **Define ViewModel**:
```csharp
public class PortfolioVM : KeyValueVM<string, PortfolioEntity>
{
public PortfolioVM(string key, PortfolioEntity value) : base(key, value) { }
}
```
3. **Register**:
```csharp
services
.AddWorkspaceChildType<PortfolioEntity>()
.AddWorkspaceDocumentService<string, PortfolioEntity>()
.AddTransient<PortfolioVM>();
```
4. **Create pages** (follow Workflow 2 and 3 above)
5. **Result**: Portfolios appear in workspace subdirectory `Portfolios/`
---
## Key Components Reference
### ObservableDataView
**Purpose**: Pre-built MudDataGrid component with reactive workspace data integration.
**Key Parameters**:
- `TKey`, `TValue`, `TValueVM` - Type parameters
- `DataServiceProvider` - **CRITICAL**: Pass `@WorkspaceServices` here
- `AllowedEditModes` - EditMode.None, .Cell, .Form, .All
- `ReadOnly` - Enable/disable editing
- `Columns` - Custom column definitions
**Automatic Features**:
- CRUD toolbar (Add/Edit/Delete buttons)
- Reactive updates (file changes auto-refresh UI)
- VM creation (automatic via constructor)
- Sorting, filtering, grouping
### ObservableReaderWriterItemVM
**Purpose**: ViewModel wrapper for single workspace documents.
**Constructor**:
```csharp
public ObservableReaderWriterItemVM(
IObservableReader<TKey, TValue> reader,
IObservableWriter<TKey, TValue> writer)
```
**Key Properties**:
- `Id` - The document key (triggers load when set)
- `Value` - The wrapped entity (as TValueVM)
- `Writer` - Access to persistence
**Key Methods**:
- `Write()` - Save changes to file
---
## Common Pitfalls
### ❌ Pitfall 1: Injecting Workspace Services Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.