স্কিল খুঁজুন
আপনার এজেন্টের জন্য উপযুক্ত সক্ষমতা খুঁজে নিন।
zero-warnings-enforcer
Applique la philosophie "Broken Window" avec zéro tolérance pour les warnings/errors ESLint et TypeScript. JAMAIS désactiver les règles, TOUJOURS corriger la cause racine. À utiliser lors de la correction d'erreurs, warnings, ou quand l'utilisateur mentionne "eslint", "typescript error", "warning", "linting", "quality", "broken window", "@ts-ignore", "eslint-disable".
python-style
Enforce consistent Python typing (type hints + return types), concise Google-style docstrings, PEP 8/Black formatting, and unit tests when creating or editing Python code. Use when working on .py files, Python APIs, refactors, or bug fixes where maintainability and correctness matter.
pm-validator
Validate outputs against requirements with quality scoring
code-formatter
Auto-format code with Prettier and ESLint, fix linting errors, and enforce code style standards. Use when user says "format code", "fix linting", "prettier", "eslint", or when code needs style fixes.
check-envs
Check and validate all required environment variables in .env file. Use when verifying environment setup or troubleshooting configuration issues.
code-cleanup
Detect and clean redundant code in Python and TypeScript projects. Finds unused imports, dead functions, stale comments, debug statements, and unused dependencies. Use when asked to "clean code", "find dead code", "remove unused imports", "check redundant code", or "清理代码".
typescript-strict-config
Strict TypeScript configuration with all safety flags enabled. Use when initializing TypeScript projects or enforcing type safety.
sdlc-review
Use when reviewing code, verifying implementations, checking security, validating acceptance criteria, or conducting code reviews for a completed implementation.
code-smell-detector
Detects code smells, anti-patterns, and common bugs with quantified thresholds and severity scoring. Use when reviewing code quality, finding maintainability issues, detecting SOLID violations, or identifying technical debt.
validate-protection
Validate protection enforcement via pre-commit hooks. Use when building or testing code protection system (PROTECT-002).
ringlinting-codebase
Parallel lint fixing pattern - runs lint checks, groups issues into independent streams, and dispatches AI agents to fix all issues until the codebase is clean.
modern-ui-quality-gate
Enforces modern, minimal, professional UI standards and rejects outdated or visually noisy web design patterns.
google-shell-style
Use when the user asks to "refactor shell script", "fix bash style", "apply Google style guide to shell", "review shell script style", "format bash script", or when writing, reviewing, or refactoring shell/bash scripts. Provides Google Shell Style Guide rules for formatting, quoting, naming, control flow, and common anti-patterns.
lint-kb
Validate and enforce KB documentation formats, completeness, and integrity. Checks recent docs (uncommitted or last N commits) against KB standards. CHECKS PERFORMED: 1. FORMAT - Documents follow required templates (headers, sections) 2. COMPLETENESS - Tickets/issues have all required files (1-5) 3. INTEGRITY - All tickets in index.md, phases in roadmap.md 4. PATTERNS - Have Status: open|resolved 5. NAMING - Files follow conventions (verb-noun, feat-, comp-, etc.) Use when: - Before committing KB docs - After creating tickets/issues - Periodic maintenance - User says "lint kb", "check docs", "validate kb"
code-hygiene
Apply code hygiene standards for clean, maintainable code. Use when writing, refactoring, or reviewing code.
code-conventions
코드 컨벤션, 코딩 스타일, 코드 스타일, 네이밍, 컨벤션 - Always apply when writing code. Code style, naming rules, function/file size limits for TypeScript, Python, and Java.
