GitHub
frappe-api
Frappe Python and JavaScript API reference including document operations, database queries, utilities, and REST API patterns. Use when working with frappe.get_doc, frappe.db, frappe.call, or any Frappe API meth...
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
server-scripts
Frappe server-side Python patterns for controllers, document events, whitelisted APIs, background jobs, and database operations. Use when writing controller logic, creating APIs, handling document events, or pr...
GitHub
clean-commits
Use when committing code - ensures atomic, descriptive commits that leave the codebase in a merge-ready state at every point
GitHub
timescaledb
MANDATORY when working with time-series data, hypertables, continuous aggregates, or compression - enforces TimescaleDB 2.24.0 best practices including lightning-fast recompression, UUIDv7 continuous aggregates...
GitHub
acceptance-criteria-verification
Use after implementing features - verifies each acceptance criterion with structured testing and posts verification reports to the GitHub issue
GitHub
documentation-audit
Use when documentation drift is detected. Comprehensively audits codebase and creates/updates Swagger, features docs, and general documentation to achieve full sync.
GitHub
silent-failure-hunter
Use when asked to detect silent failures/weak error handling or explicitly asked to run the silent-failure-hunter subagent.
GitHub
issue-driven-development
Use for any development work - the master 13-step coding process that orchestrates all other skills, ensuring GitHub issue tracking, proper branching, TDD, code review, and CI verification
GitHub
sentry-setup-tracing
Setup Sentry Tracing (Performance Monitoring) in any project. Use this when asked to add performance monitoring, enable tracing, track transactions/spans, or instrument application performance. Supports JavaScr...
GitHub
tdd-full-coverage
Use when implementing features or fixes - test-driven development with RED-GREEN-REFACTOR cycle and full code coverage requirement
GitHub
feedback-triage
Use when receiving UAT feedback, bug reports, user testing results, stakeholder feedback, QA findings, or any batch of issues to investigate. Investigates each item BEFORE creating issues, classifies by type an...
GitHub
initiative-architecture
Use for MASSIVE work requests requiring multi-epic planning. Creates research spikes, documents all unknowns and decisions, builds resumable architecture documents, and structures work into epics and milestones...
GitHub
postgres-rls
MANDATORY when touching auth tables, tenant isolation, RLS policies, or multi-tenant database code - enforces Row Level Security best practices and catches common bypass vulnerabilities
GitHub
sentry-setup-ai-monitoring
Setup Sentry AI Agent Monitoring in any project. Use this when asked to add AI monitoring, track LLM calls, monitor AI agents, or instrument OpenAI/Anthropic/Vercel AI/LangChain/Google GenAI. Automatically dete...
GitHub
autonomous-orchestration
Use when user requests autonomous operation across multiple issues. Orchestrates parallel workers, monitors progress, handles SLEEP/WAKE cycles, and works until scope is complete without user intervention.
GitHub
skill-development
Use when the user wants to create or refine Codex skills, improve skill descriptions, organize skill resources, or follow Codex skill best practices.
GitHub
conflict-resolution
Use when encountering merge conflicts - handle conflicts cleanly, verify resolution, and maintain code integrity
GitHub
inclusive-language
Use when writing code, documentation, or comments - always use accessible and respectful terminology
GitHub
strict-typing
Use when writing code in typed languages - enforces full typing with no any/unknown/untyped escapes, even if it requires extra time
GitHub
worker-handover
Defines context handover format when workers hit turn limit. Posts structured handover to GitHub issue comments enabling replacement workers to continue seamlessly.
GitHub
project-board-enforcement
MANDATORY for all work - the project board is THE source of truth. This skill provides verification functions and gates that other skills MUST call. No work proceeds without project board compliance.
GitHub
issue-prerequisite
Use before starting ANY work - hard gate ensuring a GitHub issue exists, creating one if needed through user questioning
GitHub
verification-before-merge
Use before merging PR - final gate ensuring all tests pass, review complete, CI green, and acceptance criteria verified
GitHub
inline-documentation
Use when writing code - ensure complete JSDoc, docstrings, and inline comments assuming documentation will be generated from code
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é.