grove-documentation_skill

Overview

This skill writes user-facing documentation, help articles, specs, and microcopy in the Grove voice. Use it whenever text will be read by Wanderers, Rooted, Pathfinders, or Wayfinders to keep tone warm, clear, and human.

How this skill works

It applies Grove rules: short paragraphs, varied sentence rhythm, and strict avoidance of AI patterns and banned words. It swaps generic terms for Grove-specific identity language, formats technical and user docs to the appropriate tone, and runs a quick checklist to remove em-dashes and awkward phrasing.

When to use it

• Writing help center articles or tooltips for the UI
• Drafting onboarding flows, email copy, and error messages
• Creating landing page or blog copy for the Grove platform
• Drafting internal specs or API docs with clear tone adjustments
• Reviewing existing documentation for voice consistency

Best practices

• Use 'Wanderer', 'Rooted', 'Pathfinder', and 'Wayfinder' instead of generic labels
• Keep paragraphs short and focused, one idea per paragraph
• Avoid the banned word list and AI patterns like 'not X, but Y'
• Use plain transitions and vary sentence length for rhythm
• End with a concise, earned closer or leave it clean

Example use cases

• A help article: clear steps for creating the first post with a simple closer
• An onboarding tooltip: one warm sentence that points to the next action
• An error message: honest statement of what happened and a next step
• A technical spec: direct parameter table with minimal warmth
• Microcopy for buttons and labels that speak to Wanderers