input-validation
Input validation patterns for the .NET 8 WPF widget host app. Use when implementing form validation, data annotations, command can-execute logic, and error display in MVVM ViewModels.
Find the perfect capability for your agent.
Input validation patterns for the .NET 8 WPF widget host app. Use when implementing form validation, data annotations, command can-execute logic, and error display in MVVM ViewModels.
Defines coding standards, test patterns, and language conventions for this project. Use this when writing code, comments, documentation, or git commit messages.
Perform comprehensive C#/.NET code reviews focusing on clean code, security, testing, performance, and documentation
Use this agent when you need a brutally honest Rails code review from the perspective of David Heinemeier Hansson. This agent excels at identifying anti-patterns, JavaScript framework contamination in Rails codebases, and violations of Rails conventions. Perfect for reviewing Rails code, architectural decisions, or implementation plans where you want uncompromising feedback on Rails best practices.\n\n<example>\nContext: The user wants to review a recently implemented Rails feature for adherence to Rails conventions.\nuser: "I just implemented a new user authentication system using JWT tokens and a separate API layer"\nassistant: "I'll use the DHH Rails reviewer agent to evaluate this implementation"\n<commentary>\nSince the user has implemented authentication with patterns that might be influenced by JavaScript frameworks (JWT, separate API layer), the dhh-rails-reviewer agent should analyze this critically.\n</commentary>\n</example>\n\n<example>\nContext: The user is planning a new Rails feature and wants
This skill should be used when reviewing or editing copy to ensure adherence to Every's style guide. It provides a systematic line-by-line review process for grammar, punctuation, mechanics, and style guide compliance.
Use this agent when you need to perform security audits, vulnerability assessments, or security reviews of code. This includes checking for common security vulnerabilities, validating input handling, reviewing authentication/authorization implementations, scanning for hardcoded secrets, and ensuring OWASP compliance. <example>Context: The user wants to ensure their newly implemented API endpoints are secure before deployment.\nuser: "I've just finished implementing the user authentication endpoints. Can you check them for security issues?"\nassistant: "I'll use the security-sentinel agent to perform a comprehensive security review of your authentication endpoints."\n<commentary>Since the user is asking for a security review of authentication code, use the security-sentinel agent to scan for vulnerabilities and ensure secure implementation.</commentary></example> <example>Context: The user is concerned about potential SQL injection vulnerabilities in their database queries.\nuser: "I'm worried about SQL inject
Expert in conducting thorough code reviews for Python projects using GitHub MCP, covering test coverage, security practices, PEP 8 compliance, and code organization. Use when reviewing code or PRs.
pnpm+turbo 모노레포에서 Node 버전(.nvmrc)과 터보 task 의존성을 고려해 lint/typecheck/build를 안전하게 실행하고, 실패 시 패키지 단위로 범위를 좁혀 원인을 찾습니다.
hometeプロジェクト用のiOS Swiftコードレビュースキル。SwiftLintを実行し、警告・エラーを報告し、git diffで変更されたSwiftファイルをレビューする。/code-reviewコマンドでユーザーがコードレビューを要求した時、または機能実装、リファクタリング、バグ修正、テスト更新後に使用。DIパターン準拠、Swift 6並行性、過度なエンジニアリングの回避、テストコードの品質に焦点を当てる。
Use this agent when you need a final review pass to ensure code changes are as simple and minimal as possible. This agent should be invoked after implementation is complete but before finalizing changes, to identify opportunities for simplification, remove unnecessary complexity, and ensure adherence to YAGNI principles. Examples: <example>Context: The user has just implemented a new feature and wants to ensure it's as simple as possible. user: "I've finished implementing the user authentication system" assistant: "Great! Let me review the implementation for simplicity and minimalism using the code-simplicity-reviewer agent" <commentary>Since implementation is complete, use the code-simplicity-reviewer agent to identify simplification opportunities.</commentary></example> <example>Context: The user has written complex business logic and wants to simplify it. user: "I think this order processing logic might be overly complex" assistant: "I'll use the code-simplicity-reviewer agent to analyze the complexity and
Use this agent when reviewing code to ensure features are agent-native - that any action a user can take, an agent can also take, and anything a user can see, an agent can see. This enforces the principle that agents should have parity with users in capability and context. <example>Context: The user added a new feature to their application.\nuser: "I just implemented a new email filtering feature"\nassistant: "I'll use the agent-native-reviewer to verify this feature is accessible to agents"\n<commentary>New features need agent-native review to ensure agents can also filter emails, not just humans through UI.</commentary></example><example>Context: The user created a new UI workflow.\nuser: "I added a multi-step wizard for creating reports"\nassistant: "Let me check if this workflow is agent-native using the agent-native-reviewer"\n<commentary>UI workflows often miss agent accessibility - the reviewer checks for API/tool equivalents.</commentary></example>
Runs configured type checkers (pyrefly, mypy) on files after editing. MUST USE when validating Python type safety (Internal-only passive hook).
Go code standards enforcing idiomatic patterns, safety, and maintainability. Use when writing, generating, or reviewing Go code.
Configures modern TypeScript (4.9+ through 5.x) for maximum type safety with sustainable compile times. Use when designing type-safe configs/maps/APIs, enforcing strictness flags, improving TS build performance (incremental, project references), or setting up separate TS/ESLint configs for tests.
自分の PR に付いたレビューコメントを確認し、修正対応を実行する(PR作成者向け)。「レビュー対応」「レビューコメント確認」「指摘を修正」「PRコメント確認」などで起動。
Search ACE playbook before implementing, building, fixing, debugging, or refactoring code. Capture patterns after completing substantial coding work.
Biome/Ultracite 린트 경고(예: useSortedClasses)와 포맷 문제를 의미 변경 없이(safe fix) 해결하고, 패키지 단위로 빠르게 재검증합니다.
掃描程式碼和配置檔中的敏感資料洩漏,包括 API Keys、密碼、Token 等
Implement authentication and authorization with Better Auth - a framework-agnostic TypeScript authentication framework. Features include email/password authentication with verification, OAuth providers (Google, GitHub, Discord, etc.), two-factor authentication (TOTP, SMS), passkeys/WebAuthn support, session management, role-based access control (RBAC), rate limiting, and database adapters. Use when adding authentication to applications, implementing OAuth flows, setting up 2FA/MFA, managing user sessions, configuring authorization rules, or building secure authentication systems for web applications.