bateau84
68 skills with substantive source documentation and an official publisher or observed installation demand. Read each skill’s original documentation through its card.
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).
- installs
- 1
- GitHub stars
- 0
- Updated
- Oct 18
bateau84behavioral-spec
Derive bounded, implementation-independent requirements from agreed product intent through goal refinement, coverage lenses, obstacle analysis, provenance tracking, and counterexample checks. Use to select, author, and reconcile Behavioral Requirements (BR), Quality Scenarios (QS), and Obligation Contracts (OC) without expanding scope. Not for concrete API/schema/protocol realization (use architectural-spec) or human-centered stories and scenarios (use user-stories-and-scenarios).
- installs
- 1
- GitHub stars
- 0
- Updated
- Oct 18
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).
- installs
- 1
- GitHub stars
- 0
- Updated
- Oct 18
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.
- installs
- 1
- GitHub stars
- 0
- Updated
- Oct 18
bateau84desktop-ui-design
Desktop GUI design for native and hybrid applications: platform conventions (macOS HIG, Windows Fluent, GNOME HIG), menus, keyboard shortcuts, window management, session persistence, native vs Electron/Tauri trade-offs, and accessibility APIs. Use for Swift/AppKit, C/WinUI, GTK+, or Electron/Tauri/Flutter desktop design. Add web-ui-design for a web app shipped as a desktop wrapper. Not for browser-only interfaces, terminal applications (use tui-design), or command-line tools (use cli-design).
- installs
- 1
- GitHub stars
- 0
- Updated
- Oct 18
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
- installs
- 1
- GitHub stars
- 0
- Updated
- Oct 18
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
- installs
- 1
- GitHub stars
- 0
- Updated
- Oct 18
bateau84git-commit-discipline
Small coherent commits, explanatory messages, shared-working-tree discipline, and safe undo/recovery. Use when asked to commit, when a diff mixes concerns, when agents share a working tree, or when undoing or recovering Git changes. Not for content conflicts (use git-conflicts).
- installs
- 1
- GitHub stars
- 0
- Updated
- Oct 18
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.
- installs
- 1
- GitHub stars
- 0
- Updated
- Oct 18
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.
- installs
- 1
- GitHub stars
- 0
- Updated
- Oct 18
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.
- installs
- 1
- GitHub stars
- 0
- Updated
- Oct 18
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).
- installs
- 1
- GitHub stars
- 0
- Updated
- Oct 18
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).
- installs
- 1
- GitHub stars
- 0
- Updated
- Oct 18
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.
- installs
- 1
- GitHub stars
- 0
- Updated
- Oct 18
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.
- installs
- 1
- GitHub stars
- 0
- Updated
- Oct 18
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.
- installs
- 1
- GitHub stars
- 0
- Updated
- Oct 18
bateau84golang-dependency-injection
google/wire, uber-go/dig, uber-go/fx, samber/do, manual constructor injection, and service containers in Go. Use when designing service architecture, setting up dependency injection, refactoring tightly coupled code, or managing singletons and service factories.
- installs
- 1
- GitHub stars
- 0
- Updated
- Oct 18
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).
- installs
- 1
- GitHub stars
- 0
- Updated
- Oct 18
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).
- installs
- 1
- GitHub stars
- 0
- Updated
- Oct 18
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).
- installs
- 1
- GitHub stars
- 0
- Updated
- Oct 18
bateau84golang-grpc
Implement and review gRPC servers and clients in Go — protobuf organization, interceptors, status-code error handling, TLS/mTLS, bufconn testing, and streaming RPCs. Use when writing proto files, setting up gRPC interceptors, handling gRPC errors with status codes, or configuring mTLS. Not for general Go API design (→ See golang-design-patterns).
- installs
- 1
- GitHub stars
- 0
- Updated
- Oct 18
bateau84golang-lint
Linting best practices and golangci-lint configuration for Golang projects — running linters, configuring .golangci.yml, suppressing warnings with nolint directives, interpreting lint output, and selecting linters. Use when configuring golangci-lint, asking about lint warnings or nolint suppressions, setting up code quality tooling, or choosing linters. Also use when the user mentions golangci-lint, go vet, staticcheck, or revive.
- installs
- 1
- GitHub stars
- 0
- Updated
- Oct 18
bateau84golang-modernize
Modernize Go code to use recent language features, standard library improvements, and idiomatic patterns. Trigger when old-style patterns are detected or when encountering deprecation warnings. Also use when the user explicitly asks for modernization, a Go version upgrade, or a CI/tooling refresh.
- installs
- 1
- GitHub stars
- 0
- Updated
- Oct 18
bateau84golang-observability
Go production observability — structured logging with slog, Prometheus metrics, OpenTelemetry tracing, continuous profiling with pprof/Pyroscope, alerting, and Grafana dashboards. Use when instrumenting a Go service for production monitoring, adding metrics or tracing, migrating from zap/logrus/zerolog to slog, correlating logs and traces, or setting up alerting. Not for benchmark profiling (→ See golang-benchmark), or optimization patterns (→ See golang-performance).
- installs
- 1
- GitHub stars
- 0
- Updated
- Oct 18