अपने एजेंट के लिए सही क्षमता खोजें।
Comprehensive ESLint agent for JavaScript/TypeScript code quality. Use when setting up ESLint, configuring linting rules, analyzing code for issues, fixing violations, or integrating ESLint into development workflows. Triggers on requests involving code quality, linting, static analysis, or ESLint configuration for JavaScript, TypeScript, React, or Node.js projects.
Maintain consistent code formatting, naming conventions, type safety, and automated code quality standards across PHP and TypeScript/JavaScript. Use this skill when writing or editing any PHP files (.php), TypeScript/JavaScript files (.ts, .tsx, .js, .jsx), when implementing type declarations and return types, when running code formatters (Laravel Pint, Ultracite) or linters, when running static analysis tools (Larastan), when naming variables, functions, classes, or files, when applying DRY principles, when removing dead code, or when preparing code for review or commit.
Identifies code smells, applies design patterns, guides migrations, and performs security/performance/accessibility refactoring. Use when improving code quality, modernizing codebases, applying design patterns, migrating to TypeScript, or extracting microservices.
Fixes error handling issues including floating promises, silent catches, and throwing non-Error objects. Use when encountering @typescript-eslint/no-floating-promises, silent catch blocks, or throw statement issues.
Analyzes TypeScript/Node.js projects for code quality, type safety, and technical debt
Run automatically after completing any code changes. Validates TypeScript build, auto-fixes prettier and linting, then manually fixes any remaining issues.
Write clean, consistent code following established naming conventions, formatting rules, and the DRY principle across all files. Use this skill when writing any code in any file, naming variables and functions, structuring code logic, formatting code with consistent indentation, choosing descriptive names that reveal intent, keeping functions small and focused, removing dead code and unused imports, extracting common logic into reusable functions, maintaining consistent code style across the codebase, configuring linters and formatters, or refactoring code for better readability. Apply this skill universally across all coding tasks to ensure code quality, maintainability, and consistency with project standards. This skill should be active for all file types including TypeScript, JavaScript, Python, Ruby, Java, Go, and other programming languages.
Use when writing or reviewing TypeScript code, or when the user mentions TypeScript, strict typing, type errors, or type safety.
Maintain code quality with Ruff for Python and ESLint/TypeScript for frontend. Run linters, fix issues, and ensure consistent formatting. Use when linting code, fixing style issues, or preparing to commit.
Run automatically after completing any code changes. Validates TypeScript build, auto-fixes prettier and linting, then manually fixes any remaining issues.
Generate configuration files for tools like ESLint, Prettier, TypeScript, and Webpack. Use when setting up project tooling or standardizing configurations.
Safely refactor TypeScript code while maintaining type safety and test coverage. Includes verification steps.
Validates type consistency across Rust, TypeScript, PostgreSQL boundaries. Use when reviewing code, debugging type mismatches, or validating API contracts. Triggers on: check consistency, validate types, find mismatches, cross-language.
TypeScript coding standards. Use when: writing or reviewing TypeScript code (*.ts, *.tsx).
Runs frontend quality checks including TypeScript, ESLint, and tests. Use before commits, PRs, or when the user says "check frontend", "run frontend tests", "lint frontend".
Generate Prettier configuration files for consistent code formatting across JavaScript, TypeScript, CSS, and other file types. Triggers on "create prettier config", "generate prettier configuration", "prettier setup", "code formatting config".
Review, analyze, and inspect code for Photo Map MVP project following Spring Boot, Angular 18, and shared project conventions. Check security, performance, naming, testing, and MVP scope compliance. Use when reviewing pull requests, conducting code audits, analyzing code quality, inspecting Java or TypeScript files, or ensuring quality before commits. File types: .java, .ts, .html, .xml, .properties, .css, .scss
Resolve all TypeScript errors using root cause analysis, targeted fixes, and mandatory validation
