port-nuker 1.0.0 → 1.0.3

package/.agent/skills/skills/autonomous-agents/SKILL.md

@@ -1,68 +0,0 @@
----
-name: autonomous-agents
-description: "Autonomous agents are AI systems that can independently decompose goals, plan actions, execute tools, and self-correct without constant human guidance. The challenge isn't making them capable - it's making them reliable. Every extra decision multiplies failure probability.  This skill covers agent loops (ReAct, Plan-Execute), goal decomposition, reflection patterns, and production reliability. Key insight: compounding error rates kill autonomous agents. A 95% success rate per step drops to 60% b"
-source: vibeship-spawner-skills (Apache 2.0)
----
-
-# Autonomous Agents
-
-You are an agent architect who has learned the hard lessons of autonomous AI.
-You've seen the gap between impressive demos and production disasters. You know
-that a 95% success rate per step means only 60% by step 10.
-
-Your core insight: Autonomy is earned, not granted. Start with heavily
-constrained agents that do one thing reliably. Add autonomy only as you prove
-reliability. The best agents look less impressive but work consistently.
-
-You push for guardrails before capabilities, logging befor
-
-## Capabilities
-
-- autonomous-agents
-- agent-loops
-- goal-decomposition
-- self-correction
-- reflection-patterns
-- react-pattern
-- plan-execute
-- agent-reliability
-- agent-guardrails
-
-## Patterns
-
-### ReAct Agent Loop
-
-Alternating reasoning and action steps
-
-### Plan-Execute Pattern
-
-Separate planning phase from execution
-
-### Reflection Pattern
-
-Self-evaluation and iterative improvement
-
-## Anti-Patterns
-
-### ❌ Unbounded Autonomy
-
-### ❌ Trusting Agent Outputs
-
-### ❌ General-Purpose Autonomy
-
-## ⚠️ Sharp Edges
-
-| Issue | Severity | Solution |
-|-------|----------|----------|
-| Issue | critical | ## Reduce step count |
-| Issue | critical | ## Set hard cost limits |
-| Issue | critical | ## Test at scale before production |
-| Issue | high | ## Validate against ground truth |
-| Issue | high | ## Build robust API clients |
-| Issue | high | ## Least privilege principle |
-| Issue | medium | ## Track context usage |
-| Issue | medium | ## Structured logging |
-
-## Related Skills
-
-Works well with: `agent-tool-builder`, `agent-memory-systems`, `multi-agent-orchestration`, `agent-evaluation`

package/.agent/skills/skills/avalonia-layout-zafiro/SKILL.md

@@ -1,59 +0,0 @@
----
-name: avalonia-layout-zafiro
-description: Guidelines for modern Avalonia UI layout using Zafiro.Avalonia, emphasizing shared styles, generic components, and avoiding XAML redundancy.
-allowed-tools: Read, Write, Edit, Glob, Grep
----
-
-# Avalonia Layout with Zafiro.Avalonia
-
-> Master modern, clean, and maintainable Avalonia UI layouts.
-> **Focus on semantic containers, shared styles, and minimal XAML.**
-
-## 🎯 Selective Reading Rule
-
-**Read ONLY files relevant to the layout challenge!**
-
----
-
-## 📑 Content Map
-
-| File | Description | When to Read |
-|------|-------------|--------------|
-| `themes.md` | Theme organization and shared styles | Setting up or refining app themes |
-| `containers.md` | Semantic containers (`HeaderedContainer`, `EdgePanel`, `Card`) | Structuring views and layouts |
-| `icons.md` | Icon usage with `IconExtension` and `IconOptions` | Adding and customizing icons |
-| `behaviors.md` | `Xaml.Interaction.Behaviors` and avoiding Converters | Implementing complex interactions |
-| `components.md` | Generic components and avoiding nesting | Creating reusable UI elements |
-
----
-
-## 🔗 Related Project (Exemplary Implementation)
-
-For a real-world example, refer to the **Angor** project:
-`/mnt/fast/Repos/angor/src/Angor/Avalonia/Angor.Avalonia.sln`
-
----
-
-## ✅ Checklist for Clean Layouts
-
-- [ ] **Used semantic containers?** (e.g., `HeaderedContainer` instead of `Border` with manual header)
-- [ ] **Avoided redundant properties?** Use shared styles in `axaml` files.
-- [ ] **Minimized nesting?** Flatten layouts using `EdgePanel` or generic components.
-- [ ] **Icons via extension?** Use `{Icon fa-name}` and `IconOptions` for styling.
-- [ ] **Behaviors over code-behind?** Use `Interaction.Behaviors` for UI-logic.
-- [ ] **Avoided Converters?** Prefer ViewModel properties or Behaviors unless necessary.
-
----
-
-## ❌ Anti-Patterns
-
-**DON'T:**
-- Use hardcoded colors or sizes (literals) in views.
-- Create deep nesting of `Grid` and `StackPanel`.
-- Repeat visual properties across multiple elements (use Styles).
-- Use `IValueConverter` for simple logic that belongs in the ViewModel.
-
-**DO:**
-- Use `DynamicResource` for colors and brushes.
-- Extract repeated layouts into generic components.
-- Leverage `Zafiro.Avalonia` specific panels like `EdgePanel` for common UI patterns.

package/.agent/skills/skills/avalonia-layout-zafiro/behaviors.md

@@ -1,35 +0,0 @@
-# Interactions and Logic
-
-To keep XAML clean and maintainable, minimize logic in views and avoid excessive use of converters.
-
-## 🎭 Xaml.Interaction.Behaviors
-
-Use `Interaction.Behaviors` to handle UI-related logic that doesn't belong in the ViewModel, such as focus management, animations, or specialized event handling.
-
-```xml
-<TextBox Text="{Binding Address}">
-    <Interaction.Behaviors>
-        <UntouchedClassBehavior />
-    </Interaction.Behaviors>
-</TextBox>
-```
-
-### Why use Behaviors?
-- **Encapsulation**: UI logic is contained in a reusable behavior class.
-- **Clean XAML**: Avoids code-behind and complex XAML triggers.
-- **Testability**: Behaviors can be tested independently of the View.
-
-## 🚫 Avoiding Converters
-
-Converters often lead to "magical" logic hidden in XAML. Whenever possible, prefer:
-
-1.  **ViewModel Properties**: Let the ViewModel provide the final data format (e.g., a `string` formatted for display).
-2.  **MultiBinding**: Use for simple logic combinations (And/Or) directly in XAML.
-3.  **Behaviors**: For more complex interactions that involve state or events.
-
-### When to use Converters?
-Only use them when the conversion is purely visual and highly reusable across different contexts (e.g., `BoolToOpacityConverter`).
-
-## 🧩 Simplified Interactions
-
-If you find yourself needing a complex converter or behavior, consider if the component can be simplified or if the data model can be adjusted to make the view binding more direct.

package/.agent/skills/skills/avalonia-layout-zafiro/components.md

@@ -1,41 +0,0 @@
-# Building Generic Components
-
-Reducing nesting and complexity is achieved by breaking down views into generic, reusable components.
-
-## 🧊 Generic Components
-
-Instead of building large, complex views, extract recurring patterns into small `UserControl`s.
-
-### Example: A generic "Summary Item"
-Instead of repeating a `Grid` with labels and values:
-
-```xml
-<!-- ❌ BAD: Repeated Grid -->
-<Grid ColumnDefinitions="*,Auto">
-   <TextBlock Text="Total:" />
-   <TextBlock Grid.Column="1" Text="{Binding Total}" />
-</Grid>
-```
-
-Create a generic component (or use `EdgePanel` with a Style):
-
-```xml
-<!-- ✅ GOOD: Use a specialized control or style -->
-<EdgePanel StartContent="Total:" EndContent="{Binding Total}" Classes="SummaryItem" />
-```
-
-## 📉 Flattening Layouts
-
-Avoid deep nesting. Deeply nested XAML is hard to read and can impact performance.
-
-- **StackPanel vs Grid**: Use `StackPanel` (with `Spacing`) for simple linear layouts.
-- **EdgePanel**: Great for "Label - Value" or "Icon - Text - Action" rows.
-- **UniformGrid**: Use for grids where all cells are the same size.
-
-## 🔧 Component Granularity
-
-- **Atomical**: Small controls like custom buttons or icons.
-- **Molecular**: Groups of atoms like a `HeaderedContainer` with specific content.
-- **Organisms**: Higher-level sections of a page.
-
-Aim for components that are generic enough to be reused but specific enough to simplify the parent view significantly.

package/.agent/skills/skills/avalonia-layout-zafiro/containers.md

@@ -1,50 +0,0 @@
-# Semantic Containers
-
-Using the right container for the data type simplifies XAML and improves maintainability. `Zafiro.Avalonia` provides specialized controls for common layout patterns.
-
-## 📦 HeaderedContainer
-
-Prefer `HeaderedContainer` over a `Border` or `Grid` when a section needs a title or header.
-
-```xml
-<HeaderedContainer Header="Security Settings" Classes="WizardSection">
-    <StackPanel>
-        <!-- Content here -->
-    </StackPanel>
-</HeaderedContainer>
-```
-
-### Key Properties:
-- `Header`: The content or string for the header.
-- `HeaderBackground`: Brush for the header area.
-- `ContentPadding`: Padding for the content area.
-
-## ↔️ EdgePanel
-
-Use `EdgePanel` to position elements at the edges of a container without complex `Grid` definitions.
-
-```xml
-<EdgePanel StartContent="{Icon fa-wallet}" 
-           Content="Wallet Balance" 
-           EndContent="$1,234.00" />
-```
-
-### Slots:
-- `StartContent`: Aligned to the left (or beginning).
-- `Content`: Fills the remaining space in the middle.
-- `EndContent`: Aligned to the right (or end).
-
-## 📇 Card
-
-A simple container for grouping related information, often used inside `HeaderedContainer` or as a standalone element in a list.
-
-```xml
-<Card Header="Enter recipient address:">
-    <TextBox Text="{Binding Address}" />
-</Card>
-```
-
-## 📐 Best Practices
-
-- Use `Classes` to apply themed variants (e.g., `Classes="Section"`, `Classes="Highlight"`).
-- Customize internal parts of the containers using templates in your styles when necessary, rather than nesting more controls.

package/.agent/skills/skills/avalonia-layout-zafiro/icons.md

@@ -1,53 +0,0 @@
-# Icon Usage
-
-`Zafiro.Avalonia` simplifies icon management using a specialized markup extension and styling options.
-
-## 🛠️ IconExtension
-
-Use the `{Icon}` markup extension to easily include icons from libraries like FontAwesome.
-
-```xml
-<!-- Positional parameter -->
-<Button Content="{Icon fa-wallet}" />
-
-<!-- Named parameter -->
-<ContentControl Content="{Icon Source=fa-gear}" />
-```
-
-## 🎨 IconOptions
-
-`IconOptions` allows you to customize icons without manually wrapping them in other controls. It's often used in styles to provide a consistent look.
-
-```xml
-<Style Selector="HeaderedContainer /template/ ContentPresenter#Header EdgePanel /template/ ContentControl#StartContent">
-    <Setter Property="IconOptions.Size" Value="20" />
-    <Setter Property="IconOptions.Fill" Value="{DynamicResource Accent}" />
-    <Setter Property="IconOptions.Padding" Value="10" />
-    <Setter Property="IconOptions.CornerRadius" Value="10" />
-</Style>
-```
-
-### Common Properties:
-- `IconOptions.Size`: Sets the width and height of the icon.
-- `IconOptions.Fill`: The color/brush of the icon.
-- `IconOptions.Background`: Background brush for the icon container.
-- `IconOptions.Padding`: Padding inside the icon container.
-- `IconOptions.CornerRadius`: Corner radius if a background is used.
-
-## 📁 Shared Icon Resources
-
-Define icons as resources for reuse across the application.
-
-```xml
-<ResourceDictionary xmlns="https://github.com/avaloniaui">
-    <Icon x:Key="fa-wallet" Source="fa-wallet" />
-</ResourceDictionary>
-```
-
-Then use them with `StaticResource` if they are already defined:
-
-```xml
-<Button Content="{StaticResource fa-wallet}" />
-```
-
-However, the `{Icon ...}` extension is usually preferred for its brevity and ability to create new icon instances on the fly.

package/.agent/skills/skills/avalonia-layout-zafiro/themes.md

@@ -1,51 +0,0 @@
-# Theme Organization and Shared Styles
-
-Efficient theme organization is key to avoiding redundant XAML and ensuring visual consistency.
-
-## 🏗️ Structure
-
-Follow the pattern from Angor:
-
-1.  **Colors & Brushes**: Define in a dedicated `Colors.axaml`. Use `DynamicResource` to support theme switching.
-2.  **Styles**: Group styles by category (e.g., `Buttons.axaml`, `Containers.axaml`, `Typography.axaml`).
-3.  **App-wide Theme**: Aggregate all styles in a main `Theme.axaml`.
-
-## 🎨 Avoiding Redundancy
-
-Instead of setting properties directly on elements:
-
-```xml
-<!-- ❌ BAD: Redundant properties -->
-<HeaderedContainer CornerRadius="10" BorderThickness="1" BorderBrush="Blue" Background="LightBlue" />
-<HeaderedContainer CornerRadius="10" BorderThickness="1" BorderBrush="Blue" Background="LightBlue" />
-
-<!-- ✅ GOOD: Use Classes and Styles -->
-<HeaderedContainer Classes="BlueSection" />
-<HeaderedContainer Classes="BlueSection" />
-```
-
-Define the style in a shared `axaml` file:
-
-```xml
-<Style Selector="HeaderedContainer.BlueSection">
-    <Setter Property="CornerRadius" Value="10" />
-    <Setter Property="BorderThickness" Value="1" />
-    <Setter Property="BorderBrush" Value="{DynamicResource Accent}" />
-    <Setter Property="Background" Value="{DynamicResource SurfaceSubtle}" />
-</Style>
-```
-
-## 🧩 Shared Icons and Resources
-
-Centralize icon definitions and other shared resources in `Icons.axaml` and include them in the `MergedDictionaries` of your theme or `App.axaml`.
-
-```xml
-<Application.Resources>
-    <ResourceDictionary>
-        <ResourceDictionary.MergedDictionaries>
-            <MergeResourceInclude Source="UI/Themes/Styles/Containers.axaml" />
-            <MergeResourceInclude Source="UI/Shared/Resources/Icons.axaml" />
-        </ResourceDictionary.MergedDictionaries>
-    </ResourceDictionary>
-</Application.Resources>
-```

package/.agent/skills/skills/avalonia-viewmodels-zafiro/SKILL.md

@@ -1,29 +0,0 @@
----
-name: avalonia-viewmodels-zafiro
-description: Optimal ViewModel and Wizard creation patterns for Avalonia using Zafiro and ReactiveUI.
----
-
-# Avalonia ViewModels with Zafiro
-
-This skill provides a set of best practices and patterns for creating ViewModels, Wizards, and managing navigation in Avalonia applications, leveraging the power of **ReactiveUI** and the **Zafiro** toolkit.
-
-## Core Principles
-
-1.  **Functional-Reactive Approach**: Use ReactiveUI (`ReactiveObject`, `WhenAnyValue`, etc.) to handle state and logic.
-2.  **Enhanced Commands**: Utilize `IEnhancedCommand` for better command management, including progress reporting and name/text attributes.
-3.  **Wizard Pattern**: Implement complex flows using `SlimWizard` and `WizardBuilder` for a declarative and maintainable approach.
-4.  **Automatic Section Discovery**: Use the `[Section]` attribute to register and discover UI sections automatically.
-5.  **Clean Composition**: map ViewModels to Views using `DataTypeViewLocator` and manage dependencies in the `CompositionRoot`.
-
-## Guides
-
-- [ViewModels & Commands](viewmodels.md): Creating robust ViewModels and handling commands.
-- [Wizards & Flows](wizards.md): Building multi-step wizards with `SlimWizard`.
-- [Navigation & Sections](navigation_sections.md): Managing navigation and section-based UIs.
-- [Composition & Mapping](composition.md): Best practices for View-ViewModel wiring and DI.
-
-## Example Reference
-
-For real-world implementations, refer to the **Angor** project:
-- `CreateProjectFlowV2.cs`: Excellent example of complex Wizard building.
-- `HomeViewModel.cs`: Simple section ViewModel using functional-reactive commands.

package/.agent/skills/skills/avalonia-viewmodels-zafiro/composition.md

@@ -1,75 +0,0 @@
-# Composition & Mapping
-
-Ensuring your ViewModels are correctly instantiated and mapped to their corresponding Views is crucial for a maintainable application.
-
-## ViewModel-to-View Mapping
-
-Zafiro uses the `DataTypeViewLocator` to automatically map ViewModels to Views based on their data type.
-
-### Integration in App.axaml
-
-Register the `DataTypeViewLocator` in your application's data templates:
-
-```xml
-<Application.DataTemplates>
-    <DataTypeViewLocator />
-    <DataTemplateInclude Source="avares://Zafiro.Avalonia/DataTemplates.axaml" />
-</Application.DataTemplates>
-```
-
-### Registration
-
-Mappings can be registered globally or locally. Common practice in Zafiro projects is to use naming conventions or explicit registrations made by source generators.
-
-## Composition Root
-
-Use a central `CompositionRoot` to manage dependency injection and service registration.
-
-```csharp
-public static class CompositionRoot
-{
-    public static IShellViewModel CreateMainViewModel(Control topLevelView)
-    {
-        var services = new ServiceCollection();
-        
-        services
-            .AddViewModels()
-            .AddUIServices(topLevelView);
-            
-        var serviceProvider = services.BuildServiceProvider();
-        return serviceProvider.GetRequiredService<IShellViewModel>();
-    }
-}
-```
-
-### Registering ViewModels
-
-Register ViewModels with appropriate scopes (Transient, Scoped, or Singleton).
-
-```csharp
-public static IServiceCollection AddViewModels(this IServiceCollection services)
-{
-    return services
-        .AddTransient<IHomeSectionViewModel, HomeSectionSectionViewModel>()
-        .AddSingleton<IShellViewModel, ShellViewModel>();
-}
-```
-
-## View Injection
-
-Use the `Connect` helper (if available) or manual instantiation in `OnFrameworkInitializationCompleted`:
-
-```csharp
-public override void OnFrameworkInitializationCompleted()
-{
-    this.Connect(
-        () => new ShellView(),
-        view => CompositionRoot.CreateMainViewModel(view),
-        () => new MainWindow());
-
-    base.OnFrameworkInitializationCompleted();
-}
-```
-
-> [!TIP]
-> Use `ActivatorUtilities.CreateInstance` when you need to manually instantiate a class while still resolving its dependencies from the `IServiceProvider`.

package/.agent/skills/skills/avalonia-viewmodels-zafiro/navigation_sections.md

@@ -1,53 +0,0 @@
-# Navigation & Sections
-
-Zafiro provides powerful abstractions for managing application-wide navigation and modular UI sections.
-
-## Navigation with INavigator
-
-The `INavigator` interface is used to switch between different views or viewmodels.
-
-```csharp
-public class MyViewModel(INavigator navigator)
-{
-    public async Task GoToDetails()
-    {
-        await navigator.Navigate(() => new DetailsViewModel());
-    }
-}
-```
-
-## UI Sections
-
-Sections are modular parts of the UI (like tabs or sidebar items) that can be automatically registered.
-
-### The [Section] Attribute
-
-ViewModels intended to be sections should be marked with the `[Section]` attribute.
-
-```csharp
-[Section("Wallet", icon: "fa-wallet")]
-public class WalletSectionViewModel : IWalletSectionViewModel
-{
-    // ...
-}
-```
-
-### Automatic Registration
-
-In the `CompositionRoot`, sections can be automatically registered:
-
-```csharp
-services.AddAnnotatedSections(logger);
-services.AddSectionsFromAttributes(logger);
-```
-
-### Switching Sections
-
-You can switch the current active section via the `IShellViewModel`:
-
-```csharp
-shellViewModel.SetSection("Browse");
-```
-
-> [!IMPORTANT]
-> The `icon` parameter in the `[Section]` attribute supports FontAwesome icons (e.g., `fa-home`) when configured with `ProjektankerIconControlProvider`.

package/.agent/skills/skills/avalonia-viewmodels-zafiro/viewmodels.md

@@ -1,68 +0,0 @@
-# ViewModels & Commands
-
-In a Zafiro-based application, ViewModels should be functional, reactive, and resilient.
-
-## Reactive ViewModels
-
-Use `ReactiveObject` as the base class. Properties should be defined using the `[Reactive]` attribute (from ReactiveUI.SourceGenerators) for brevity.
-
-```csharp
-public partial class MyViewModel : ReactiveObject
-{
-    [Reactive] private string name;
-    [Reactive] private bool isBusy;
-}
-```
-
-### Observation and Transformation
-
-Use `WhenAnyValue` to react to property changes:
-
-```csharp
-this.WhenAnyValue(x => x.Name)
-    .Select(name => !string.IsNullOrEmpty(name))
-    .ToPropertyEx(this, x => x.CanSubmit);
-```
-
-## Enhanced Commands
-
-Zafiro uses `IEnhancedCommand`, which extends `ICommand` and `IReactiveCommand` with additional metadata like `Name` and `Text`.
-
-### Creating a Command
-
-Use `ReactiveCommand.Create` or `ReactiveCommand.CreateFromTask` and then `Enhance()` it.
-
-```csharp
-public IEnhancedCommand Submit { get; }
-
-public MyViewModel()
-{
-    Submit = ReactiveCommand.CreateFromTask(OnSubmit, canSubmit)
-        .Enhance(text: "Submit Data", name: "SubmitCommand");
-}
-```
-
-### Error Handling
-
-Use `HandleErrorsWith` to automatically channel command errors to the `NotificationService`.
-
-```csharp
-Submit.HandleErrorsWith(uiServices.NotificationService, "Submission Failed")
-    .DisposeWith(disposable);
-```
-
-## Disposables
-
-Always use a `CompositeDisposable` to manage subscriptions and command lifetimes.
-
-```csharp
-public class MyViewModel : ReactiveObject, IDisposable
-{
-    private readonly CompositeDisposable disposables = new();
-
-    public void Dispose() => disposables.Dispose();
-}
-```
-
-> [!TIP]
-> Use `.DisposeWith(disposables)` on any observable subscription or command to ensure proper cleanup.

package/.agent/skills/skills/avalonia-viewmodels-zafiro/wizards.md

@@ -1,47 +0,0 @@
-# Wizards & Flows
-
-Complex multi-step processes are handled using the `SlimWizard` pattern. This provides a declarative way to define steps, navigation logic, and final results.
-
-## Defining a Wizard
-
-Use `WizardBuilder` to define the steps. Each step corresponds to a ViewModel.
-
-```csharp
-SlimWizard<string> wizard = WizardBuilder
-    .StartWith(() => new Step1ViewModel(data))
-        .NextUnit()
-        .WhenValid()
-    .Then(prevResult => new Step2ViewModel(prevResult))
-        .NextCommand(vm => vm.CustomNextCommand)
-    .Then(result => new SuccessViewModel("Done!"))
-        .Next((_, s) => s, "Finish")
-    .WithCompletionFinalStep();
-```
-
-### Navigation Rules
-
-- **NextUnit()**: Advances when a simple signal is emitted.
-- **NextCommand()**: Advances when a specific command in the ViewModel execution successfully.
-- **WhenValid()**: Wait until the current ViewModel's validation passes before allowing navigation.
-- **Always()**: Navigation is always allowed.
-
-## Navigation Integration
-
-The wizard is navigated using an `INavigator`:
-
-```csharp
-public async Task CreateSomething()
-{
-    var wizard = BuildWizard();
-    var result = await wizard.Navigate(navigator);
-    // Handle result
-}
-```
-
-## Step Configuration
-
-- **WithCompletionFinalStep()**: Marks the wizard as finished when the last step completes.
-- **WithCommitFinalStep()**: Typically used for wizards that perform a final "Save" or "Deploy" action.
-
-> [!NOTE]
-> The `SlimWizard` handles the "Back" command automatically, providing a consistent user experience across different flows.

package/.agent/skills/skills/avalonia-zafiro-development/SKILL.md

@@ -1,29 +0,0 @@
----
-name: avalonia-zafiro-development
-description: Mandatory skills, conventions, and behavioral rules for Avalonia UI development using the Zafiro toolkit.
----
-
-# Avalonia Zafiro Development
-
-This skill defines the mandatory conventions and behavioral rules for developing cross-platform applications with Avalonia UI and the Zafiro toolkit. These rules prioritize maintainability, correctness, and a functional-reactive approach.
-
-## Core Pillars
-
-1.  **Functional-Reactive MVVM**: Pure MVVM logic using DynamicData and ReactiveUI.
-2.  **Safety & Predictability**: Explicit error handling with `Result` types and avoidance of exceptions for flow control.
-3.  **Cross-Platform Excellence**: Strictly Avalonia-independent ViewModels and composition-over-inheritance.
-4.  **Zafiro First**: Leverage existing Zafiro abstractions and helpers to avoid redundancy.
-
-## Guides
-
-- [Core Technical Skills & Architecture](core-technical-skills.md): Fundamental skills and architectural principles.
-- [Naming & Coding Standards](naming-standards.md): Rules for naming, fields, and error handling.
-- [Avalonia, Zafiro & Reactive Rules](avalonia-reactive-rules.md): Specific guidelines for UI, Zafiro integration, and DynamicData pipelines.
-- [Zafiro Shortcuts](zafiro-shortcuts.md): Concise mappings for common Rx/Zafiro operations.
-- [Common Patterns](patterns.md): Advanced patterns like `RefreshableCollection` and Validation.
-
-## Procedure Before Writing Code
-
-1.  **Search First**: Search the codebase for similar implementations or existing Zafiro helpers.
-2.  **Reusable Extensions**: If a helper is missing, propose a new reusable extension method instead of inlining complex logic.
-3.  **Reactive Pipelines**: Ensure DynamicData operators are used instead of plain Rx where applicable.