37건 · 관련도순
Configure login state and access rules in Blazor Web Apps. Accounts for server and browser rendering, protects pages by role or policy, and helps diagnose missing authentication state or errors on Identity pages.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Helps compile Rust and C into WebAssembly for browsers and servers. Covers JavaScript integration, WASI interfaces for accessing system resources, typed component connections, and practical ways to tune binary size, execution speed, and memory use.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Integrate RuView through shell commands, an HTTP API, or WebAssembly builds, which run compiled code in browsers and supported edge devices. Covers survivor scan commands, result exports, API hosting, and browser or ESP32 deployment paths.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Create and manage agents in WebAssembly, an execution environment that keeps their work isolated. Try untrusted code or agent configurations, manage sandbox files and tool access, and export agents for sharing.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Find prebuilt WASM agents, software components packaged in WebAssembly format, through gallery browsing and keyword search. Install agents from their configurations, or export and publish your own agents to share with the community.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Convert an older Blazor Server app into a .NET 8+ Blazor Web App while preserving interactive server behavior. It guides changes to page structure, startup configuration, authentication state sharing, and validation of the converted app.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Fix Blazor issues during prerendering, when the server sends initial HTML before interactive features load. Preserve component state to avoid repeated data requests and flicker, handle unavailable services, and configure prerendering or page routing where needed.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Share shopping carts, themes, and other state across Blazor components that are not directly connected. Choose cascading values or shared services, notify components when data changes, and account for rendering boundaries and service lifetimes.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Guides conversion of a pre-.NET 8 Blazor Server app into a .NET 8+ Blazor Web App. USE FOR: migrating apps that use AddServerSideBlazor and MapBlazorHub to the AddRazorComponents/MapRazorComponents model, converting _Host.cshtml to an App.razor root component, replacing blazor.server.js with blazor.web.js, migrating CascadingAuthenticationState to a service, adopting new Blazor Web App features like enhanced navigation and streaming rendering. DO NOT USE FOR: apps that are already Blazor Web Apps (already use AddRazorComponents and MapRazorComponents), Blazor WebAssembly or hosted Blazor WebAssembly apps (different migration path), apps that should stay on the Blazor Server hosting model without converting, or apps still targeting .NET Framework.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build cross-platform .NET applications with Uno Platform targeting WebAssembly, iOS, Android, macOS, Linux, and Windows from a single XAML/C# codebase. USE FOR: building cross-platform apps from a single C# and XAML codebase; targeting WebAssembly, iOS, Android, macOS, Linux, and Windows simultaneously; migrating WPF or UWP. DO NOT USE FOR: unrelated stacks; generic tasks that do not need this specific guidance. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build and review Blazor applications across server, WebAssembly, web app, and hybrid scenarios with correct component design, state flow, rendering, and hosting choices. USE FOR: building interactive web UIs with C# instead of JavaScript; choosing between Server, WebAssembly, or Auto render modes; designing component hierarchies and state. DO NOT USE FOR: unrelated stacks; generic tasks that do not need this specific guidance. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Expert guide for WebAssembly (WASM) and Edge Computing. Covers WASI preview 2, Spin/Fermyon, Cloudflare Workers WASM, and high-performance browser computing / Panduan ahli untuk WebAssembly (WASM) dan Edge Computing. Mencakup WASI preview 2, Spin/Fermyon, Cloudflare Workers WASM, dan komputasi performa tinggi di browser.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Expert guide for ephemeral WebAssembly (WASM) and isolated micro-runtime sandboxes to securely execute AI-generated code, validate database migrations in-memory, and perform sub-millisecond fuzzing / Panduan ahli sandbox WebAssembly (WASM) efemeral dan micro-runtime terisolasi untuk eksekusi kode AI yang aman, validasi migrasi database in-memory, dan fuzzing sub-milidetik.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Expert en edge computing v2 (CDN, edge functions, WebAssembly, IoT gateway, contexte DZ)
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create a new ASP.NET Core web application or web site using Blazor. USE FOR: creating a new Blazor web app, scaffolding a new web project, starting a new web site, choosing render modes (Static SSR, Interactive Server, Interactive WebAssembly, Auto), running dotnet new blazor with the right options, setting up initial project structure. DO NOT USE FOR: adding features to existing projects, changing how an existing app renders, or component authoring (use author-component).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Call APIs, load data into components, and handle the async lifecycle in Blazor. USE FOR fetching data from a backend, submitting data to an API, displaying loading/error states, registering HttpClient, building service abstractions for Auto/WebAssembly render modes. DO NOT USE for form validation (see collect-user-input), prerendering persistence (see support-prerendering), or project scaffolding (see create-blazor-project).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build Blazor forms, search boxes, and input controls with validation and submission handling. The skill covers file uploads and explains which form patterns apply to interactive pages and pages rendered on the server.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Build, run, debug and ship 3D city games in Godot 4 — procedurally generated cities (block grids, districts, weighted building typologies, MultiMesh batching, facade shaders, terrain, day/night, landmarks), first-person controllers, headless verification, Blender-generated .glb assets, rigged character and animation packs, real OpenStreetMap-derived cities, WebAssembly export, and cloud GPU streaming on GCP. Use this skill whenever the work involves Godot or a .gd/.tscn/.gdshader/project.godot file; whenever someone wants to start, set up, clone onto a new machine, or stand up a 3D game or city generator; whenever they mention procedural city, city generator, block grid, building typology, MultiMesh, facade shader, terrain heightmap, navmesh, Godot export templates, export presets, headless Godot, .glb pipeline, Blender asset generation, character rigs or borrowed animations; and whenever they want to deploy or share a game — web export, SharedArrayBuffer/COOP/COEP, Selkies, pixel streaming, GPU VM, or "let people play this without installing anything." Reach for it even on vague asks like "get this running", "why is my city slow", "my model faces backwards", "make it work on a cloud machine", or "set this up somewhere else too" when a Godot 3D project is in play.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Write UI tests for Blazor applications (Server or WebAssembly) using Playwright. Covers navigation, interaction, authentication, selectors, and common Blazor-specific patterns.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use Chrome DevTools MCP from .NET agents and .NET-focused repos to inspect, debug, and automate Chrome through an MCP client. USE FOR: the repo needs browser-level debugging for ASP.NET Core, Blazor, WebAssembly, or any .NET app with a web UI; the user wants an MCP server that can inspect console. DO NOT USE FOR: pure .NET code analysis, unit testing, or NuGet/package management; static HTML linting alone. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Call APIs, load data into components, and handle the async lifecycle in Blazor. USE FOR fetching data from a backend, submitting data to an API, displaying loading/error states, registering HttpClient, building service abstractions for Auto/WebAssembly render modes. DO NOT USE for form validation (see collect-user-input), prerendering persistence (see support-prerendering), or project scaffolding (see create-blazor-project).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create a new ASP.NET Core web application or web site using Blazor. USE FOR: creating a new Blazor web app, scaffolding a new web project, starting a new web site, choosing render modes (Static SSR, Interactive Server, Interactive WebAssembly, Auto), running dotnet new blazor with the right options, setting up initial project structure. DO NOT USE FOR: adding features to existing projects, changing how an existing app renders, or component authoring (use author-component).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Add authentication and authorization to a Blazor Web App, accounting for the app's render mode. USE WHEN the user needs [Authorize] on pages, AuthorizeView, role or policy-based access, login/logout Identity pages, or AuthenticationStateProvider. Also USE WHEN auth state is null after WebAssembly loads, SignInManager throws in an interactive component, NotAuthorized content never renders in static SSR, or HttpContext.User is null in an interactive component. DO NOT USE for general component authoring (see author-component), for prerendering concerns unrelated to auth (see support-prerendering), or for managing non-auth cascading state (see coordinate-components).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Share state between components that don't have a direct parent-child parameter relationship, using cascading values, scoped services with change events, or CascadingValueSource via DI. USE WHEN the user needs a CascadingParameter or CascadingValue that works across render mode boundaries, a shopping cart or notification count accessible from multiple pages, a theme or user preference cascaded app-wide, or when components in different parts of the tree must react when shared data changes. Also USE WHEN cascading values aren't reaching interactive children in per-page interactivity mode, or when the user needs to understand scoped vs singleton service lifetime for state on Blazor Server. DO NOT USE for direct parent-child parameter passing or EventCallback (see author-component), for persisting state across prerender-to-interactive transitions (see support-prerendering), or for service abstractions for data fetching in Auto/WebAssembly (see fetch-and-send-data).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.