Loading...
Loading...
Found 154 Skills
Use when writing type annotations on variables. Use when TypeScript can infer the type. Use when code feels cluttered with types.
Verify and enforce coding standards, AI guidelines, and workspace compliance across repositories. Use for standards propagation, compliance verification, and enforcing development best practices.
Use before committing code - validates Drupal coding standards, SOLID/DRY principles, security practices, and CSS standards
When dealing with python code, these guidelines must always be followed.
Use when writing, reviewing, or refactoring WordPress PHP code. Covers WordPress Coding Standards (WPCS), naming conventions, Yoda conditions, $wpdb usage, escaping with esc_html/esc_attr/esc_url, wp_kses, hooks (add_action, add_filter, apply_filters, do_action), i18n functions (__(), _e(), _x, _n), wp_enqueue_script, wp_enqueue_style, formatting rules, deprecated function replacements, and WordPress API best practices. For security see wp-security; for performance see wp-performance; for blocks see wp-blocks.
Read the backend development guidelines before starting your development task.
Load project context from .claude/ directory at the start of every task. This ensures Gemini CLI has the same coding rules, design decisions, and library constraints as Claude Code.
Generate pure mapper functions for transformations between layers, HTTP DTOs to use case inputs dtos, use case to response dto, etc.
Personal PHP conventions enforced when creating, modifying, or planning code that will touch PHP files. Covers strict types, function imports, testing philosophy, class design, observability, and planning practices. Activate whenever working on PHP code.
Creates project constitution files (CLAUDE.md/AGENTS.md) that serve as always-loaded context for coding agents. Use when setting up a new project for spec-driven development, configuring agent instructions, writing CLAUDE.md or AGENTS.md, or establishing project-wide coding standards and constraints.