erbatista
- 6 skills
- 0 followers
- 3 hours ago last updated
- ▌ Feature Development · erbatistaImplement new C#/.NET/WPF features using the repository's existing architecture, patterns, tests, and build conventions. Use for new capabilities, user stories, enhancements, commands, views, ViewModels, services, workflows, and feature extensions; do not use for defect-first investigations where the primary task is diagnosing existing incorrect behavior.
- ▌ Blazor · erbatista bundleRepository conventions, build/test commands, and framework pitfalls for Blazor codebases - .NET solutions with .razor components, Razor class libraries, Blazor Server or WebAssembly, and interactive render modes. Load whenever working in a Blazor project, and whenever feature-development or bug-fixing routes here in their stack-detection step. Not for WPF or non-.NET projects.
- ▌ Bug Fixing 2 · erbatista bundleDiagnose and fix existing defects in any codebase by reproducing the problem, establishing root cause with evidence, adding regression coverage when practical, and applying the smallest safe correction. Use for crashes, exceptions, incorrect results, regressions, intermittent failures, state and concurrency bugs, UI that does not update, and production incidents, even when the user only says "this doesn't work". Language-agnostic; detects the stack and loads the matching stack skill (dotnet-wpf, blazor) for framework-specific investigation and validation. Do not use as the primary workflow for net-new feature development; use feature-development for that.
- ▌ Dotnet Wpf · erbatista bundleRepository conventions, build/test commands, and framework pitfalls for C#/.NET/WPF codebases - solutions with .sln/.csproj and UseWPF, XAML views, ViewModels, MVVM, commands, bindings, and dispatcher/UI-thread work. Load whenever working in a .NET/WPF repository, and whenever feature-development or bug-fixing routes here in their stack-detection step. Not for Blazor, ASP.NET, or non-.NET projects.
- ▌ Feature Development 2 · erbatista bundleImplement new features, user stories, enhancements, commands, views, services, endpoints, and workflow extensions in any codebase, using the repository's existing architecture, patterns, tests, and build conventions. Use whenever the task is to add, build, implement, extend, or support new behavior, even when the word "feature" is not used. Language-agnostic; detects the stack and loads the matching stack skill (dotnet-wpf, blazor) for conventions and validation commands. Do not use when the primary task is diagnosing existing incorrect behavior; use bug-fixing for that.
- ▌ Bug Fixing · erbatistaDiagnose and fix existing C#/.NET/WPF defects by reproducing the problem, establishing root cause, protecting the defect with regression coverage when practical, and applying the smallest safe correction. Use for crashes, incorrect behavior, binding failures, threading issues, state bugs, regressions, exceptions, and production defects; do not use as the primary workflow for net-new feature development.