その他のスキル

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.

日本語の概要は準備中です。原文の説明を表示しています。

Detects MSBuild projects with conflicting OutputPath or IntermediateOutputPath. USE FOR: builds failing with 'Cannot create a file when that file already exists', 'The process cannot access the file because it is being used by another process', intermittent build failures that succeed on retry, or missing/overwritten outputs in multi-project or multi-targeting builds where bin/obj (or project.assets.json) collide. Common causes: shared OutputPath, missing AppendTargetFrameworkToOutputPath, extra global properties (e.g. PublishReadyToRun), or SetTargetFramework on a ProjectReference to a single-targeting project. DO NOT USE FOR: file access errors unrelated to MSBuild (OS-level locking), single-project single-TFM builds, non-MSBuild build systems.

日本語の概要は準備中です。原文の説明を表示しています。

Choosing an MSBuild CopyToOutputDirectory / CopyToPublishDirectory mode: Never, PreserveNewest, Always, and IfDifferent (MSBuild 17.13+), plus $(SkipUnchangedFilesOnCopyAlways). USE FOR: removing the per-build Always copy perf hit; resetting output files mutated between builds. DO NOT USE FOR: general incremental-build diagnosis (use incremental-build); non-MSBuild build systems.

日本語の概要は準備中です。原文の説明を表示しています。

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).

日本語の概要は準備中です。原文の説明を表示しています。

Addresses all review comments on a PR automatically. Escalates genuine human decisions. Use when asked to /pr-merge-ready, create and babysit a PR, batch-fix PR comments, or address review feedback quickly.

日本語の概要は準備中です。原文の説明を表示しています。

Install, configure, update, or upgrade vendored anti-slop Oxlint plugins. Use when adding anti-slop, picking up upstream rules or fixes, or migrating an existing installation while preserving local customizations.

日本語の概要は準備中です。原文の説明を表示しています。

Cross-platform path handling and command patterns

日本語の概要は準備中です。原文の説明を表示しています。

Shifts Layer 3 model selection to cost-optimized alternatives when economy mode is active.

日本語の概要は準備中です。原文の説明を表示しています。

Never read .env files or write secrets to .squad/ committed files

日本語の概要は準備中です。原文の説明を表示しています。

The complete file-by-file source-of-truth hierarchy for Squad: which files are authoritative, which are derived/append-only, who may write each one, who may read each one, and the precedence rules when they conflict. Squad coordinator loads this on demand when it needs to resolve a write conflict, decide where a piece of state belongs, or answer a 'who owns this file' question.

日本語の概要は準備中です。原文の説明を表示しています。

The complete two-phase Init Mode protocol the Squad coordinator runs when no team exists yet in the current repo. Phase 1 = propose the team (no files created, wait for user confirm). Phase 2 = create .squad/ scaffolding, casting state, .gitattributes for merge drivers, and the always-on built-ins (Scribe, Ralph, Rai, Fact Checker). Loaded on demand when the coordinator detects no .squad/team.md exists.

日本語の概要は準備中です。原文の説明を表示しています。

Context hygiene — compress, prune, archive .squad/ state

日本語の概要は準備中です。原文の説明を表示しています。

Standard collaboration patterns for all squad agents — worktree awareness, decisions, cross-agent communication

日本語の概要は準備中です。原文の説明を表示しています。

Team initialization flow (Phase 1 proposal + Phase 2 creation)

日本語の概要は準備中です。原文の説明を表示しています。

Standard recovery patterns for all squad agents. When something fails, adapt — don't just report the failure.

日本語の概要は準備中です。原文の説明を表示しています。

Pre-release validation, npm publish procedures, and post-publish verification

日本語の概要は準備中です。原文の説明を表示しています。

Shared hard rules enforced across all squad agents

日本語の概要は準備中です。原文の説明を表示しています。

Add temporary ID support to safe-output jobs end to end.

日本語の概要は準備中です。原文の説明を表示しています。

Categorized catalog of common Squad operations. Coordinator reads this file and presents it as an interactive menu when the user asks for available commands or help.

日本語の概要は準備中です。原文の説明を表示しています。

Route agent notifications to specific channels by type — prevent alert fatigue from single-channel flooding

日本語の概要は準備中です。原文の説明を表示しています。

Coordinating work across multiple Squad instances — discovery, delegation, and disambiguation when the user says 'squad' (the product) vs casual English 'group of agents'.

日本語の概要は準備中です。原文の説明を表示しています。

Three-tier agent memory model (hot/cold/wiki) for context reduction per spawn

日本語の概要は準備中です。原文の説明を表示しています。

Teaches agents to reply to PR review comment threads after fixing issues, making resolutions traceable

日本語の概要は準備中です。原文の説明を表示しています。

Tone enforcement patterns for external-facing community responses

日本語の概要は準備中です。原文の説明を表示しています。