Loading...
Loading...
Found 1,062 Skills
Skill for creating custom lint rules by leveraging the existing linter ecosystems of various programming languages. This is a linter designed for AI Agents rather than humans, and its error messages function as correction instruction prompts for AI. Create custom rules in the `lints/` directory using standard methods for each language, including Rust (dylint), TypeScript/JavaScript (ESLint), Python (pylint), Go (golangci-lint), etc. Use this skill in the following scenarios: (1) When you want AI to enforce project-specific coding rules; (2) When you want to create lint rules that output AI-readable correction instructions when violations occur; (3) When you want to enforce naming conventions, structural patterns, and consistency rules through AI-driven linting. Triggers: "Create a linter rule", "Add a lint rule", "Enforce this pattern", "AI linter", "Custom lint", "Code rules", "Naming rules", "Structural rules", "create a linter rule", "add a lint rule", "enforce this pattern", "AI linter".
Modernize JavaScript/TypeScript toolchain to high-performance native alternatives. Use when upgrading build tools, linters, or compilers.
Build TypeScript clients for SpacetimeDB. Use when connecting to SpacetimeDB from web apps, Node.js, Deno, Bun, or other JavaScript runtimes.
OpenFGA authorization modeling best practices and guidelines. This skill should be used when authoring, reviewing, or refactoring OpenFGA authorization models. Triggers on tasks involving OpenFGA models, relationship definitions, permission structures, .fga files, .fga.yaml test files, or OpenFGA SDK usage in JavaScript, TypeScript, Go, Python, Java, or .NET.
Use when hotwire (Turbo and Stimulus) for building modern reactive Rails applications without complex JavaScript frameworks.
Tests web applications for Cross-Site Scripting (XSS) vulnerabilities by injecting JavaScript payloads into reflected, stored, and DOM-based contexts to demonstrate client-side code execution, session hijacking, and user impersonation. The tester identifies all injection points and output contexts, crafts context-appropriate payloads, and bypasses sanitization and CSP protections. Activates for requests involving XSS testing, cross-site scripting assessment, client-side injection testing, or JavaScript injection vulnerability testing.
Perform static analysis of malicious PDF documents using peepdf, pdfid, and pdf-parser to extract embedded JavaScript, shellcode, and suspicious objects.
This skill should be used when the user asks to "set up ESLint", "configure ESLint rules", "fix ESLint errors", "migrate to flat config", or needs guidance on JavaScript/TypeScript linting best practices.
Senior frontend engineering expertise for building high-quality web interfaces. Use this skill when writing, reviewing, or optimizing frontend code - HTML, CSS, JavaScript, TypeScript, components, layouts, forms, or interactive UI. Triggers on web performance optimization (Core Web Vitals, bundle size, lazy loading), accessibility audits (WCAG, ARIA, keyboard navigation, screen readers), code quality reviews, component architecture decisions, testing strategy, and modern CSS patterns. Covers the full frontend spectrum from semantic markup to production performance.
Restore session state from handoff artifacts and route to the next action. Priority cascade: HANDOFF.json (highest) > .continue-here.md > incomplete task_plan.md > git log. Presents a status dashboard, then executes the next action. Use for "resume", "continue", "pick up where I left off", "what was I doing", "continue work". Do NOT use for starting new tasks (use /do), reviewing past sessions (use /retro), or reading task plans (read task_plan.md directly).
Validate a published or draft-preview WordPress post in a real browser using Playwright. Checks rendered title, heading structure, image loading, OG/meta tags, JavaScript errors, and responsive layout at mobile/tablet/desktop breakpoints. When Chrome DevTools MCP is available, can use it for live browser inspection as an alternative to Playwright. Use for "validate wordpress post", "check live post", "verify published post", "wordpress post looks right", "check og tags", or "responsive check wordpress". Do NOT use for source markdown validation (use pre-publish-checker), SEO keyword analysis (use seo-optimizer), or uploading content (use wordpress-uploader).
Run Python (ruff) and JavaScript (Biome) linting, formatting, and code quality checks with auto-fix support. Use when code needs linting, formatting, or style checking before commits. Use for "lint", "format", "ruff", "biome", "code style", or "check quality". Do NOT use for comprehensive code review (use systematic-code-review).