GitHub
executing-plans
Use when implementing a multi-step plan. Execute systematically with verification checkpoints to catch errors early.
Skills IA Bases de données
Découvrez les skills Bases de données, comparez leurs dépôts et consultez leurs instructions.
Catégories: Bases de données
Bases de données Effacer les filtres
Explorer
GitHub
finishing-a-development-branch
Use when ready to merge feature branch. Complete checklist before creating PR/MR. Ensures professional quality and prevents embarrassing mistakes.
GitHub
writing-plans
Use after brainstorming, before implementation. Breaks work into discrete, actionable tasks with clear verification points.
GitHub
pre-commit-hooks
MANDATORY setup for all projects. Automated code quality enforcement before commits. Prevents bad code from entering repository.
GitHub
playwright-frontend-testing
Use when testing frontend applications. AI-assisted browser testing with Playwright MCP. Fast, deterministic, no vision models needed.
GitHub
cloud-monitoring
Cloud monitoring with Prometheus, Grafana, and cloud-native tools. Use when setting up metrics, alerts, dashboards, or troubleshooting performance issues.
GitHub
writing-skills
Use when creating reusable process documentation. Apply TDD: baseline without skill → document failures → write skill → test → iterate. Four types: Discipline, Technique, Pattern, Reference. Iron Law: No skill...
GitHub
git-platform-cli
MANDATORY: Use gh (GitHub) or glab (GitLab) CLI for ALL issue/task management. Unified workflow across platforms.
GitHub
brainstorming
Use when starting new features, major changes, or unclear requirements. Establishes shared understanding before implementation.
GitHub
testing-anti-patterns
Use to avoid critical testing mistakes. Five Iron Laws: Never test mock behavior, Never add test-only methods, Never mock without understanding, Always integration test, Always test error paths.
GitHub
kubernetes-orchestration
Kubernetes container orchestration. Use when deploying to Kubernetes, writing manifests, configuring Helm charts, or troubleshooting cluster issues.
GitHub
persistent-memory
Use when working on long-running projects or needing context across sessions. Covers memory architecture, privacy controls, efficient retrieval, and integration with claude-mem plugin. Apply when building featu...
GitHub
using-skills
Check for relevant skills before starting any task
GitHub
brand-guidelines
Establish or analyze brand identity guidelines. Creates comprehensive brand documentation that frontend-design, testing, and other skills automatically reference for consistent execution.
GitHub
git-workflow
Use when making commits, creating branches, or managing Git operations. Ensures consistent Git practices and proper commit messages.
GitHub
test-driven-development
Use when adding features or fixing bugs. Follow RED/GREEN/REFACTOR cycle. Write failing test first, implement minimal code to pass, then refactor.
GitHub
code-review
Self-review before declaring work complete
GitHub
browser-automation-debugging
Use when debugging web applications or automating browser tasks. Leverage Chrome DevTools MCP for inspection, performance analysis, and automated testing.
GitHub
terraform-iac
Infrastructure as Code with Terraform. Use when provisioning cloud resources, managing state, creating modules, or reviewing Terraform configurations.
GitHub
frontend-design
Create distinctive, production-grade frontend interfaces with high design quality. Use when building web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.
GitHub
alibaba-cloud-architecture
Alibaba Cloud architecture patterns and best practices. Use when designing, deploying, or reviewing infrastructure on Alibaba Cloud including ECS, ACK, Function Compute, and OSS.
GitHub
remote-code-agents
Delegate tasks to remote Claude Code agent containers for parallel execution, long-running analysis, or resource-intensive operations.
GitHub
branch-discipline
Enforce one branch per issue, small focused commits, and clean git history. Use with /branch command.
GitHub
root-cause-tracing
Use when symptoms don't reveal the cause. Trace backward through call chains to find where problems originate. Follow: Observe symptom → Find immediate cause → Identify caller → Keep tracing → Locate trigger.
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é.