メニュー
Write documentation, help articles, specs, and user-facing text in the authentic Grove voice. Use when writing any text that users will read, updating help center content, or drafting specs. Ensures warmth, clarity, and avoidance of AI patterns.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Move mountains with patient strength. Wake from hibernation, gather what must move, carry it carefully, hibernate to verify, and wake again to confirm. Use when migrating anything — data, components, icons, documents, formats, or systems.
Gather scattered ideas into organized GitHub issues. The bee collects pollen from every flower, checks if the hive already has it, and carefully deposits new work in the comb for later. Never edits code—only organizes the work ahead. Use when creating issues from TODOs or planning work.
Better Auth framework reference — configuration, security, rate limiting, sessions, plugins, and production hardening. Use when configuring Better Auth, auditing auth security, adding plugins, or troubleshooting Heartwood.
Build multi-file features with unstoppable momentum. Trumpet the vision, gather materials, construct with strength, test thoroughly, and celebrate completion. Use when implementing features that span multiple files or systems.
Make your invisible work visible. The firefly drifts through your git history, gathers what you shipped into stories, glows them into human words, and helps you share them with the world. Use when you need patch notes, posts, or just want to see what you built.
The drum sounds. Hummingbird, Squirrel, Firefly, and Wren gather for a complete growth cycle — from finding opportunities to shipping findable content. Use when you want to plan and execute your content-to-discovery pipeline in one focused session.
| name | grove-documentation |
| description | Write documentation, help articles, specs, and user-facing text in the authentic Grove voice. Use when writing any text that users will read, updating help center content, or drafting specs. Ensures warmth, clarity, and avoidance of AI patterns. |
Activate this skill when:
From the project's guiding principles:
This site is my authentic voice—warm, introspective, queer, unapologetically building something meaningful; write like you're helping me speak, not perform.
Write with the warmth of a midnight tea shop and the clarity of good documentation—this is my space, make it feel like home.
Warm but not cutesy. We're friendly, not performative. "Let's get started" feels right. "Let's gooo! 🚀" does not.
Direct and honest. Say what you mean. Acknowledge limitations. Don't oversell. If something doesn't work yet, say so.
Conversational but not sloppy. Contractions are fine (you're, it's, we're). Short paragraphs. Questions that invite readers in. But still clear, still structured.
Introspective. Grove makes space for reflection. We don't rush. We ask "why" alongside "how."
Poetic in small doses. Italicized one-liners at the end of sections can land beautifully. Use them sparingly, earn them.
Mix short sentences with longer ones. Vary your rhythm. Read it aloud—if it sounds monotonous, it is.
Good:
Every new visitor asks the same question. "Is the music broken?" No. There is no music. There never has been.
Not good:
Every new visitor asks a common question. The question is usually about whether the music system is functioning. The answer is that there is no music system. There has never been one.
Grove uses specific terms for community members. Always use these in user-facing text.
| Term | Who | Context |
|---|---|---|
| Wanderer | Everyone | Default greeting, anonymous visitors, all users |
| Rooted / the Rooted | Subscribers | Those who've planted their tree, paid users |
| Pathfinder | Trusted guides | Appointed community helpers |
| Wayfinder | Autumn (singular) | The grove keeper |
{{name}}, not "Wanderer".Good:
Avoid:
Wanderer → Wayfinder reflects the journey:
See docs/grove-user-identity.md for full documentation.
When writing text that includes Grove terminology in UI or content, use GroveTerm components instead of hardcoding terms. Grove Mode lets users toggle between standard terms (default for new visitors) and Grove terms.
For Svelte UI: Use GroveTerm, GroveSwap, or GroveText components from @autumnsgrove/lattice/ui.
For data-driven content (FAQ items, pricing text, help articles): Use [[term]] syntax. Examples:
"Your [[bloom|posts]] are always yours." renders "posts" when Grove Mode is OFF, "blooms" when ON"Visit your [[arbor|dashboard]] to get started." renders "dashboard" or "Arbor""Ask a [[pathfinder|community guide]] for help." renders "community guide" or "Pathfinder"For markdown content (help center articles): The rehype-groveterm plugin transforms [[term]] syntax in markdown automatically.
Key principle: New visitors should see familiar, standard terminology. Grove's nature-themed vocabulary is opt-in, not forced. This keeps the platform accessible and welcoming while rewarding those who want to explore the ecosystem's personality.
These patterns make text sound like AI wrote it. Avoid them completely.
The full anti-patterns reference lives in owl-archive/references/anti-patterns.md. Here's a quick summary of the most critical avoidances.
-> not → in prose.Keep them short. One idea per paragraph. Two to four sentences is usually right.
White space is your friend. Dense walls of text don't feel like home.
Use lists when they clarify. But don't turn everything into bullets. Sometimes prose flows better.
Good use of lists:
Bad use of lists:
Be specific. "Writing Guidelines" is better than "Guidelines." "What Grove Sounds Like" is better than "Voice."
Action-oriented headers work well for help docs: "Add Your First Post" not "Posts."
Use sparingly. When you do:
💡 Tip: Helpful suggestion that enhances understanding.
⚠️ Warning: Something that could cause problems if ignored.
Don't use callouts for things that should just be in the text.
Grove docs often end with an italicized line. This should feel earned, not forced.
Works:
Sometimes the most radical thing you can offer is nothing at all.
The path becomes clear by walking it.
Doesn't work:
And that's how you configure your settings!
If you can't find a poetic closer that resonates, don't force one. A clean ending is fine.
Grove is explicitly queer-friendly. This means:
| Avoid | Use Instead |
|---|---|
| "Add your husband/wife" | "Add your partner" or "Add someone special" |
| "he or she" | "they" or rephrase to avoid pronouns |
| "Dear Sir/Madam" | "Hello" or "Hi there" |
| "mankind" | "people" or "everyone" |
| Examples with only straight couples | Vary your examples, or keep them neutral |
When asking for relationship info (if ever needed):
We don't make a big deal of being queer-friendly. We just are. No rainbow-washing, no performative allyship. The inclusivity is baked in, not bolted on.
Specs and internal docs can be more matter-of-fact. Tables, schemas, API references—these need clarity over warmth.
User-facing docs (help center, onboarding, error messages) carry the full Grove voice.
Both should avoid AI patterns.
API Reference (minimal warmth, maximum clarity):
POST /api/posts
Creates a new blog post.
Parameters:
- title (string, required): Post title
- content (string, required): Markdown content
- published (boolean): Default false
Returns: Post object or 400 error
Internal Spec (clear, some personality):
## Feed Caching Strategy
Feed pages cache for 5 minutes in KV. When a new post is shared,
we invalidate the chronological feed but let popular/hot feeds
age out naturally. This keeps things fresh without hammering D1.
Getting Started Guide (full Grove voice):
## Your First Post
Welcome. Let's get something published.
The editor opens to a blank page. That's intentional. No templates,
no suggested topics. Just you and your words.
Write something. Anything. Hit publish when it feels ready.
Onboarding Tooltip (warm but concise):
This is your dashboard. Everything you need, nothing you don't.
When things break, stay warm but be honest. Don't blame the user. Don't hide behind vague language.
Good:
Couldn't save your post. Check your connection and try again.
That page doesn't exist. It may have been moved or deleted.
Something went wrong on our end. We're looking into it.
Your draft is saved locally.
Avoid:
Oops! 😅 Looks like something went wrong! Don't worry though,
these things happen! Please try again later!
Error 500: Internal Server Error. Contact administrator.
We're SO sorry!!! We feel TERRIBLE about this!!!
Please forgive us and try again!
Be honest about what broke. Be helpful about next steps. Don't make them feel stupid. Don't make yourself sound incompetent. One sentence is usually enough.
Before finalizing any Grove documentation:
When grove-ui-design or walking-through-the-grove need written content, invoke this skill first. The visual design and naming should match the voice.
Typical flow:
grove-documentation for voice guidanceThis skill (grove-documentation) is for quick, functional text: help articles, error messages, tooltips, onboarding copy. Content that's read in passing.
Use museum-documentation when you need narrative, explorable documentation:
| Use grove-documentation | Use museum-documentation |
|---|---|
| Help center articles | Knowledge base "how it works" |
| Tooltips and labels | Codebase guided tours |
| Error messages | System architecture explains |
| Onboarding flows | Technical deep-dives for curious Wanderers |
| Quick-reference guides | Exhibit-style documentation |
If the reader should skim and act, use this skill. If the reader should explore and understand, use museum-documentation.
# Your First Post
Welcome. Let's get something published.
From your admin panel, click **New Post** in the sidebar. The editor opens with a blank canvas.
Write in Markdown. If you're new to it, here are the basics:
- **Bold:** `**text**`
- _Italic:_ `*text*`
- Links: `[text](url)`
The preview panel shows how your post will look. Toggle it with the eye icon.
When you're ready, hit **Publish**. Your words are live.
_The blank page isn't as scary as it looks._
# Your First Post
Furthermore, in today's digital landscape, creating your first blog post is an exciting journey! It's not just about writing—it's about expressing yourself in a transformative way.
Navigate to your admin panel and leverage the New Post functionality. The seamless editor provides a robust interface for your content creation needs.
Additionally, Grove utilizes Markdown—a comprehensive formatting system that empowers you to create intricate, captivating content. Moreover, the preview feature allows you to visualize your post before publication.
Embark on your blogging journey today!
This one's trickier. It looks okay at first glance:
# Your First Post
Ready to share your thoughts with the world? Let's get started.
From your admin panel, click **New Post** in the sidebar. You'll see our editor—a clean, distraction-free space for your writing.
Grove uses Markdown for formatting. It's not complicated—here are the basics you'll need:
- **Bold:** `**text**`
- _Italic:_ `*text*`
- Links: `[text](url)`
The preview panel lets you see how your post will look before publishing. When you're satisfied with your work, hit **Publish**.
Your voice matters. We can't wait to see what you create.
What's wrong:
| Do | Don't |
|---|---|
| Write short paragraphs | Write walls of text |
| Use "and," "but," "so" | Use "Furthermore," "Moreover" |
| Say what you mean | Hedge with "may," "might," "could" |
| Vary sentence rhythm | Write uniform sentence lengths |
| Use commas or periods | Use em-dashes |
| Let ideas connect naturally | Force transitions everywhere |
| Earn poetic closers | Force poetic closers |
| Acknowledge limitations | Oversell or overpromise |
Write like you're explaining something to a friend at 2 AM. Clear, warm, honest.