Multi-file
writingOfficial
Official Provider SkillView repo
Use when adding triple-slash comments to Swift types, methods, or properties; creating a .docc catalog folder; writing articles or extension files for a Swift package; fixing DocC build warnings about broken symbol links or missing documentation; or setting up module-level documentation for the first time.
Files2 files
SKILL.md202 lines
Loading editor…
Install
RecommendedOne command — your agent picks it up automatically.
Select an AI agent above to see the install command.
or
Manual Install
More stepsDownload the archive and add the files to your project manually.
Skill details
Versionv1.0.0
AuthorSupabase
Categorywriting
Skill IDsupabase/supabase-swift/.claude/skills/swift-docc
Files2 files
Related skills
Swift Api Design GuidelinesUse whenever you write, name, or review any public (or internal-but-API-shaped) Swift declaration in this repo — a method, function, initializer, property, protocol, or parameter — and especially before opening a PR that adds or renames public API. Covers naming clarity, argument labels, factory/initializer conventions, boolean and mutating/nonmutating naming, and terms of art, per https://www.swift.org/documentation/api-design-guidelines/. Also use when reviewing a PR's diff for naming issues, Writing Migration GuidesUse when a change is a breaking change — a `fix!:`/`feat!:` commit, a `BREAKING CHANGE:` footer, or any edit that changes a public API's shape or behavior — and needs an entry in the root `V<N>_MIGRATION.md` file. Also use when reviewing a PR that has one, to check it against this format.Docs Eval PlanningPlan a documentation eval for supabase/evals, where a docs guide is the subject under test. Use when asked to write, add, or design an eval for a Supabase docs guide, when a ticket asks for a deterministic eval on a page, or when deciding what a guide-under-test eval should check. Produces a plan, not files. Not for debugging a scorer, running an eval, or writing example solutions.Writing ChangelogsGuides the writing and editing of changelog entries in the per-module CHANGELOG.md files. Use when a user-facing change needs an entry, when drafting or reshaping an Unreleased section, or when reviewing entries at release time. Covers the type headings, the entry shape and the succinctness bar - what an entry says and what it leaves to the docs.Feature TryoutsUse when adding, reviewing, or troubleshooting an interactive release-note Try This experience, including commands, views, editor samples, Chat drafts, guided spotlights, prerequisites, scoped targets, or Agents-window handoff.Natural WritingContains well-defined rules for creating natural, accurate, and readable writing. Use whenever authoring longer text, like analysis documents, PR or CL descriptions, or documentation.