AGENT SKILLS · ÉQUIPEMENT DE MISSION
Des Agent Skills utiles classés selon leur usage réel
Comparez les Skills vérifiés par fonction, contenu, installations et fiabilité de la source avant de les ajouter.
- PÉRIMÈTRE
- VÉRIFIÉ
- Skills
- 22 440
- dépôts
- 3446
- dernière synchronisation
- 28 oct. 2026
factorialcofcode-forms
Embed a Factorial Code process's input-parameter form on a webpage — embed methods, version pinning to the stable alias, what a public form means for the process behind it, driving behavior from the process return value, styling and themes, multi-step flows, and file uploads. Use when embedding, configuring, styling, or wiring up a Factorial Code (fcode) form.
- Installations / 1h
- 1
- GitHub Stars
- 1
- Mis à jour
- 20 oct.
factorialcofcode-i18n
Workspace locales and translations for Factorial Code — i18n/ .yaml files, the fcode.i18n helper in code and in form schemas, execution-locale selection, per-call locale overrides, primary-locale fallback, locale versioning, and the i18n: CLI commands. Use when adding a locale, internationalizing process code or form text, rendering several languages in one execution, or testing and syncing translations.
- Installations / 1h
- 1
- GitHub Stars
- 1
- Mis à jour
- 20 oct.
factorialcofcode-json-schema
Author Factorial Code process input-parameter schemas (parametersSchema.json) — every supported input type and validation option, with a complete annotated sample. Use when creating or editing a parametersSchema.json, or defining a Factorial Code (fcode) process's input parameters or form fields.
- Installations / 1h
- 1
- GitHub Stars
- 1
- Mis à jour
- 20 oct.
factorialcofcode-python
Write Python 3.13 for Factorial Code processes and modules — the main() entry point, fcode.context.parameters, fcode.importmodule(), datastore/storage/env helpers, PEP 8 / snakecase, auto-installed dependencies, and return-value formats. Use when creating or editing .py process or module code for Factorial Code (fcode).
- Installations / 1h
- 1
- GitHub Stars
- 1
- Mis à jour
- 20 oct.
factorialcofcode-release
Promote a Factorial Code app's code from its dev workspace to its prod workspace — fcode clone the dev- workspace, remote:add the prod- workspace, pull prod's current metadata, then add and push. Use when releasing, promoting, or deploying a Factorial Code (fcode) app's dev workspace to production, or pushing a dev- workspace's code to its prod- counterpart.
- Installations / 1h
- 1
- GitHub Stars
- 1
- Mis à jour
- 20 oct.
factorialcofcode-ui-triggers
Surface a Factorial Code process as a button inside the Factorial product UI — the factorial.uiTrigger settings in a process's metadata.json (location id, label, icon; awaitResult at the block's top level) and the legacy uiTrigger block they replace, what the process receives when a user clicks, what a synchronous trigger returns, form-backed triggers and their file uploads, i18n labels, the icon allowlist, and how Factorial's FactorialCodeTrigger component renders them. Use when an app process
- Installations / 1h
- 1
- GitHub Stars
- 1
- Mis à jour
- 20 oct.
factorialcointegration-capability-analysis
Analyses a third-party system's API or file specification against Factorial's integrations framework and produces a detailed integration mapping document — the integration domain (payroll or finance), every capability in that domain with its verdict (fully, partially or not supported), the vendor endpoints to use for each, and the field-by-field mapping between Factorial's API and the vendor's. Use whenever someone shares a vendor API spec, OpenAPI/Swagger file, developer-portal link, integratio
- Installations / 1h
- 1
- GitHub Stars
- 1
- Mis à jour
- 20 oct.
leonardgorgesweb-typography
Typesetting judgement for web text in German and English (HTML/CSS, multi-column layouts, print stylesheets, CSS-generated PDFs). Use when writing, styling or fixing text and layout - single words stranded on a paragraph's last line (runts, Wortwaisen), headline wrapping, hyphenation, line length and leading, page margins, widows and orphans (Hurenkind, Schusterjunge) across columns and pages, fluid and responsive type sizes, type scales, choosing or pairing typefaces, quotation marks, dashes an
- Installations / 1h
- 1
- GitHub Stars
- 1
- Mis à jour
- 19 oct.
bateau84accessibility-design
Accessibility as a design input. Use WCAG 2.2 and disability-specific constraints to produce verifiable requirements for human-facing web, CLI, TUI, and desktop interfaces. Use when designing interactions, states, navigation, input, or visual information. Not for accessibility implementation (use accessibility), web rendering mechanics (use web-ui-design), or visual design (use visual-interface-design).
- Installations / 1h
- 1
- GitHub Stars
- 0
- Mis à jour
- 18 oct.
bateau84cli-design
CLI as a first-class human interface: command grammar, composability, exit semantics, stdin/stdout/stderr contracts, discoverability, help, and errors. Use when designing or reviewing developer tools, build/deployment tools, data pipelines, or system administration CLIs. Not for persistent TUIs (use tui-design), general interaction patterns (use interaction-design), or language-specific CLI implementation (use golang-cli or equivalent).
- Installations / 1h
- 1
- GitHub Stars
- 0
- Mis à jour
- 18 oct.
bateau84design-validation
Evaluate the real implemented human-facing experience against accepted design, representative Scenarios, accessibility, and usability evidence without silently redesigning it. Also use to review a proposed design before implementation for coherence, state coverage, accessibility, and implementation-ready precision.
- Installations / 1h
- 1
- GitHub Stars
- 0
- Mis à jour
- 18 oct.
bateau84experience-design
Problem framing and scenario construction — the upstream discipline that identifies the actual human problem before any interface decision is made. Use when the problem is new or poorly defined, the interface type is unclear, the stated solution might not address the real need, or the user population is broad or unfamiliar. Not for information structure or navigation (→ information-architecture), per-action interface response (→ interaction-design), task-step sequencing (→ user-flow-design), or
- Installations / 1h
- 1
- GitHub Stars
- 0
- Mis à jour
- 18 oct.
bateau84feature-handoff
Compile a compact, self-contained implementation request for another component, repository, or fresh agent session when current work depends on functionality elsewhere. Use for cross-component or cross-session handoffs such as frontend→backend, service A→service B, application→infrastructure, or one independently handled subsystem→another. Not for task orchestration, implementation plans, or authoring durable requirements and architecture (use behavioral-spec or architectural-spec for those arti
- Installations / 1h
- 1
- GitHub Stars
- 0
- Mis à jour
- 18 oct.
bateau84git-conflicts
Use when a git merge, rebase, cherry-pick, or stash stops with conflicts; when git rebase --continue refuses to proceed; when conflict markers ( ) appear; when combining changes from both sides is required; or when a rebase/merge is stuck.
- Installations / 1h
- 1
- GitHub Stars
- 0
- Mis à jour
- 18 oct.
bateau84github-action
GitHub custom action design, implementation, packaging, maintenance, release, and hardening for JavaScript, Docker container, composite, and actions that invoke bundled scripts/binaries. Use for action.yml/action.yaml and the executable implementation behind an action. Not for workflow orchestration; use github-workflow.
- Installations / 1h
- 1
- GitHub Stars
- 0
- Mis à jour
- 18 oct.
bateau84github-workflow
GitHub Actions workflow design, implementation, maintenance, and hardening for .github/workflows, reusable workflows, CI/CD triggers, jobs, permissions, runners, secrets, caches, artifacts, and deployments. Use for workflow YAML and workflow-level trust boundaries. Not for implementing a custom action itself; use github-action.
- Installations / 1h
- 1
- GitHub Stars
- 0
- Mis à jour
- 18 oct.
bateau84golang-cli
Go CLI application development — command structure, flag handling, configuration layering, version embedding, exit codes, I/O patterns, signal handling, shell completion, argument validation, and CLI unit testing. Use when building, modifying, or reviewing a Go CLI tool, picking a CLI structure, or setting up signal handling and exit codes. Not for cobra / viper APIs (→ See golang-spf13-cobra and golang-spf13-viper).
- Installations / 1h
- 1
- GitHub Stars
- 0
- Mis à jour
- 18 oct.
bateau84golang-code-style
Go code style conventions — line length, breaking, variable declarations, control flow clarity, and when comments help vs hurt. Use when writing or reviewing Go code, choosing between style alternatives, or establishing project coding standards. Not for naming conventions (→ See golang-naming), linter configuration (→ See golang-lint), or doc comments (→ See golang-documentation).
- Installations / 1h
- 1
- GitHub Stars
- 0
- Mis à jour
- 18 oct.
bateau84golang-common-practice
Go verification, code-quality posture, and skill-family conventions. Use alongside relevant golang- implementation or review skills for repository-aware checks and diagnose-before-fixing discipline.
- Installations / 1h
- 1
- GitHub Stars
- 0
- Mis à jour
- 18 oct.
bateau84golang-context
Design context propagation, debug leaks, and choose between context types in Go — cancellation, timeouts, deadlines, request-scoped values, and context.WithoutCancel. Apply when designing context propagation across API layers, debugging leaked or unexpired contexts, choosing between context.Background/TODO/WithoutCancel, or deciding what to store in context. Not for code that merely accepts ctx as first parameter.
- Installations / 1h
- 1
- GitHub Stars
- 0
- Mis à jour
- 18 oct.
bateau84golang-database
Comprehensive guide for Go database access — parameterized queries, struct scanning, NULLable columns, transactions, isolation levels, SELECT FOR UPDATE, connection pool, batch processing, context propagation, and migration tooling. Use when writing, reviewing, or debugging Golang code that interacts with PostgreSQL, MariaDB, MySQL, or SQLite; for database testing; or for questions about database/sql, sqlx, or pgx. Does NOT generate database schemas or migration SQL.
- Installations / 1h
- 1
- GitHub Stars
- 0
- Mis à jour
- 18 oct.
bateau84golang-design-patterns
Functional options, graceful shutdown, error flow and cascading, resource lifecycle, constructor APIs, resilience patterns in Go. Use when picking a Go idiom for a constructor, shutdown, or error pattern, or asking which idiomatic Go pattern fits a problem. Not for DI library choice (→ See golang-dependency-injection).
- Installations / 1h
- 1
- GitHub Stars
- 0
- Mis à jour
- 18 oct.
bateau84golang-documentation
Write godoc comments, Example tests, READMEs, CHANGELOGs, CONTRIBUTING guides, and doc sites for Go projects. Use when writing or reviewing doc comments, adding code examples, setting up a doc site, or discussing documentation best practices for Go libraries or CLIs. Not for Swagger/OpenAPI annotations (→ See golang-swagger).
- Installations / 1h
- 1
- GitHub Stars
- 0
- Mis à jour
- 18 oct.
bateau84golang-error-handling
Wrap, propagate, and inspect errors in Go — %w, errors.Is, errors.As, errors.Join, sentinel errors, custom error types, panic/recover, and the single handling rule. Use when creating or wrapping errors, designing an error API, deciding between error wrapping and panic, or inspecting errors up the call stack. Not for slog setup (→ See golang-observability).
- Installations / 1h
- 1
- GitHub Stars
- 0
- Mis à jour
- 18 oct.