Browse reusable Agent Skills, each with a clear purpose and practical guidance.
Apply findings by making the suggested code changes. Applies accepted verdicts, escalates ambiguous findings to the user, and offers to note genuine improvements for later. Use when the user asks to "apply findings", "apply fixes", "apply suggestions", "apply accepted findings", "fix the findings", or "apply the review results".
Fundamental software principles - SOLID, DRY, Occam's Razor, Miller's Law, YAGNI, Readable Code. Triggers: 原則, シンプル, 複雑, アーキテクチャ, リファクタリング, 保守性, コード品質, design pattern, best practice, clean code
Framework-agnostic frontend component design patterns.
Configures background job scheduling and task execution with APScheduler 3.x in FastAPI. Use when: adding new background jobs, modifying job intervals, implementing job state persistence, handling job events, or debugging scheduler issues.
プロジェクトで使用しているアーキテクチャの実装ベストプラクティスを調査し、 docs/best-practices.md にドキュメント化する。技術スタックを自動検出し、 スタック別のベストプラクティス（コード例・アンチパターン）を出力する。 「ベストプラクティスをまとめて」「実装パターンを調べて」「コーディングガイドを作成」 「アーキテクチャの使い方を整理」などの依頼時に発火。
Create and validate solution design documents (SDD). Use when designing architecture, defining interfaces, documenting technical decisions, analyzing system components, or working on solution-design.md files in docs/specs/. Includes validation checklist, consistency verification, and overlap detection.
Use this skill when exploring codebase architecture or planning new features requiring models/enums. AUTO-ACTIVATE when user mentions (FR/EN): - modèle, model, models, enum, enums, schema, Prisma schema - architecture, domain, domaine, existe, exists, available, disponible - créer, create, ajouter, add, nouveau, new, nouvelle feature - quel modèle, what model, which model,quel enum - 121 modèles, 87 enums, Planning, Leave, Business Rules This skill provides INSTANT lookup (500 tokens vs 15k for full ERD) for 121 models and 87 enums.
Single deployable with enforced module boundaries for team autonomy without distributed complexity. Triggers: modular monolith, module boundaries, single deployment, team autonomy Use when: teams need autonomy without distributed overhead DO NOT use when: already using microservices or system is small.
Design coarse-grained service architecture for deployment independence without microservices complexity and overhead.