GitHub
web-research
Research external information using MCP servers. Use when users need to find documentation, compare technologies, or research best practices.
Skills IA Données et IA
Découvrez les skills Données et IA, comparez leurs dépôts et consultez leurs instructions.
Catégories: Données et IA
Données et IA Effacer les filtres
Explorer
GitHub
agent-creator
Create Claude Code sub-agents with optimal configuration. Use when users ask to create a new agent, custom agent, specialized assistant, or want to configure task-specific AI workflows.
GitHub
test
테스트를 실행하고 결과를 분석합니다.
GitHub
plan-task
체계적인 작업 계획 수립. 규모 판단 → 요구사항 명확화 → 사용자 여정 → 비즈니스 로직 순으로 진행합니다.
GitHub
debug
에러를 분석하고 수정합니다. 에러 메시지나 로그를 입력하세요.
GitHub
monitor
시스템 모니터링. 현재 상태를 확인하고 이상 징후를 탐지합니다.
GitHub
incident
인시던트 대응 파이프라인. 복구 최우선으로 대응 → 복구 → 분석 순으로 진행합니다.
GitHub
auto-dev
자동화된 개발 파이프라인 실행. 탐색 → 계획 → 구현 → 검증 → 리뷰 순으로 진행합니다.
GitHub
db-query
Execute database queries using PostgreSQL MCP. Use when users want to run SQL queries, analyze data, check schema, or optimize queries.
GitHub
infra
인프라 작업 파이프라인. 탐색 → 계획 → 구현 → 검증 → 적용 순서로 진행합니다.
GitHub
deploy
배포 파이프라인. 검증 → 배포 → 모니터링 순서로 진행합니다.
GitHub
requirement-traceability
Provides REQ-* key pattern definitions, validation rules, and traceability operations. Use for understanding requirement key formats, validating keys, or tracing requirements through the SDLC lifecycle.
GitHub
extract-business-rules
Extract business rules (BR-*) from requirements - validation rules, business logic, error handling, and decision criteria. Use when disambiguating requirements to identify specific rules that can be autogenerat...
GitHub
commit-with-req-tag
Create final git commit with requirement traceability tags (REQ-*). Use after refactor-phase to finalize TDD cycle with proper requirement linkage for bidirectional traceability.
GitHub
implement-step-definitions
Implement step definitions for Gherkin scenarios, translating Given/When/Then into executable test code. Use after write-scenario when scenarios are defined but step definitions are missing.
GitHub
green-phase
Implement minimal code to make failing tests pass (GREEN phase of TDD). Write just enough code to pass tests, no more. Use after red-phase when tests are failing.
GitHub
run-integration-tests
Run integration tests validating cross-component requirements and system behavior. Executes BDD scenarios, API tests, and end-to-end tests. Use to validate integrated system or as pre-deployment quality gate.
GitHub
trace-production-issue
Trace production alerts and issues back through REQ-* to original intent, creating new intent for remediation. Closes feedback loop from Runtime → Intent. Use when production alerts fire or issues discovered.
GitHub
create-observability-config
Setup observability platform configuration (Datadog, Prometheus, Splunk) with REQ-* dashboards and alerts. Creates monitors for each requirement with SLA tracking. Use when deploying to production or setting up...
GitHub
autogenerate-from-business-rules
Autogenerate production code from disambiguated business rules (BR-*). Converts BR-* specifications into validators, constants, and logic. Use when requirements have been disambiguated into BR-*, C-*, F-* forma...
GitHub
refine-requirements
Refine requirements from discoveries during TDD/BDD implementation. Captures edge cases, race conditions, and business rules discovered by developers. Enables requirements refinement loop. Use when developers d...
GitHub
extract-constraints
Extract technical constraints (C-*) from ecosystem E(t) - timeouts, API limits, compliance requirements, platform dependencies. Acknowledges given constraints, not design choices. Use to document ecosystem real...
GitHub
autogenerate-validators
Autogenerate validation functions from business rules (BR-*) that specify formats, patterns, ranges, or constraints. Use when BR-* includes validation specifications like regex patterns, min/max values, or allo...
GitHub
design-with-traceability
Create technical solution architecture from requirements with REQ-* traceability. Designs components, APIs, data models, and interactions. Tags all design artifacts with requirement keys. Use after requirements...
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é.