Menu
Use this if you want to look up Svelte, SvelteKit, and Svelte CLI documentation.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
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.
Create or update Chatto docs website release pages by comparing release-please state, tags, commits, changelog entries, and PRs
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.
Update docs/ARCHITECTURE.md to reflect the current state of the codebase by examining code and documentation.
Run a documentation-focused maintenance checkup of the Chatto codebase. Fans out to /fdr, /adr, and /chatto-architecture, then compiles a single consolidated report. Always propose-only — no changes applied without explicit user approval. At the end, points the human at other maintenance skills (/update-project-dependencies, /chatto-security-review) they may want to run themselves.
Production debugging tools for NATS streams, KV buckets, and protobuf events. Covers nats CLI commands, stream inspection, protobuf decoding, and message iteration.
| name | svelte-docs |
| description | Use this if you want to look up Svelte, SvelteKit, and Svelte CLI documentation. |
Look up Svelte, SvelteKit, and Svelte CLI documentation from the official LLM-optimized docs at svelte.dev.
Start with compressed documentation to minimize context usage:
Fetch https://svelte.dev/llms-small.txt using the WebFetch tool.
If the answer is unclear or more detail is needed, escalate to medium docs:
Fetch https://svelte.dev/llms-medium.txt
For comprehensive reference (only when necessary):
Fetch https://svelte.dev/llms-full.txt
When you know the question is about a specific package, use targeted docs:
https://svelte.dev/docs/svelte/llms-small.txt or https://svelte.dev/docs/svelte/llms.txthttps://svelte.dev/docs/kit/llms-small.txt or https://svelte.dev/docs/kit/llms.txthttps://svelte.dev/docs/cli/llms.txtWhen fetching documentation, use a prompt that extracts the relevant information:
WebFetch url: https://svelte.dev/llms-small.txt
prompt: "Find information about [topic]. Extract relevant code examples and explanations."
If arguments are provided, interpret them as:
svelte - Fetch only Svelte docs (not SvelteKit)kit or sveltekit - Fetch only SvelteKit docscli - Fetch only CLI docsfull - Skip to full documentation immediatelymedium - Start with medium documentation