software-development
Clean code principles - avoid common issues like unnecessary try/catch, unused variables, DRY violations, and layer confusion
Clean code principles - avoid common issues like unnecessary try/catch, unused variables, DRY violations, and layer confusion
Enforce strict TypeScript standards including centralized type definitions in app/types/, arrow functions only, explicit return types, and lang="ts" in all components. Use when reviewing or creating TypeScript code.
バグ、スタイルの問題、ベストプラクティスについてコードの変更をレビューします。プルリクエスト(PR)の確認やコード品質のチェック時に使用してください。
Use when reviewing commit messages for compliance with the seven rules from cbea.ms/git-commit - checks subject line length, imperative mood, line wrapping, and that the message explains what and why
Review workscript node implementations for alignment with NODE_DEVELOPMENT_BLUEPRINT.md and consistency with the new-node skill. Use when reviewing node code, auditing node implementations, checking for compliance with single-edge return pattern, validating ai_hints metadata consistency, or ensuring thorough documentation of state interactions. Triggers on requests like "review this node", "check node compliance", "audit node implementation", or "validate node metadata".
Analyzes writing-ecosystem traces to fix style.yaml, template.yaml, and tools.yaml based on quality issues found in production runs.
Applies Sun Lab C# and Unity coding conventions when writing, reviewing, or refactoring code. Covers .cs files, XML documentation, naming conventions, MQTT patterns, README.md files, git commit messages, and YAML task templates. Use when writing or modifying any .cs, .md, or .yaml files in Sun Lab projects.
Biome linter/formatter setup. Use when configuring Biome as an alternative to ESLint + Prettier.
Use when the user asks for a local CodeRabbit review before creating a pull request. Delegates to the specialized local-coderabbit-reviewer sub-agent to run the scan, analyze results, present a plan for fixes, apply changes, run tests, and commit only if all tests pass.
Enforces consistent design tokens, patterns, and component styles. Use when building new components, reviewing UI consistency, or extracting patterns from existing code.
Apply the Agent OS standard for global coding style.
Core development principles including anti-hallucination, anti-hardcoding, error handling, logging, testing, and security standards. Use during feature design, implementation, and code review to ensure code quality and maintainability. Applies universally to all code regardless of technology or feature.
Set up and run Ruff in Python projects. Use when installing Ruff with uv, configuring ruff.toml, updating AGENTS.md and .gitignore for Ruff, or running Ruff lint/format commands.
Automatically applies when writing Python code to enforce comprehensive type hints. Ensures mypy compatibility, proper generic types, and type safety best practices.
TypeScript coding style and patterns - type safety, error handling, code organization
Run pre-commit hooks (clang-format, clang-tidy) on all files. Use when the user wants to format code, run linters, or prepare code for commit.
Use when creating or editing markdown files to ensure strict compliance with markdownlint rules and professional markdown best practices
代码质量快速检查工具。当用户说"检查代码"、"运行测试"、"质量检查"时自动触发。自动执行 lint、类型检查、覆盖率验证。
Validate plan document structure and frontmatter. Use when checking plans for compliance, ensuring proper formatting, or verifying metadata before commits.
TypeScript coding standards, strict mode practices, and type safety guidelines.