GitHub
playwright-debugging
Use when Playwright scripts fail, tests are flaky, selectors stop working, or timeouts occur - provides systematic debugging approach for browser automation issues
☆ 89Voir le skill
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
testing-skills-with-subagents
Use when creating or editing skills, before deployment, to verify they work under pressure and resist rationalization - applies RED-GREEN-REFACTOR cycle to process documentation by running baseline without skil...
☆ 89Voir le skill
GitHub
writing-good-tests
Use when writing or reviewing tests - covers test philosophy, condition-based waiting, mocking strategy, and test isolation
☆ 89Voir le skill
GitHub
howto-code-in-typescript
Use when writing TypeScript code, reviewing TS implementations, or making decisions about type declarations, function styles, or naming conventions - comprehensive house style covering type vs interface rules,...
☆ 89Voir le skill
GitHub
playwright-patterns
Use when writing Playwright automation code, building web scrapers, or creating E2E tests - provides best practices for selector strategies, waiting patterns, and robust automation that minimizes flakiness
☆ 89Voir le skill
GitHub
investigating-a-codebase
Use when planning or designing features and need to understand current codebase state, find existing patterns, or verify assumptions about what exists; when design makes assumptions about file locations, struct...
☆ 89Voir le skill
GitHub
property-based-testing
Use when writing tests for serialization, validation, normalization, or pure functions - provides property catalog, pattern detection, and library reference for property-based testing
☆ 89Voir le skill
GitHub
defense-in-depth
Use when invalid data causes failures deep in execution - validates at every layer data passes through to make bugs structurally impossible rather than temporarily fixed
☆ 89Voir le skill
GitHub
using-git-worktrees
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification
☆ 89Voir le skill
GitHub
using-generic-agents
Use to decide what kind of generic agent you should use
☆ 89Voir le skill
GitHub
starting-an-implementation-plan
Use when beginning implementation from a design plan - orchestrates branch creation, detailed planning, and hands off to execution with all necessary context
☆ 89Voir le skill
GitHub
requesting-code-review
Use when completing tasks, implementing major features, or before merging to verify work meets requirements - dispatches code-reviewer subagent, handles retries and timeouts, manages review-fix loop until zero...
☆ 89Voir le skill
GitHub
researching-on-the-internet
Use when planning features and need current API docs, library patterns, or external knowledge; when testing hypotheses about technology choices or claims; when verifying assumptions before design decisions - ga...
☆ 89Voir le skill
GitHub
asking-clarifying-questions
Use after initial design context is gathered, before brainstorming - resolves contradictions in requirements, disambiguates terminology, clarifies scope boundaries, and verifies assumptions to prevent building...
☆ 89Voir le skill
GitHub
brainstorming
Use when creating or developing anything, before writing code or implementation plans - refines rough ideas into fully-formed designs through structured Socratic questioning, alternative exploration, and increm...
☆ 89Voir le skill
GitHub
executing-an-implementation-plan
Use when executing implementation plans with independent tasks in the current session - dispatches fresh subagent for each task, reviews once per phase, loads phases just-in-time to minimize context usage
☆ 89Voir le skill
GitHub
writing-implementation-plans
Use when design is complete and you need detailed implementation tasks for engineers with zero codebase context - creates comprehensive implementation plans with exact file paths, complete code examples, and ve...
☆ 89Voir le skill
GitHub
creating-an-agent
Use when creating specialized subagents for Claude Code plugins or the Task tool - covers description writing for auto-delegation, tool selection, prompt structure, and testing agents
☆ 89Voir le skill
GitHub
starting-a-design-plan
Use when beginning any design process - orchestrates gathering context, clarifying requirements, brainstorming solutions, and documenting validated designs to create implementation-ready design documents
☆ 89Voir le skill
GitHub
writing-claude-md-files
Use when creating or updating CLAUDE.md files for projects or subdirectories - covers top-level vs domain-level organization, capturing architectural intent and contracts, and mandatory freshness dates
☆ 89Voir le skill
GitHub
programming-in-react
Use when writing or modifying React components, planning React features, or working with .jsx/.tsx files - provides modern React patterns with TypeScript, hooks usage, component composition, and common pitfalls...
☆ 89Voir le skill
GitHub
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes - four-phase framework (root cause investigation, pattern analysis, hypothesis testing, implementation) that ensures u...
☆ 89Voir le skill
GitHub
writing-for-a-technical-audience
Use when writing documentation, guides, API references, or technical content for developers - enforces clarity, conciseness, and authenticity while avoiding AI writing patterns that signal inauthenticity
☆ 89Voir le skill
GitHub
writing-claude-directives
Use when writing instructions that guide Claude behavior - skills, CLAUDE.md files, agent prompts, system prompts. Covers token efficiency, compliance techniques, and discovery optimization.
☆ 89Voir le skill
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é.