اپنے ایجنٹ کے لیے موزوں صلاحیت تلاش کریں۔
Run frontend quality checks including ESLint, Prettier, and TypeScript compilation. Use when ensuring frontend code quality, before committing, running checks, or when user mentions quality, checks, ESLint, Prettier, TypeScript, or npm run checks.
Enforce strict type safety, accessibility standards, and code quality for TypeScript/JavaScript projects using Biome's formatter and linter. Use when writing, reviewing, or fixing TS/JS/TSX/JSX code, checking for a11y issues, linting errors, type safety problems, or when the user mentions code quality, formatting, accessibility, or best practices.
Enforces immutable coding principles, function structure ordering, functional programming patterns, TDD, clean deletion, and YAGNI+SOLID+DRY+KISS principles for this codebase. This skill should be used when writing or reviewing TypeScript/React code in this project, particularly when creating hooks, utility functions, or components. Use this skill to ensure code follows the established patterns for immutability, proper ordering of statements, functional transformations, test-driven development, and simplicity (preferring Occam's Razor/KISS when principles conflict).
Provides comprehensive TypeScript development expertise and coding standards. Ensures type safety through strict type checking, implements clean code patterns, and maintains consistent architectural decisions. Specializes in advanced type system features including generics, conditional types, mapped types, and template literal types. Use when: working with TypeScript files (.ts/.tsx), defining type definitions and interfaces, implementing generic programming patterns, designing type-safe APIs, handling complex type transformations, integrating TypeScript with React/Vue/Angular frameworks, configuring strict mode settings, resolving type errors, or optimizing type performance in large codebases.
Generates LLM-optimized code context with function call graphs, side effect detection, and incremental updates. Processes JavaScript/TypeScript codebases to create compact semantic representations including multi-level summaries, entry point identification, and hash-based change tracking. Provides 74-97% token reduction compared to reading raw source files. Useful for understanding code architecture, debugging complex systems, reviewing pull requests, and onboarding to unfamiliar projects.
Use this agent when you need to review TypeScript code changes with an extremely high quality bar. This agent should be invoked after implementing features, modifying existing code, or creating new TypeScript components. The agent applies Kieran's strict TypeScript conventions and taste preferences to ensure code meets exceptional standards.\n\nExamples:\n- <example>\n Context: The user has just implemented a new React component with hooks.\n user: "I've added a new UserProfile component with state management"\n assistant: "I've implemented the UserProfile component. Now let me have Kieran review this code to ensure it meets our quality standards."\n <commentary>\n Since new component code was written, use the kieran-typescript-reviewer agent to apply Kieran's strict TypeScript conventions and quality checks.\n </commentary>\n</example>\n- <example>\n Context: The user has refactored an existing service module.\n user: "Please refactor the EmailService to handle attachments"\n assistant: "I've refact
Comprehensive code review skill for TypeScript, JavaScript, Python, Swift, Kotlin, Go. Includes automated code analysis, best practice checking, security scanning, and review checklist generation. Use when reviewing pull requests, providing code feedback, identifying issues, or ensuring code quality standards.
コード品質チェック専門スキル。TypeScript/JavaScript ファイルの ESLint、型チェック、コーディング規約を検証する。
Automatically detect and fix TypeScript unused imports/variables errors (TS6133). Use when encountering "declared but its value is never read" errors during tsc, build, or CI checks.
Formatting rules for TypeScript conditional types. Use when writing complex conditional types to ensure debuggable, maintainable formatting with proper alignment.
Audit TypeScript/typed code for type safety issues. Identifies any abuse, missing type guards, and opportunities to make invalid states unrepresentable. Read-only. Triggers: review types, type safety, check types, typescript review.
Automated code quality assistant that formats code, fixes syntax/type errors, detects bugs, and validates fixes across Python, JavaScript, TypeScript, Java, Go, and Rust
Comprehensive code review for Ishkul's React Native/TypeScript frontend and Go backend. Checks for quality, security, performance, and adherence to project conventions. Use after implementing features or during PR review.
Expert knowledge for runtime validation in TypeScript using ArkType, a syntax-first validation library with TypeScript-like definitions, JIT compilation for 10x-100x performance over Zod, native recursion support, morphs for data transformation, and Standard Schema compatibility
Use when writing TypeScript code. Applies TypeScript best practices for type safety, generics, JSDoc patterns, and maintainable typed code.
Perform automated static code analysis on modified files. Triggers automatically after code changes to catch common issues before QA Lead review. Checks for: code complexity, dead code, type errors, import issues, and style violations. Use when: - Code files have been modified - Before committing changes - As pre-check for QA Lead review - User asks "analyze this code" or "check for issues" This skill runs lightweight static analysis tools (pylint, mypy, ruff for Python; eslint, tsc for TypeScript) and reports findings in structured format.
Apply consistent coding style, naming conventions, and code formatting across the NestJS API codebase. Use this skill when writing any TypeScript code in the apps/api/ or packages/shared/ directories, when naming variables, functions, classes, or files, when structuring imports and exports, or when following the project's ESLint and Prettier configurations. This includes enforcing strict TypeScript settings (no any, prefer-nullish-coalescing, prefer-optional-chain), using proper file naming patterns (kebab-case for files, PascalCase for classes), organizing imports alphabetically, and maintaining 120 character line width. Apply when writing any *.ts file, refactoring code, or reviewing code quality.
