重要前提
安装AI Skills的关键前提是:必须科学上网,且开启TUN模式,这一点至关重要,直接决定安装能否顺利完成,在此郑重提醒三遍:科学上网,科学上网,科学上网。查看完整安装教程 →
walking-through-the-grove by autumnsgrove/groveengine
npx skills add https://github.com/autumnsgrove/groveengine --skill walking-through-the-grove为 Grove 生态系统命名的仪式。当你需要一个 契合 的名字时使用它——不仅仅是一个聪明的双关语,而是属于这片森林的东西。
grove-ui-design 技能遇到需要命名的新 UI 时调用这是一次 旅程 ,而不是一份清单。请慢慢来。
# 总是从这里开始
cat docs/philosophy/grove-naming.md
阅读整个文档。不要略读。用心体会:
为你的旅程创建一个 Markdown 文件:
mkdir -p docs/scratch
# 创建:docs/scratch/{概念}-命名旅程.md
这个草稿本是你自言自语的地方。包括:
广告位招租
在这里展示您的产品或服务
触达数万 AI 开发者,精准高效
在你的草稿本里,画出林间。ASCII 艺术很有帮助:
☀️
🌲 🌲 🌲
🌲 🌳 🌲
═══════════════════════════════════════════════
根系在下方连接
(菌丝网络)
将现有服务放在可视化图中:
不要先问“它该放在哪里?”。问:
从根本上说,它是什么?
它在用户生活中做什么?
它应该唤起什么情感?
想象你是一个在林间漫步的用户。在你的草稿本里写下:
## 漫步穿过...
我进入林间。我看到...
我走过 Meadow,那里有人聚集。
我找到我的树——我的博客,我的空间。
我查看我的 Rings(私密成长)。
我看到我的 Foliage(别人眼中的我)。
现在我需要 [新事物]。我在哪里找到它?
它看起来像什么?谁在那里?感觉如何?
让这个场景引导你找到名字。
根据你的漫步,列出 5-10 个候选名。对每一个:
**[名称]** - `[名称].grove.place`
- 它在自然界中的含义
- 为什么它适合这个概念
- 氛围/感觉
- 潜在问题
一个好的 Grove 名字应该能自然地完成这个句子:
"[名称] 是你 ****** ___****** 的地方。"
或者:
"[名称] 是 ****** ___******。"
如果你写不出一句诗意的单行描述,这个名字可能就不合适。
一旦你找到了名字,用 Grove 风格写下来:
## [名称]
**[标语]** · `[域名].grove.place`
[2-3 句话解释这个东西在现实世界中是什么——自然的隐喻。然后 2-3 句话解释它在 Grove 中做什么。以它应该唤起的感觉结尾。]
_[一句诗意的斜体单行描述]_
在最终确定之前:
更新所有文件:
docs/grove-naming.md — 添加完整条目docs/philosophy/grove-naming.md — 更新源文件(生成清单)services/grove-router/src/index.ts — 声明子域名plant/src/routes/api/check-username/+server.ts — 保留用户名scripts/generate/grove-term-manifest.ts 以使用新术语重建 grove-term-manifest.json。此清单为所有 GroveTerm 组件(GroveTerm、GroveSwap、GroveText 等)提供支持,这些组件根据用户的 Grove 模式设置自动在标准和 Grove 术语之间切换。来自命名文档:
"这些名字有共同点:自然、庇护、生长的事物。但它们都不直接 关于 树木。它们关于在森林里和周围发生的事情。"
"Grove 是这个地方。这些是你在那里找到的东西。"
这个名字应该感觉 理所当然 ——就像它一直在那里,等待着被发现。
问题:我们需要为支持工单命名。
最初的尝试(被否决):
漫步:
我在林间。我的树出了点问题。我需要帮助。Waystone 给我自助指南。Clearing 显示状态。但我需要实际 和某人谈谈。
我该怎么做?
我走到……一个小木屋。那里有个门廊。有人在那里。我坐下来。我们谈论发生了什么。
领悟: 支持不是一个工单系统。它是一次门廊上的谈话。
名字: Porch
树林中木屋的门廊。你走上台阶。你坐下来。林间守护者走出来。你们交谈。
"在门廊上坐坐。我们一起想办法解决。"
当 grove-ui-design 技能遇到需要命名的事物时:
这确保了命名是有意为之,而不是仓促决定。
找到合适的名字后,你需要撰写它的描述。在以下情况下调用 grove-documentation 技能:
docs/grove-naming.md 撰写条目时命名文档条目应遵循 Grove 的语调:温暖、直接,避免 AI 模式。grove-documentation 技能有完整的指南。
保留你的草稿本文件。它们记录了我们对 Grove 的思考方式:
docs/scratch/
grove-journey.md ← 最初的 Porch 发现过程
{功能}-naming.md ← 未来的命名旅程
这些成为 Grove 故事的一部分。
每周安装次数
50
仓库
GitHub 星标数
2
首次出现
2026年2月5日
安全审计
安装于
opencode50
gemini-cli50
codex50
codebuddy49
github-copilot49
amp49
A naming ritual for the Grove ecosystem. Use this when you need to find a name that fits —not just a clever pun, but something that belongs in this forest.
grove-ui-design skill when new UI needs a nameThis is a journey , not a checklist. Take your time.
# Always start here
cat docs/philosophy/grove-naming.md
Read the entire document. Don't skim. Let it sink in:
Create a markdown file for your journey:
mkdir -p docs/scratch
# Create: docs/scratch/{concept}-naming-journey.md
This scratchpad is where you think out loud. Include:
In your scratchpad, draw the grove. ASCII art helps:
☀️
🌲 🌲 🌲
🌲 🌳 🌲
═══════════════════════════════════════════════
ROOTS CONNECT BENEATH
(mycelium network)
Place the existing services in the visualization:
Don't ask "where does it go?" first. Ask:
What is it, fundamentally?
What does it DO in the user's life?
What emotion should it evoke?
Imagine you're a user walking through the grove. Write this in your scratchpad:
## Walking Through...
I enter the grove. I see...
I walk past the Meadow where others gather.
I find my tree—my blog, my space.
I check my Rings (private growth).
I see my Foliage (how others see me).
Now I need [THE NEW THING]. Where do I find it?
What does it look like? Who's there? How does it feel?
Let the scene guide you to the name.
Based on your walk, list 5-10 candidates. For each:
**[Name]** - `[name].grove.place`
- What it means in nature
- Why it fits this concept
- The vibe/feeling
- Potential issues
A good Grove name should complete this sentence naturally:
"[Name] is where you ****** ___******."
Or:
"[Name] is the ****** ___******."
If you can't write a poetic one-liner, the name might not fit.
Once you've found the name, write it in Grove style:
## [Name]
**[Tagline]** · `[domain].grove.place`
[2-3 sentences explaining what this thing IS in the real world—
the natural metaphor. Then 2-3 sentences explaining what it does
in Grove. End with the feeling it should evoke.]
_[A poetic one-liner in italics]_
Before finalizing:
Update all the files:
docs/grove-naming.md — Add the full entrydocs/philosophy/grove-naming.md — Update source (generates manifest)services/grove-router/src/index.ts — Claim subdomainplant/src/routes/api/check-username/+server.ts — Reserve usernamescripts/generate/grove-term-manifest.ts to rebuild grove-term-manifest.json with the new term. This manifest powers all GroveTerm components (GroveTerm, GroveSwap, GroveText, etc.) that automatically switch between standard and Grove terminology based on the user's Grove Mode setting.From the naming document:
"These names share common ground: nature, shelter, things that grow. But none of them are about trees directly. They're about what happens in and around the forest."
"The Grove is the place. These are the things you find there."
The name should feel inevitable —like it was always there, waiting to be discovered.
The problem: We need a name for support tickets.
First attempts (rejected):
The walk:
I'm in the grove. Something's wrong with my tree. I need help. Waystone gives me self-service guides. Clearing shows me status. But I need to actually talk to someone.
What do I do?
I walk to... a cabin. There's a porch. Someone's there. I sit down. We talk about what's going on.
The realization: Support isn't a ticket system. It's a porch conversation.
The name: Porch
A porch on a cabin in the woods. You come up the steps. You sit down. The grove keeper comes out. You talk.
"Have a seat on the porch. We'll figure it out together."
When the grove-ui-design skill encounters something that needs naming:
This keeps the naming intentional rather than rushed.
After finding the right name, you'll need to write its description. Invoke the grove-documentation skill when:
docs/grove-naming.mdThe naming document entries should follow Grove's voice: warm, direct, avoiding AI patterns. The grove-documentation skill has the full guidelines.
Keep your scratchpad files. They're documentation of how we think about Grove:
docs/scratch/
grove-journey.md ← The original Porch discovery
{feature}-naming.md ← Future naming journeys
These become part of Grove's story.
Weekly Installs
50
Repository
GitHub Stars
2
First Seen
Feb 5, 2026
Security Audits
Gen Agent Trust HubPassSocketPassSnykPass
Installed on
opencode50
gemini-cli50
codex50
codebuddy49
github-copilot49
amp49
任务估算指南:敏捷开发故事点、计划扑克、T恤尺码法详解
10,500 周安装
NUnit 单元测试最佳实践指南:C# 数据驱动测试与断言方法详解
7,800 周安装
MSTest 单元测试最佳实践指南:C# 现代测试框架使用教程
7,800 周安装
C# MCP服务器生成器 - 快速构建Model Context Protocol服务器 | .NET 8开发工具
7,800 周安装
技术调研文档创建指南:结构化模板与最佳实践
7,900 周安装
GitHub Issues自动创建工具:为未实现的规范要求生成Issue | GitHub Copilot扩展
7,900 周安装
GitHub Copilot 使用指标查询工具 - 获取组织与企业级AI编程助手统计数据
7,800 周安装