documentation-writer
Documentation Writer
Use this skill for all docs edits in src/routes/(docs)/docs/content/ and when updating docs navigation in src/routes/(docs)/docs.json.
Non-negotiable rules
- Be concise: remove repetition and background that does not help the user complete a task.
- Be actionable: prioritize “what to do” over theory.
- One source of truth: if another page already has details, link to it instead of duplicating.
- Preserve structure: keep valid frontmatter and heading anchor IDs.
- Keep examples copyable: minimal, tested-looking, and directly relevant.
- Search before writing: always check if the content already exists in some form before adding new sections or pages.
- Check Relevant Code: Search the codebase inside
src/for any relevant code, comments, or tests that can inform the documentation content and ensure accuracy.
Docs config model (current)
docs.json is versioned. Sidebar lives inside tabs:
versions[].content.navigation.tabs[].sidebar
More from rajnandan1/kener
tailwindcss
Tailwind CSS v4 utility-first styling patterns including responsive design, dark mode, and custom configuration. Use when styling with Tailwind, adding utility classes, configuring Tailwind, setting up dark mode, or customizing the theme.
20svelte-code-writer
CLI tools for Svelte 5 documentation lookup and code analysis. MUST be used whenever creating or editing 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.
12ss-shadcn-svelte
>
2code-context
Persistent code architecture documentation via a `.codecontext/` folder.
1