S4RCIV

Writes a blameless incident postmortem for the s4rCiv project in Japanese, grounded in the real timeline, commits, and logs (never speculation). Use when the user says "ポストモーテム書いて" / "障害報告書いて" / "事後検証" / "incident report" / "RCA" / "根本原因", or after an incident, outage, data-integrity scare, or a committed bug fix worth a durable record. Authoring only — no deploy.

Go ベストプラクティス。Go コードの品質を保つための規約とパターン集。

Python ベストプラクティス。Python コードの品質を保つための規約とレビュー観点（Python 3.14+）。

Rust ベストプラクティス。Rust コードの品質を保つための規約とパターン集（Edition 2024）。

Svelte 5 & SvelteKit ベストプラクティス。Svelte 5 Runes ベースのコンポーネント設計規約。

TypeScript ベストプラクティス。型安全性とコード品質を保つための規約。

Clean Architecture layer patterns (Handler → Usecase → Port → Gateway → Driver), mapped to s4rCiv's adapter model and observation/interpretation plane separation. Use when implementing or reviewing layered backend code (source adapters, normalizer, read models, CQRS).

Docker Compose command reference for the s4rCiv local stack (root compose.yaml, project name s4rciv). Services: db (Postgres), migrate (Atlas), api (Go), differ (Rust), web (SvelteKit). Use when running, restarting, or inspecting s4rCiv containers locally, or applying migrations.

Audits code, schema, and migrations for violations of immutable data-model invariants: append-first event log, reproject-safe projectors, disposable read models, versioned artifacts, merge-safe upserts, and no business-fact `time.Now()`. Use when changing migrations, projectors, event handlers, append-only stores, or any read model derived from events; or when the user mentions "イミュータブル", "event sourcing", "projector", "reproject", "append-only", "projection", "read model", or kawasima's resource/event modeling.

Writes an Architecture Decision Record for the s4rCiv project in Japanese after a decision or completed implementation. Authoring only — no deploy / no Pact / no container rebuild (s4rCiv has no deploy infra yet). Trigger when the user says "ADR書いて" / "ADRにまとめて" / "ADRに記録して" / "docs/ADR" 関連のまとめ依頼, or after a change that clearly warrants a decision record.

Audits code for security vulnerabilities using OWASP Top 10:2025, OWASP ASVS 5.0, the OWASP Secure Code Review Cheat Sheet, and (for AI/agentic code paths) the OWASP Top 10 for Agentic Applications 2026 as authoritative sources. Produces a structured findings report with severity, OWASP/CWE mapping, evidence, and concrete remediation. Use when the user asks for "security review", "脆弱性チェック", "セキュリティ監査", "OWASP レビュー", threat-modeling a diff/module, or when a change touches authentication, authorization, crypto, input validation, deserialization, file upload, SQL/NoSQL/command building, secrets, logging, error handling, dependency updates, or LLM/agent/RAG code paths.

Test-Driven Development workflow for all languages. Use when implementing new features, fixing bugs, or refactoring code, or when the user says "TDDで". Enforces outside-in order E2E → contract (CDC, when a boundary is crossed) → Unit (RED-GREEN-REFACTOR) with concrete stubs, and a local CI parity sweep (format/lint/type/test) before handoff.

Web research skill that prioritizes official documentation while covering broad literature. Searches, fetches, and synthesizes findings into a structured actionable report. Use when: - 「調べて」「リサーチして」「公式ドキュメント確認して」 - "research X", "look up", "find docs for" - Evaluating libraries, frameworks, or approaches - Investigating errors, migration guides, or breaking changes - Needing up-to-date information beyond training data