AGENT SKILLS · EQUIPAGGIAMENTO / bateau84

bateau84 · Agent Skills

68 skills with substantive source documentation and an official publisher or observed installation demand. Read each skill’s original documentation through its card.

bateau84
Community

python-fastapi

Building HTTP APIs with FastAPI — APIRouter organization, path/query/body params, Pydantic request/response models, dependency injection with Depends, app.state and lifespan, HTTPException and error responses, status codes, async vs sync endpoints, and the auto-generated OpenAPI/Swagger docs. Use when adding or reviewing FastAPI routes, wiring dependencies, shaping request/response models, structuring an API package, or documenting an HTTP API. Also use when the user mentions FastAPI, uvicorn, A

installazioni
1
GitHub Stars
0
Aggiornato
18 ott
bateau84
Community

python-observability

Production observability for Python services — structured JSON logging (stdlib logging + python-json-logger), log levels and the named-logger hierarchy, Prometheus metrics with prometheus-client (Counter/Gauge/Histogram), a /metrics endpoint, correlation/context fields, and OpenTelemetry tracing. Use when adding logging, instrumenting metrics, exposing a metrics endpoint, designing log structure, or wiring tracing into a Python service. Also use when the user mentions logging, structured logs, P

installazioni
1
GitHub Stars
0
Aggiornato
18 ott
bateau84
Community

python-type-checking

Static typing for Python — type hints, generics, Optional/None handling, Union and the X | Y syntax, Literal, Protocol (structural typing), TypedDict, typing.cast, gradual typing, and running a static checker (mypy, ty, or pyright) in CI. Use when adding type annotations, fixing type-checker errors, designing typed interfaces, modeling None-safety, or configuring static type analysis. Also use when the user mentions mypy, pyright, ty, type hints, typing, Protocol, or generics in Python.

installazioni
1
GitHub Stars
0
Aggiornato
18 ott
bateau84
Community

retrospective

Facilitate a retrospective (retro, coding-session retro, sprint retro, lessons learned) after a coding session, milestone, sprint, incident response, or meaningful batch of engineering or agent work. Use to examine what worked, what was difficult, what to preserve, and what to try next. Not for deliverable acceptance, incident root-cause diagnosis, or memory cleanup alone.

installazioni
1
GitHub Stars
0
Aggiornato
18 ott
bateau84
Community

risk-driven-planning

Front-load decisive uncertainty during product discovery, solution development, and task planning. Use when an assumption could invalidate dependent commitments; not for routine detail or a new gate.

installazioni
1
GitHub Stars
0
Aggiornato
18 ott
bateau84
Community

skill-authoring

Author and maintain reusable, agent-neutral skills. Use when creating, porting, editing, auditing, or packaging SKILL.md files and supporting references. Not for agent role policy (use agent-file-authoring).

installazioni
1
GitHub Stars
0
Aggiornato
18 ott
bateau84
Community

synabun-memory

Use Synabun memory tools to recall engineering experience, preserve proven architecture and hard-won implementation lessons, learn from failures, and curate stale or duplicate memories. Use when past experience may change an approach, a reusable lesson has been verified, the user asks to remember something, or memory cleanup is requested. Not a session journal or a guide to Synabun's other tools.

installazioni
1
GitHub Stars
0
Aggiornato
18 ott
bateau84
Community

terraform-module-testing

Comprehensive guide for writing and running Terraform module tests (.tftest.hcl). Use when creating test files, writing test scenarios with run blocks, validating infrastructure behavior with assertions, mocking providers and data sources, testing module outputs and resource configurations, or troubleshooting Terraform test syntax and execution. For Terraform provider acceptance tests (Go code), use terraform-provider-testing.

installazioni
1
GitHub Stars
0
Aggiornato
18 ott
bateau84
Community

terraform-provider-docs

Create, update, and review Terraform provider documentation for Terraform Registry using HashiCorp-recommended patterns, tfplugindocs templates, and schema descriptions. Use when adding or changing provider configuration, resources, data sources, ephemeral resources, list resources, functions, or guides; when validating generated docs; and when troubleshooting missing or incorrect Registry documentation.

installazioni
1
GitHub Stars
0
Aggiornato
18 ott
bateau84
Community

terraform-provider-resources

Implement Terraform Provider resources and data sources using the Plugin Framework. Use when developing CRUD operations, schema design, state management, and acceptance testing for provider resources.

installazioni
1
GitHub Stars
0
Aggiornato
18 ott
bateau84
Community

terraform-provider-testing

Terraform provider acceptance test patterns using terraform-plugin-testing with the Plugin Framework. Covers test structure, TestCase/TestStep fields, ConfigStateChecks with custom statecheck.StateCheck implementations, plan checks, CompareValue for cross-step assertions, config helpers, import testing with ImportStateKind, sweepers, and scenario patterns (basic, update, disappears, validation, regression), and ephemeral resource testing with the echoprovider package. Use when writing, reviewing

installazioni
1
GitHub Stars
0
Aggiornato
18 ott
bateau84
Community

tui-design

Design, build, refactor, or review terminal interfaces: full-screen TUIs, interactive prompts, and command-line tools. Covers terminal constraints, keyboard interaction, focus, key bindings, color, accessibility, and framework implementation with Bubble Tea, Ratatui, Textual, or Ink. Use for terminal-app layout and UX, CLI behavior, ncurses-style tools, dashboards, REPLs, fzf-like pickers, and requests naming lazygit, k9s, btop, helix, or yazi. Not for browser/web UI, native GUI, editor/font con

installazioni
1
GitHub Stars
0
Aggiornato
18 ott
bateau84
Community

typescript-async

Asynchronous TypeScript correctness: Promise ownership, awaiting/returning work, async collection patterns, scheduler-sensitive state, cancellation with AbortSignal, cleanup, Promise combinator semantics, timeouts, bounded concurrency, and rejection propagation. Use when a TypeScript change starts, coordinates, cancels, races, retries, or observes asynchronous work.

installazioni
1
GitHub Stars
0
Aggiornato
18 ott
bateau84
Community

typescript-common-practice

Baseline TypeScript engineering practice for strict projects: use the repository compiler/toolchain as a contract, keep types close to domain meaning, prefer inference without obscuring public APIs, preserve module boundaries, avoid speculative type architecture, and run the TypeScript-specific verification loop. Use for implementation or refactoring of TypeScript source.

installazioni
1
GitHub Stars
0
Aggiornato
18 ott
bateau84
Community

typescript-testing

TypeScript/JavaScript testing mechanics across Bun test, Vitest, Jest, and similar runners: awaited async assertions, deterministic timers and concurrency, module/global mock isolation, runtime-vs-type-level tests, environment selection, regression tests, targeted mutation testing, and false-green avoidance. Use when writing or reviewing tests for TypeScript/JavaScript code. Pair with test-driven-development for red-green-refactor process.

installazioni
1
GitHub Stars
0
Aggiornato
18 ott
bateau84
Community

user-flow-design

Task-level state sequences — the path a user takes through steps, decisions, branches, and outcomes across a task or workflow. Use when users must move through more than one view or state to accomplish a goal; when entry points, decision points, or error recovery paths matter; when designing CLI pipelines or TUI navigation between views. Not for per-action response within a single view (→ interaction-design), structural organization of content or commands (→ information-architecture), or cross-c

installazioni
1
GitHub Stars
0
Aggiornato
18 ott
bateau84
Community

user-stories-and-scenarios

Capture small human-centered User Stories and concrete end-to-end design Scenarios (including a meaningful failure, interruption, or edge condition) from agreed product intent. Use for durable US/SC design artifacts. Not for system requirements or measurable quality scenarios (use behavioral-spec), or implementation design.

installazioni
1
GitHub Stars
0
Aggiornato
18 ott
bateau84
Community

visual-companion

Browser-based visual brainstorming companion for showing mockups, diagrams, and interactive A/B/C choices during conversation. Use when a question would be clearer shown than described — UI mockups, wireframes, architecture diagrams, side-by-side comparisons, flowcharts.

installazioni
1
GitHub Stars
0
Aggiornato
18 ott
bateau84
Community

web-ui-design

Web-specific interface design: browser behavior, URLs as UX, document vs app models, forms, responsive interactions, and accessibility patterns. Use for SPAs, multi-page apps, forms, dashboards, and admin interfaces. Add visual-interface-design for visual reasoning. Not for CLI design, TUI design, native desktop GUI, or pure content sites with no interaction beyond navigation.

installazioni
1
GitHub Stars
0
Aggiornato
18 ott
bateau84
Community

work-decomposition

Find coherent, context-bounded work groups, change surfaces, and dependencies before creating a delivery plan. Use when agreed work admits several splits, oversized execution units, one-task-per-file fragmentation, hidden integration work, or shared-state parallelism risks. Not for inventing product requirements or fixed scheduling policy.

installazioni
1
GitHub Stars
0
Aggiornato
18 ott