guitarrapc/dotfiles-win

adversarial-audit

外部から状態を復元できる入口（URL/クエリ、設定ファイル、API 引数、CLI 引数、環境変数、localStorage 等の永続ストレージ）を格子状に地図化し、並列レーンで仮説を形成 → 独立した反証で潰す → 生き残りだけを実機確認 → 常時確認が必要なものをユニットテストへ格上げする監査工程。「攻撃面を洗い出したい」「この入口から何ができるか網羅的に調べたい」「入力の堅牢性を監査したい」「仮説を立てて反証したい」「見つかった不変条件をテストにしたい」といった依頼で必ず使う。単発のバグ調査やコードレビューでは…

Source text: Japanese

dotnet-best-practices

Ensure .NET/C# code meets best practices for the solution/project.

dotnet-micro-optimization

Benchmark-driven micro-optimization loop: find the fastest implementation of a hot function by measuring one-hypothesis-per-variant implementations under a benchmark harness, reading JIT/native disassembly to explain the numbers, and iterating until…

dotnet-performance-discipline

Standing rules for writing allocation-conscious, high-performance C#/.NET. Covers pooled-buffer ownership (who may hold an ArrayPool rental, and what may cross an API boundary), choosing between Span/Memory/array, stackalloc byte budgets, zero-copy UTF-8 and…

seiton

Lint and fix GitHub Actions workflow files and action metadata files using seiton CLI.

code-review

Adversarial multi-agent review for implementation changes. Reviews correctness, performance, API usability, test coverage (including equivalence classes and negative cases), and spec/doc synchronization in parallel; tries to refute top claims before reporting…

document-spec-policy

Policy for reading and writing specification documents under `.github/docs/`. Covers what belongs in specs (WHAT, WHY, lessons learned), what does not (detailed HOW), post-implementation updates, and cross-document consistency rules between parser specs and…