chatto

Keep track of architectural decisions in a structured format using Architecture Decision Records (ADRs).

Run a full review of all Architecture Decision Records for implementation drift, contradictions, stale decisions, missing supersession notes, weak rationale, and missing cross-references. Use when the user asks for an ADR review, ADR audit, stale ADR check, architecture decision consistency check, or wants to verify ADRs against the current codebase, feature/design records, architecture docs, glossary, or public API state.

Invoke this skill when the user asks you to develop a feature back-to-back, with all the trimmings. This skill defines a full feature development workflow that includes code reviews, branch management, and ends in a fully fleshed-out PR.

Review Chatto public API and protocol changes for compatibility, migration needs, and generated output.

Design rules concerning Chatto's ConnectRPC API, both resources and realtime

Maintain Chatto runtime documentation in docs/architecture/ when runtime structures change, or audit it when requested.

Audit Chatto API design for consistency, completeness, integration use, and future growth. Use for a whole-API review or a focused review of a service or workflow.

Decide whether Chatto client code goes into `@chatto/client` (packages/chatto-client) or the bundled frontend (apps/frontend). Use before you add a request, store, state, helper, or protocol rule to either, or when you move code between them.

Use when designing, implementing, reviewing, debugging, or documenting Chatto event-sourced domain behavior, including EVT subjects, aggregate boundaries, Services, projections, optimistic concurrency control, read-your-writes, live/reconnect delivery, replay compatibility, migration safety, and rollback/deployment implications.

Review Chatto frontend implementation quality, including Svelte reactivity and lifecycle, component boundaries, design-system reuse, and unnecessary complexity. Use for every review that includes apps/frontend, including self-review, branch or PR review, and frontend architecture review.

Check a Chatto pull request before review or merge. Use when opening a PR or when asked to check one.

Create or update Chatto release pages from release-please state, tags, changelog entries, and PRs.

After successfully posting a PR from this git worktree, we now want to work on a new one.

Keep track of product or project features as Feature Decision Records (FDRs): one structured document per feature capturing behavior, design decisions, and rationale.

Maintain a project's glossary of domain terms, usually in docs/GLOSSARY.md. Use when looking up terms, adding or updating definitions, renaming concepts, or auditing a glossary against repository docs, code, and decision records for missing, stale, duplicated, or misplaced entries.

Write or revise JavaScript and TypeScript source, including scripts, tests, and Svelte modules. Apply its documentation and Prettier practices.

Apply the repository-wide Loom Architecture—Log-Oriented Outcomes and Materializations—when designing, implementing, reviewing, debugging, or documenting NATS and JetStream event-sourced applications. Use for work involving NATS account boundaries, a primary event stream, optimistic concurrency control, projections and read-your-writes, snapshots or checkpoints, snapshot repositories, durable workers, or reliable external effects.

A skill that provides a guided tour of a pull request, highlighting key changes, walking the developer through the code, and explaining the purpose of each modification.

Review a completed, paused, or blocked coding-agent session to identify friction, mistakes, near misses, missing context, and opportunities to improve future work. Use when the user asks to wrap up, run a retrospective, explain what issues the agent faced, capture lessons learned, or recommend improvements to repository instructions, documentation, skills, tooling, tests, or workflows. Produce an evidence-based, propose-only report; do not apply follow-up changes unless the user asks.

CLI tools for Svelte 5 documentation lookup and code analysis. MUST be used whenever creating, editing or analyzing any Svelte component (.svelte) or Svelte module (.svelte.ts/.svelte.js). If possible, this skill should be executed within the svelte-file-editor agent for optimal results.