Use when asking about Rust code style or best practices. Keywords: naming, formatting, comment, clippy, rustfmt, lint, code style, best practice, P.NAM, G.FMT, code review, naming convention,...
Write Markdown files that comply with the project's markdownlint rules and editorconfig settings. This skill should be used when creating or editing Markdown files (.md) to ensure they pass...
This skill should be used when the user asks to "run phpstan", "fix phpstan errors", "phpstan check", "lint php", "check types", or wants to run PHPStan analysis and fix errors for the current...
Run shellcheck on shell scripts after editing scripts or when debugging shell errors. Use for linting scripts in a repo (especially scripts/), catching issues like set -u with unset vars, bad...
Python language expertise for writing idiomatic, production-quality Python code. Covers web frameworks (FastAPI, Django, Flask), data processing (pandas, numpy, dask), ML patterns (sklearn,...
A sample skill demonstrating the AI Linter validation
Anthony Fu's {Opinionated} preferences and best practices for web development
Automated code formatting, Prettier/ESLint integration and code style consistency guide.
Otomatik kod formatlama, Prettier/ESLint entegrasyonu ve kod stil tutarlılığı rehberi.
Orchestrates complete project initialization by coordinating agent-folder-init, linter-formatter-init, husky-test-coverage, and other setup skills. Use this skill when starting a new project that...
Strict test-driven development state machine with red-green-refactor cycles. Enforces test-first development, meaningful failures, minimum implementations, and full verification. Activates when...
Core development standards, patterns, and best practices for React and React Native projects. Use this when users need guidance on code quality (Biome, TypeScript), testing (Jest), project...
|
Validate TypeScript/JavaScript code quality with ESLint, Prettier, type
Automated quality gates for development lifecycle. Pre-commit checks, pre-merge validation, release readiness verification, and post-release documentation.
Use when starting any Deno project, choosing packages, configuring deno.json, or running CLI commands. Provides foundational knowledge for building modern Deno applications.
Proactively analyzes the codebase and generates specialized subagents and skills to standardize agentic workflows.
TDD実装ワークフロー for Next.js projects. Use when "実装して", "機能追加", "コンポーネント作成", "ページ作成", "機能を作って", implementing features, creating components, or building pages.
Comprehensive code review workflow with specialized roles. Use when "レビューして", "review", "セキュリティチェック", "security audit", "テストレビュー", "test quality", "Next.js review", or when checking code quality,...
>