Найдите подходящую возможность для вашего агента.
Guide users through structured co-authoring, improvement, and QA of documentation. Use when users want to write or improve docs such as proposals, technical specs, decision docs, READMEs, guides, API docs, or runbooks; or when they ask for doc review, doc QA, checklists, or templates to make documentation clearer, skimmable, and correct for readers.
Best-practice workflow and guardrails for Python backend work (APIs/services, data access, background jobs, CLIs). Use when Codex is writing or refactoring Python application code, setting up Python tooling, improving performance, adding tests, or making packaging/lint/type-check decisions (uv, Ruff, mypy, pytest), including data tooling choices (prefer polars) and secure config patterns (.env).
Fix Zod schema import issues during Flow to Output SDK migration. Use when seeing "incompatible schema" errors, type errors at step boundaries, or when migrating files that import from 'zod' directly.
Next.js content model with visual editing for Netlify.
Analyze and implement purposeful UI animations for Svelte/SvelteKit + Tailwind projects. Specialized in Svelte transitions, actions, and animation patterns. Use when user asks to add animations, enhance UI motion, animate pages/components, or improve visual feedback. Triggers on "add animations", "animate UI", "motion design", "hover effects", "scroll animations", "page transitions", "micro-interactions".
Creates and manages developer-focused presentations using Slidev, a markdown-based presentation framework. Helps with creating slides, adding code examples, diagrams, animations, and exporting to various formats (PDF, PPTX, PNG). Ideal for technical talks, code demos, and developer documentation presentations.
Automatically check code against PHPCS, ESLint, WordPress Coding Standards, or Drupal Coding Standards when user asks about code style, standards compliance, or best practices. Invoke when user mentions "coding standards", "code style", "linting", "PHPCS", "ESLint", or asks if code follows conventions.
Reusable Tailwind CSS component patterns for consistent UI. Use when creating buttons, cards, forms, tables, modals, navigation, or any UI components with Tailwind CSS.
Builds development projects for production deployment. Analyzes tech stack, proposes build targets (Docker, K8s, serverless, static, etc.), gathers infrastructure requirements, and generates build artifacts. Use when ready to containerize or deploy a project.
Consult official docs via Context7/web search tool before implementing changes, and apply the repo's spec-generation workflow when asked to create plans/specs. Use for new dependencies, SDK/API wiring, or when producing feature docs.
Laravel 10+ development with Eloquent ORM, queues, API resources, and enterprise patterns. WHEN: Building Laravel applications, using Eloquent models/relationships, implementing queues/jobs, creating API resources, Laravel Sanctum/Passport auth, Livewire/Inertia. WHEN NOT: Symfony applications (use php-symfony-* skills), plain PHP without Laravel, frontend-only development.
Manage Obsidian knowledge base - capture ideas, YouTube videos, articles, repositories, create study guides, publish to GitHub Pages, and share notes via URL (no server storage). Use smart AI tagging for automatic organization.
Comprehensive Odoo coding guidelines covering module structure, XML files, Python, JavaScript, and CSS/SCSS conventions for developing Odoo applications. Use when working on Odoo module development, following Odoo coding standards, or maintaining Odoo codebases.
This skill provides guidance for initializing and structuring Next.js projects with modern best practices. It covers project setup, component organization, API integration, and development patterns following the specified architecture.
Tailwind CSS utility-first CSS framework. Use for responsive design, dark mode, utility classes, and component styling.
Create new project templates or customize existing ones with CI/CD, tooling, and AI integration. USE THIS SKILL when user says "create template", "new template for", "customize template", "add template", or wants to build a new language/framework template.
Document user-facing features in a codebase. Use when asked to document features, explain what software does, or generate feature docs. Identifies features (not technical layers), then produces numbered markdown files per feature. Works with any language.
