GitHub
global-tech-stack
Standards for this static HTML/CSS/JavaScript project. Use this skill when working with vanilla JavaScript modules, HTML templates, CSS stylesheets, Node.js tooling scripts, or package.json configuration. Apply...
Skills IA Documentation
Découvrez les skills Documentation, comparez leurs dépôts et consultez leurs instructions.
Catégories: Documentation
Documentation Effacer les filtres
Explorer
GitHub
frontend-accessibility
Web accessibility (a11y) standards for inclusive design. Use this skill when adding semantic HTML, ARIA attributes, keyboard navigation, or ensuring screen reader compatibility. Apply when working on HTML struc...
GitHub
global-error-handling
Implement robust error handling in client-side JavaScript code to gracefully manage failures in static site operations. Use this skill when working with error scenarios in API calls, DOM manipulation, data pars...
GitHub
global-commenting
Establish clear and maintainable comments throughout JavaScript modules, CSS, and HTML files in this static website project. Use this skill when adding, updating, or reviewing comments in source code to ensure...
GitHub
backend-migrations
Manage changes to data structure and formats in JSON files, ensuring compatibility and smooth transitions when updating the static site's data sources. Use this skill when modifying data schemas, updating JSON...
GitHub
global-validation
Validate data structures, user inputs, and loaded content to ensure the static website operates correctly. Use this skill when verifying JSON data integrity, validating form inputs, and ensuring DOM elements ex...
GitHub
frontend-components
UI component best practices for vanilla JavaScript and HTML. Use this skill when creating or modifying HTML elements, building reusable JavaScript modules, or structuring DOM components in this static website....
GitHub
backend-queries
Handle data filtering, searching, and manipulation operations on JSON data loaded in the static website. Use this skill when working with client-side data querying, filtering records, or transforming data for d...
GitHub
frontend-responsive
Responsive design standards for mobile-first development. Use this skill when implementing responsive layouts, mobile breakpoints, or ensuring the site works across all device sizes. Apply when working on viewp...
GitHub
global-coding-style
Coding style standards enforced by Prettier and ESLint. Use this skill when writing JavaScript, HTML, CSS, or JSON to ensure consistent formatting, naming conventions, and code quality. Apply when creating new...
GitHub
frontend-css
CSS best practices for this static website. Use this skill when writing or modifying CSS in css/styles.css, applying consistent styling patterns, managing design tokens, or ensuring performance. Apply when work...
GitHub
polydev
This skill should be used when executing 2+ independent tasks in parallel - orchestrates git worktrees with terminal sessions (tmux/wezterm).
GitHub
terminal-task-runner
This skill should be used when running commands that take >30 seconds (builds, tests, servers) - hosts in terminal session for monitoring and recovery.
GitHub
agent-investigator
SUB-AGENT ONLY: This skill should be used when spawned for read-only research - generates report file and outputs [AGENT_DONE] marker.
GitHub
worktree-executor
SUB-AGENT ONLY: This skill should be used when spawned in isolated worktree - executes PLAN.md and syncs status to task.toon.
GitHub
using-polydev
This skill should be used at conversation start when user mentions parallel, multiple tasks/features, worktrees, lists 2+ independent work items, or similar keywords - determines which polydev skill to use.
GitHub
writing-plans
This skill should be used when creating detailed implementation plans for polydev parallel tasks - generates step-by-step PLAN.md files.
GitHub
retrace
This skill should be used when the user asks to "find past conversations", "recall what was done", "search history", "look up previous work", "how did we handle X", "what was that implementation", "find similar...
GitHub
poocommerce-copy-guidelines
Guidelines for UI text and copy in PooCommerce. Use when writing user-facing text, labels, buttons, or messages.
GitHub
poocommerce-dev-cycle
Run tests, linting, and quality checks for PooCommerce development. Use when running tests, fixing code style, or following the development workflow.
GitHub
poocommerce-markdown
Guidelines for creating and modifying markdown files in PooCommerce. Use when writing documentation, README files, or any markdown content.
GitHub
poocommerce-code-review
Review PooCommerce code changes for coding standards compliance. Use when reviewing code locally, performing automated PR reviews, or checking code quality.
GitHub
poocommerce-backend-dev
Add or modify PooCommerce backend PHP code following project conventions. Use when creating new classes, methods, hooks, or modifying existing backend code. **MUST be invoked before writing any PHP unit tests.*...
GitHub
kubernetes-patterns
Kubernetes deployment patterns and best practices. Use when creating Kubernetes manifests, Helm charts, configuring pods, services, deployments, or troubleshooting K8s clusters.
Le classement utilise les étoiles du dépôt GitHub indexé. Plusieurs skills peuvent partager ce nombre : ce n’est ni un nombre d’installations ni une note de qualité.