Use devtools-utils factory functions to create per-framework plugin adapters. createReactPlugin/createSolidPlugin/createVuePlugin/createPreactPlugin, createReactPanel/createSolidPanel/createVuePanel/createPreactPanel. [Plugin, NoOpPlugin] tuple for tree-shaking. DevtoolsPanelProps (theme). Vue uses (name, component) not options object. Solid render must be function.
Reference guide for Forms controls — classes inheriting from FrameworkElement. Load this when working on Button, CheckBox, ListBox, ComboBox, TextBox, ScrollViewer, or any class in Gum.Forms.Controls (or FlatRedBall.Forms.Controls). Also load when working on FrameworkElement itself, the Visual/InteractiveGue relationship, state machines, DefaultVisuals, or ReactToVisualChanged.
Reference guide for how Gum applies variables and sets properties on renderables. Load this when working on ApplyState, SetProperty, SetVariablesRecursively, CustomSetPropertyOnRenderable, font loading, IsAllLayoutSuspended, or isFontDirty.
Reference guide for Gum's runtime data binding system — BindingContext, SetBinding on both GraphicalUiElement visuals and FrameworkElement Forms controls, binding types (string, Binding object, lambda), and how the two systems differ.
Create a conversation practice chat MulmoScript with speech bubble UI and character illustration (voiceover approach). Use when the user wants to create English conversation practice content.
Create a vocabulary learning chat MulmoScript with messenger-style animated UI (voiceover approach). Use when the user wants to create vocabulary learning content.
Reference guide for Gum's runtime font loading system in MonoGame/KNI — the three font loading paths (custom font, font-property cache lookup, in-memory generation), the lookup cascade, FontCache naming, and common gotchas. Load when working on TextRuntime font properties, BitmapFont loading, CustomSetPropertyOnRenderable.UpdateToFontValues, IInMemoryFontCreator, or font-related documentation.
Install TanStack Devtools, pick framework adapter (React/Vue/Solid/Preact), register plugins via plugins prop, configure shell (position, hotkeys, theme, hideUntilHover, requireUrlFlag, eventBusConfig). TanStackDevtools component, defaultOpen, localStorage persistence.
Bump the NuGet package versions for all 12 Gum projects (11 libraries + GumCli). Queries NuGet to check if a version exists for today, then sets the new version to YYYY.M.D.V where V increments from the latest published version today (or starts at 1). Creates a release branch named ReleaseCode_YYYY_M_D_V, commits the changes, and pushes. Run this before triggering the nuget release workflow.
Publish plugin to npm and submit to TanStack Devtools Marketplace. PluginMetadata registry format, plugin-registry.ts, pluginImport (importName, type), requires (packageName, minVersion), framework tagging, multi-framework submissions, featured plugins.
在使用 MCP 做前端 JavaScript 逆向时使用，适用于签名链路定位、页面观察取证、本地补环境复现、VMP 类插桩分析、AST 去混淆与证据化输出。
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
Extracts duplicated properties, methods, and logic from sibling Blazor components into a shared intermediate base class. Covers identification of duplicated surfaces, base class creation, member migration, and @inherits directive updates. Use when three or more components share copy-pasted Parameter declarations, consolidating shared helper methods, or refactoring component inheritance hierarchies.
Defines the file location, page structure, content guidelines, and navigation update requirements for creating component sample and demo pages in the AfterBlazorServerSide sample app. Use when adding a new BWFC component sample page, updating NavMenu.razor or ComponentList.razor navigation, writing demo sections with escaped code blocks, or ensuring consistent sample page conventions across the project.
How to migrate ASP.NET Web Forms themes (App_Themes) to Blazor using BWFC auto-discovery
Provides a step-by-step workflow for creating Blazor components that emulate ASP.NET Web Forms controls in the BlazorWebFormsComponents library. Covers base class selection (BaseWebFormsComponent, BaseStyledComponent, DataBoundComponent, BaseValidator), Web Forms property and event naming conventions, Playwright integration testing setup, and the complete checklist from component creation through documentation and navigation updates. Use when implementing a new BWFC component, choosing the correct base class for a control type, adding unit or integration tests, or extending an existing component with new Web Forms property support.
Upgrades a Blazor component from BaseWebFormsComponent to BaseStyledComponent to gain IStyle properties like BackColor, CssClass, Font, and dimensions. Walks through base class changes, @inherits directives, style application, and duplicate property removal. Use when a component needs inline styling support, adding CSS class parameters, or migrating Web Forms style attributes to Blazor components.
Adds dual EventCallback parameter aliases (bare and On-prefixed) to Blazor components for Web Forms migration compatibility. Guides creation of EventArgs classes, coalescing invocation patterns, and HasDelegate guard checks. Use when adding new event parameters to a BWFC component, implementing Web Forms event naming conventions, or migrating ASP.NET Web Forms event handlers to Blazor.
Provides workaround patterns for Blazor Server enhanced navigation silently stripping onclick attributes from button elements, causing form submissions to fail. Covers anchor-based form submission for HTTP POST endpoints and EditForm for in-component handling. Use when a form submit button does nothing on click, when building auth forms that POST to minimal API endpoints, or when choosing between HTML form POST and Blazor EditForm for data entry pages.
Provides patterns for automated HTML fidelity comparison between ASP.NET Web Forms controls and their BWFC Blazor equivalents using Playwright. Covers marker-based control isolation with data-audit attributes, HTML normalization rules for stripping ViewState and naming-container IDs, and control classification by audit feasibility (Clean, Structural, JS-coupled, Divergent). Use when validating migration output fidelity, setting up Playwright-based HTML comparison tests, building an intentional divergence registry, or auditing whether migrated Blazor components render equivalent DOM structure.
Angular core patterns: standalone components, signals, inject, control flow, zoneless. Trigger: When creating Angular components, using signals, or setting up zoneless.
Angular forms: Signal Forms (experimental) and Reactive Forms. Trigger: When working with forms, validation, or form state in Angular.
Angular architecture: Scope Rule, project structure, file naming, style guide. Trigger: When structuring Angular projects or deciding where to place components.
