senda

GitHub Actions CI pipeline conventions — job shape, caching, permissions, and action pinning. Use when asked to "set up CI", "add a GitHub Actions workflow", "fix the pipeline", or when creating/reviewing files under .github/workflows/ for Go or Node/TS projects.

Systematic root-cause debugging — reproduce, isolate, fix at the source, prove the fix. Use when the user reports a bug, an error, a crash, flaky behavior, "this doesn't work", "why is this failing", or pastes a stack trace or failing test output.

Production Go service conventions — project layout, config, slog logging, context propagation, graceful shutdown, error wrapping, plain-constructor DI, and table-driven tests. Use when building or reviewing a Go backend service or worker; triggers when the repo contains go.mod plus a long-running-process signal (HTTP/queue/DB usage, cmd/ layout), or when the user asks how to structure a Go service. For TUIs use go-tui; for desktop apps use wails3 — this skill's config/logging/error conventions still apply to their Go code.

Conventions for building Go terminal UIs with Bubble Tea v2, Bubbles v2, and Lip Gloss v2 (charm.land module path). Covers Elm-architecture discipline, tea.Cmd/tea.Msg side effects, sub-model composition, keymaps, styling, and testing. Use when writing or reviewing a Go TUI, terminal UI, or interactive CLI screen; when the user says "bubbletea", "bubbles", "lipgloss", "TUI", "terminal UI", or "charm"; or when go.mod imports charm.land/bubbletea, charm.land/bubbles, charm.land/lipgloss, or github.com/charmbracelet/bubbletea (v1 — flag for migration).

Behavior-preserving restructuring done safely — test net first, small verified steps, no mixed-in feature changes. Use when the user says "refactor", "clean up", "restructure", "extract", "rename", "split this file/function", "reduce duplication", or "make this testable".

Automated releases with conventional commits, release-please, and tag-triggered build workflows. Use when asked to "set up releases", "automate versioning", "add a changelog", "tag a release", "configure release-please", or "publish binaries on tag" — and when touching release-please-config.json, .release-please-manifest.json, .goreleaser.yml, or a CHANGELOG.md maintained by a bot.

Conventions and idioms for SolidJS 1.x and SolidStart 1.x — fine-grained reactivity, signals, control-flow components, resources, and stores. Use when writing Solid or SolidStart code, when the user says "SolidJS", "createSignal", or "Solid Start", or when the repo contains app.config.ts with @solidjs/start or solid-js in package.json.

Conventions for building Go desktop apps with Wails v3 — services, TypeScript bindings, events, windows, and packaging. Use when writing Wails v3 code, when the user says "Wails", "wails3", or "Go desktop app", or when the repo contains a Taskfile.yml alongside go.mod importing github.com/wailsapp/wails/v3 or a frontend using @wailsio/runtime.

Author tests that match the repo's stack and existing test style, at the cheapest level that catches the regression. Use when the user says "write tests for", "add test coverage", "test this function/handler/component", "this needs tests", or after implementing a feature that lacks tests.

Add frontend-callable Go backend method (Wails binding round-trip). Use whenever frontend needs new data or action from backend — new App method, regenerate bindings, api.ts wrapper, test stub, mock updates. Also use when binding call mysteriously returns undefined.

Keep frontend markup + WebKit e2e specs in sync. Use when touching component markup, CSS classes, dialogs, or adding UI spec drives — load-bearing selectors, two-mock split (devMock.ts vs mock-backend.mjs), dialog-driving rules. Also when e2e spec times out silently.

Build or modify any SolidJS list UI whose rows contain inputs, textareas, contenteditable, VarInput, or KVEditor. Enforces the <Index>-not-<For> rule and its runtime verification. Use for any new form list, row editor, key-value table, or when debugging "typing one character loses focus".

Pre-done checklist for any user-facing feature or behavior change in senda. Use before claiming a feature complete or committing — docs sweep (README, roadmap, index.html), test matrix, settings-modal and persistence gotchas.