Menu
SkillsMP has collected 15 skills from Cholopol/dot-pudica-framework. Open a skill to review its source and details.
Showing 15 of 15 collected skills.
Set up or verify the DotPudica framework inside a Godot .NET project: enabling the plugin, checking the injected csproj snippet, creating the AppContext bootstrap node (Initialize/Dispose), wiring GodotWindowManager. Use whenever the project has no bootstrap…
Register and consume services with DotPudica: AppContext configureServices callbacks (AddSingleton/AddTransient), [Inject] fields, [ViewModelFactory] methods, and SceneContextHost scene-level scopes with Operations cancellation tokens. Use when sharing data…
Wire communication and threading with DotPudica: [Subscribe] to ViewModel events, MessageBus weak/strong messaging, InteractionRequest for ViewModel-to-View requests, IUiDispatcher.Post, LatestSnapshotMailbox, and SceneOperationScope cancellation. Use for…
Add object pooling to DotPudica views, windows, and item lists: [DotPudicaView(Pooled = true)] with RecycleView, NodePool.Create/Allocate/Free, GodotWindowManager.ConfigurePool/ShowPooled, and [ItemsSource] PoolSize. Use when panels or popups are created and…
Verify and fix DotPudica code: run dotnet build, interpret DOTPUDICA* diagnostics (001/005/010/030-036/040-043/045/046), inspect generated .Bindings.g.cs output, and apply the framework's common-pitfall fixes. Use at the end of every task that wrote framework…
Create DotPudica View + ViewModel pairs with declarative bindings: [DotPudicaView], [BindTo], [BindCommand], [ItemsSource], [Inject], [Subscribe], [ViewModelFactory], lifecycle hooks and the mandatory _Ready/_ExitTree lines. Use whenever the user wants a UI…
Build window stacks and popups with DotPudica: GodotWindowManager node placement, GodotWindow subclasses, WindowType selection (Full/Popup/QueuedPopup/Dialog/Progress), Show/Hide/Dismiss calls, and Bundle data passing. Use whenever the user wants full-screen…
Entry point for any task involving the DotPudica MVVM framework (Godot .NET): creating UI pages, bindings, commands, item lists, windows or popups, shared services, scene scopes, object pooling, or fixing DOTPUDICA compile diagnostics. Consult this routing…
End-to-end workflow: deliver a complete new UI page (settings, inventory, menu, any panel) with ViewModel, View, bindings, commands, optional item lists, and verification. The most common workflow - use whenever the user describes a page or panel they want to…
End-to-end workflow: deliver a popup, dialog, or full-screen page with the DotPudica window manager - window class, WindowType decision, Show/Dismiss calls, Bundle data passing, and verification. Use when the user wants a popup, confirm dialog, notification,…
End-to-end workflow: fix DOTPUDICA* compile diagnostics - collect the build output, map each ID to its root cause (references/diagnostics.md), apply the fix, rebuild until clean, then re-run the original task's acceptance checks. Use whenever a build fails…
End-to-end workflow: optimize frequently opened and closed panels and popups with DotPudica pooling - decide the mode (pooled view / pooled window / ItemsSource PoolSize), apply [DotPudicaView(Pooled = true)] or ConfigurePool/ShowPooled, and verify the…
End-to-end workflow: integrate DotPudica into a new Godot .NET project from scratch - enable the plugin, check the csproj injection, create the AppContext bootstrap, build a first minimal page, and verify. Use when starting a new project or when a project has…
End-to-end workflow: deliver scene-isolated DI and leave-scene cancellation with SceneContextHost - mount the host, register transient services, create ViewModels from host.Scope, pass Operations tokens to async work, and verify. Use for rooms, matchmaking,…
End-to-end workflow: deliver cross-page shared state with DotPudica singleton services - design the service interface, register it in AppContext, inject it into pages, and verify. Use when the user wants data shared between pages (player profile, inventory,…