dotbrain 0.6.0__tar.gz → 0.7.0__tar.gz

{dotbrain-0.6.0 → dotbrain-0.7.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: dotbrain
-Version: 0.6.0
+Version: 0.7.0
 Summary: Wires project Brainspaces and skills into coding agents.
 Project-URL: Homepage, https://github.com/arminzou/dotbrain
 Project-URL: Repository, https://github.com/arminzou/dotbrain
@@ -31,6 +31,8 @@ Description-Content-Type: text/markdown
 
 # Dotbrain
 
+English | [简体中文](README.zh-CN.md)
+
 [![PyPI](https://img.shields.io/pypi/v/dotbrain?style=flat&logo=pypi)](https://pypi.org/project/dotbrain/)
 [![CI](https://img.shields.io/github/actions/workflow/status/arminzou/dotbrain/ci.yml?branch=main&style=flat&logo=github&label=CI)](https://github.com/arminzou/dotbrain/actions/workflows/ci.yml)
 [![Python](https://img.shields.io/pypi/pyversions/dotbrain?style=flat&logo=python)](https://pypi.org/project/dotbrain/)
@@ -39,8 +41,14 @@ Description-Content-Type: text/markdown
 
 **Private project context for Claude Code and Codex.**
 
-Give each coding agent your project's decisions, vocabulary, and issues. Keep that context
-versioned and outside your code repo.
+Dotbrain brings the Dotfiles convention to your project work. Keep your working notes, plans,
+instructions, and selected agent resources in a private home, then wire them into the checkouts
+where you work.
+
+Your context stays in local files with its own Git history. The CLI connects your workspace to
+the code repo; the plugin's workflow skills guide how your agent uses and maintains it with you.
+
+[https://github.com/user-attachments/assets/540e8945-b8bc-4fc1-ac05-c125bf768fa9](https://github.com/user-attachments/assets/021fc13a-db20-4549-8aab-b5240d289bde)
 
 [Documentation](https://arminzou.github.io/dotbrain/) ·
 [Getting started](https://arminzou.github.io/dotbrain/getting-started) ·
@@ -48,20 +56,27 @@ versioned and outside your code repo.
 
 ### Why I built it
 
-I built Dotbrain because my projects often start privately and get shared later. The code can be
-shared; the half-formed decisions, roadmap, and rationale need their own home. Mine scattered
-across Obsidian, gitignored notes, and agent memory. Every new session meant hunting for context
-and explaining the project again. I wanted that thinking versioned, available to both agents,
-and connected to the work.
+Global agent instructions describe how I want my agent to behave at user level. Shared repository instructions
+describe how anyone should work on the code. My own reasoning, working notes, and plans for a
+particular project need a private home.
+
+Mine were scattered across Obsidian, gitignored notes, and agent memory. Finding that context and
+bringing it into another session took effort. So did making my selected skills and subagents
+available in a new checkout. I built Dotbrain to keep that project workspace together and make
+connecting it to where I work repeatable.
+
+Read the story behind Dotbrain: [Dotfiles for Your Repo](https://x.com/i/article/2109385521214390273).
 
 ## Is this for you?
 
-Use Dotbrain if you work across agents, sessions, or worktrees and have project context worth
-preserving. It gives that context a home you can review and version with Git, separate from the
-code you share.
+Use Dotbrain when you need a private project workspace you want to keep developing across
+agents, sessions, or worktrees: context you've built up, plans in progress, and your own
+instructions and selected skills for the work.
+
+It works alongside your agent's memory system and other context tools. The workspace is yours;
+you decide which outcomes belong in shared repository docs or public proposals.
 
 If a few standing instructions in `AGENTS.md` or `CLAUDE.md` cover your needs, keep it simple.
-Dotbrain is a local tool, not a hosted team knowledge base.
 
 ## Get started
 
@@ -99,27 +114,55 @@ the repo to its private Brainspace. Check the result with:
 dotbrain doctor
 ```
 
-Start a fresh agent session in the wired repo to load its Brain context.
+Start a fresh agent session in the wired repo to load the Dotbrain convention. It tells the
+agent where to find your project context and how to work with it.
 See [Getting started](https://arminzou.github.io/dotbrain/getting-started) for manual installation,
 backups, a second machine, and troubleshooting.
 
+### Update
+
+Update the plugin and the CLI together. In Claude Code, run `/plugin`, update dotbrain from the
+menu, then `/reload-plugins`. In Codex:
+
+```bash
+codex plugin marketplace upgrade
+codex plugin add dotbrain@dotbrain
+```
+
+Then upgrade the CLI and reconcile your machine and projects:
+
+```bash
+uv tool install dotbrain@latest
+dotbrain bootstrap
+dotbrain refresh --all
+```
+
+Installed the CLI with pipx or pip? Upgrade with that tool instead. See
+[Staying current](https://arminzou.github.io/dotbrain/getting-started#staying-current).
+
 ## How it works
 
 Each project has a **Brainspace** under your private dotbrain home, by default `~/dotbrain/`.
-It holds the **Brain** (vocabulary, decisions, and designs) and an **execution store**
-(issues tracked with [Beads](https://github.com/gastownhall/beads)). Gitignored symlinks connect
-the code repo to that Brainspace; the private files are stored outside the code repo.
+It holds the **Brain** (`.brain/`: local Markdown files for project rules, vocabulary, decisions,
+and designs) and an **execution store** (`.beads/`: issues tracked with
+[Beads](https://github.com/gastownhall/beads)). Gitignored symlinks make both available through
+the checkout while their files and history stay outside the code repo.
 
 <picture>
-  <source media="(prefers-color-scheme: dark)" srcset="docs/public/assets/how-it-works-dark.svg">
-  <source media="(prefers-color-scheme: light)" srcset="docs/public/assets/how-it-works-light.svg">
-  <img src="docs/public/assets/how-it-works-light.svg" alt="Claude Code and Codex work in the code repo. Gitignored links connect it to a separate private Brainspace holding the Brain and Beads." width="1000">
+  <source media="(prefers-color-scheme: dark)" srcset="docs/public/assets/how-it-works-dark.png">
+  <source media="(prefers-color-scheme: light)" srcset="docs/public/assets/how-it-works-light.png">
+  <img src="docs/public/assets/how-it-works-light.png" alt="Claude Code and Codex work in the code repo. Gitignored links connect it to a separate private Brainspace holding the Brain and Beads." width="1000">
 </picture>
 
-The plugin's session-start hook loads project context. Its skills guide work when invoked,
-and wiring delivers selected skills and subagents into the repo's agent workspaces. Skills and
-Claude agents use symlinks; Codex agents use generated, Git-ignored TOML files.
-`dotbrain wire` connects worktrees to the same Brainspace through Git metadata.
+Wiring also delivers selected skills and subagents into the repo's agent workspaces, `.claude/`
+and `.codex/`. Skills and Claude agents use symlinks; Codex agents use generated, Git-ignored
+TOML files. Wiring a Git worktree connects it to the main checkout's existing Brainspace, so
+both use the same knowledge and tracker.
+
+At session start, the plugin hook supplies `DOTBRAIN.md`, the shared convention. The agent then
+reads the project's private rules and retrieves the context the task needs. Workflow skills
+guide how it consults that context and records what you work out together.
+See [Session context](https://arminzou.github.io/dotbrain/session-context) for the loading sequence.
 
 Use `dotbrain projects list` to discover registered projects. Inside a wired checkout,
 `dotbrain refresh` maintains that checkout and `dotbrain unwire` detaches it while retaining the
@@ -138,8 +181,11 @@ See [Architecture](https://arminzou.github.io/dotbrain/architecture),
 Every piece of work should leave the next session better informed. Dotbrain's bundled skills
 carry work from idea to implementation, then return what you learned to the project's context.
 
-**Start from the Brain → explore unknowns → settle decisions → write a design → work and
-verify issues → review → return lasting decisions to the Brain.**
+<picture>
+  <source media="(prefers-color-scheme: dark)" srcset="docs/public/assets/workflow-dark.png">
+  <source media="(prefers-color-scheme: light)" srcset="docs/public/assets/workflow-light.png">
+  <img src="docs/public/assets/workflow-light.png" alt="Workflow skills guide work through decisions, design, issues, execution, review, and closure. Discoveries update the active design; lasting decisions return to the Brain for the next initiative." width="880">
+</picture>
 
 The loop closes in two places:
 
@@ -150,8 +196,8 @@ The loop closes in two places:
   vocabulary in the Brain. The next initiative starts with that knowledge already available.
 
 The Brain holds durable knowledge, the design holds current intent, and Beads holds execution
-state. Each handoff lives in a document or tracker entry, so another session or agent can pick
-up the work without reconstructing it from chat history.
+state. Each handoff lives in a document or tracker entry that another session or agent can
+consult to continue the work.
 
 You own the success criteria and the final review decision. Use the full loop when work spans
 sessions or carries open questions; small changes can use just the steps they need.

{dotbrain-0.6.0 → dotbrain-0.7.0}/README.md

@@ -8,6 +8,8 @@
 
 # Dotbrain
 
+English | [简体中文](README.zh-CN.md)
+
 [![PyPI](https://img.shields.io/pypi/v/dotbrain?style=flat&logo=pypi)](https://pypi.org/project/dotbrain/)
 [![CI](https://img.shields.io/github/actions/workflow/status/arminzou/dotbrain/ci.yml?branch=main&style=flat&logo=github&label=CI)](https://github.com/arminzou/dotbrain/actions/workflows/ci.yml)
 [![Python](https://img.shields.io/pypi/pyversions/dotbrain?style=flat&logo=python)](https://pypi.org/project/dotbrain/)
@@ -16,8 +18,14 @@
 
 **Private project context for Claude Code and Codex.**
 
-Give each coding agent your project's decisions, vocabulary, and issues. Keep that context
-versioned and outside your code repo.
+Dotbrain brings the Dotfiles convention to your project work. Keep your working notes, plans,
+instructions, and selected agent resources in a private home, then wire them into the checkouts
+where you work.
+
+Your context stays in local files with its own Git history. The CLI connects your workspace to
+the code repo; the plugin's workflow skills guide how your agent uses and maintains it with you.
+
+[https://github.com/user-attachments/assets/540e8945-b8bc-4fc1-ac05-c125bf768fa9](https://github.com/user-attachments/assets/021fc13a-db20-4549-8aab-b5240d289bde)
 
 [Documentation](https://arminzou.github.io/dotbrain/) ·
 [Getting started](https://arminzou.github.io/dotbrain/getting-started) ·
@@ -25,20 +33,27 @@ versioned and outside your code repo.
 
 ### Why I built it
 
-I built Dotbrain because my projects often start privately and get shared later. The code can be
-shared; the half-formed decisions, roadmap, and rationale need their own home. Mine scattered
-across Obsidian, gitignored notes, and agent memory. Every new session meant hunting for context
-and explaining the project again. I wanted that thinking versioned, available to both agents,
-and connected to the work.
+Global agent instructions describe how I want my agent to behave at user level. Shared repository instructions
+describe how anyone should work on the code. My own reasoning, working notes, and plans for a
+particular project need a private home.
+
+Mine were scattered across Obsidian, gitignored notes, and agent memory. Finding that context and
+bringing it into another session took effort. So did making my selected skills and subagents
+available in a new checkout. I built Dotbrain to keep that project workspace together and make
+connecting it to where I work repeatable.
+
+Read the story behind Dotbrain: [Dotfiles for Your Repo](https://x.com/i/article/2109385521214390273).
 
 ## Is this for you?
 
-Use Dotbrain if you work across agents, sessions, or worktrees and have project context worth
-preserving. It gives that context a home you can review and version with Git, separate from the
-code you share.
+Use Dotbrain when you need a private project workspace you want to keep developing across
+agents, sessions, or worktrees: context you've built up, plans in progress, and your own
+instructions and selected skills for the work.
+
+It works alongside your agent's memory system and other context tools. The workspace is yours;
+you decide which outcomes belong in shared repository docs or public proposals.
 
 If a few standing instructions in `AGENTS.md` or `CLAUDE.md` cover your needs, keep it simple.
-Dotbrain is a local tool, not a hosted team knowledge base.
 
 ## Get started
 
@@ -76,27 +91,55 @@ the repo to its private Brainspace. Check the result with:
 dotbrain doctor
 ```
 
-Start a fresh agent session in the wired repo to load its Brain context.
+Start a fresh agent session in the wired repo to load the Dotbrain convention. It tells the
+agent where to find your project context and how to work with it.
 See [Getting started](https://arminzou.github.io/dotbrain/getting-started) for manual installation,
 backups, a second machine, and troubleshooting.
 
+### Update
+
+Update the plugin and the CLI together. In Claude Code, run `/plugin`, update dotbrain from the
+menu, then `/reload-plugins`. In Codex:
+
+```bash
+codex plugin marketplace upgrade
+codex plugin add dotbrain@dotbrain
+```
+
+Then upgrade the CLI and reconcile your machine and projects:
+
+```bash
+uv tool install dotbrain@latest
+dotbrain bootstrap
+dotbrain refresh --all
+```
+
+Installed the CLI with pipx or pip? Upgrade with that tool instead. See
+[Staying current](https://arminzou.github.io/dotbrain/getting-started#staying-current).
+
 ## How it works
 
 Each project has a **Brainspace** under your private dotbrain home, by default `~/dotbrain/`.
-It holds the **Brain** (vocabulary, decisions, and designs) and an **execution store**
-(issues tracked with [Beads](https://github.com/gastownhall/beads)). Gitignored symlinks connect
-the code repo to that Brainspace; the private files are stored outside the code repo.
+It holds the **Brain** (`.brain/`: local Markdown files for project rules, vocabulary, decisions,
+and designs) and an **execution store** (`.beads/`: issues tracked with
+[Beads](https://github.com/gastownhall/beads)). Gitignored symlinks make both available through
+the checkout while their files and history stay outside the code repo.
 
 <picture>
-  <source media="(prefers-color-scheme: dark)" srcset="docs/public/assets/how-it-works-dark.svg">
-  <source media="(prefers-color-scheme: light)" srcset="docs/public/assets/how-it-works-light.svg">
-  <img src="docs/public/assets/how-it-works-light.svg" alt="Claude Code and Codex work in the code repo. Gitignored links connect it to a separate private Brainspace holding the Brain and Beads." width="1000">
+  <source media="(prefers-color-scheme: dark)" srcset="docs/public/assets/how-it-works-dark.png">
+  <source media="(prefers-color-scheme: light)" srcset="docs/public/assets/how-it-works-light.png">
+  <img src="docs/public/assets/how-it-works-light.png" alt="Claude Code and Codex work in the code repo. Gitignored links connect it to a separate private Brainspace holding the Brain and Beads." width="1000">
 </picture>
 
-The plugin's session-start hook loads project context. Its skills guide work when invoked,
-and wiring delivers selected skills and subagents into the repo's agent workspaces. Skills and
-Claude agents use symlinks; Codex agents use generated, Git-ignored TOML files.
-`dotbrain wire` connects worktrees to the same Brainspace through Git metadata.
+Wiring also delivers selected skills and subagents into the repo's agent workspaces, `.claude/`
+and `.codex/`. Skills and Claude agents use symlinks; Codex agents use generated, Git-ignored
+TOML files. Wiring a Git worktree connects it to the main checkout's existing Brainspace, so
+both use the same knowledge and tracker.
+
+At session start, the plugin hook supplies `DOTBRAIN.md`, the shared convention. The agent then
+reads the project's private rules and retrieves the context the task needs. Workflow skills
+guide how it consults that context and records what you work out together.
+See [Session context](https://arminzou.github.io/dotbrain/session-context) for the loading sequence.
 
 Use `dotbrain projects list` to discover registered projects. Inside a wired checkout,
 `dotbrain refresh` maintains that checkout and `dotbrain unwire` detaches it while retaining the
@@ -115,8 +158,11 @@ See [Architecture](https://arminzou.github.io/dotbrain/architecture),
 Every piece of work should leave the next session better informed. Dotbrain's bundled skills
 carry work from idea to implementation, then return what you learned to the project's context.
 
-**Start from the Brain → explore unknowns → settle decisions → write a design → work and
-verify issues → review → return lasting decisions to the Brain.**
+<picture>
+  <source media="(prefers-color-scheme: dark)" srcset="docs/public/assets/workflow-dark.png">
+  <source media="(prefers-color-scheme: light)" srcset="docs/public/assets/workflow-light.png">
+  <img src="docs/public/assets/workflow-light.png" alt="Workflow skills guide work through decisions, design, issues, execution, review, and closure. Discoveries update the active design; lasting decisions return to the Brain for the next initiative." width="880">
+</picture>
 
 The loop closes in two places:
 
@@ -127,8 +173,8 @@ The loop closes in two places:
   vocabulary in the Brain. The next initiative starts with that knowledge already available.
 
 The Brain holds durable knowledge, the design holds current intent, and Beads holds execution
-state. Each handoff lives in a document or tracker entry, so another session or agent can pick
-up the work without reconstructing it from chat history.
+state. Each handoff lives in a document or tracker entry that another session or agent can
+consult to continue the work.
 
 You own the success criteria and the final review decision. Use the full loop when work spans
 sessions or carries open questions; small changes can use just the steps they need.

dotbrain-0.7.0/docs/.vitepress/config.mts

@@ -0,0 +1,179 @@
+import { defineConfig } from 'vitepress'
+
+export default defineConfig({
+  title: 'Dotbrain',
+  description: 'Private project context for coding agents, kept out of your code repo.',
+  base: '/',
+  cleanUrls: true,
+  lastUpdated: true,
+  // README.md is the index for browsing docs/ on GitHub, and AGENTS.md/CLAUDE.md guide agents
+  // editing docs/; index.md is the site's home.
+  srcExclude: ['README.md', 'AGENTS.md', 'CLAUDE.md'],
+  head: [
+    ['link', { rel: 'icon', type: 'image/png', sizes: '32x32', href: '/assets/favicon-light-32.png' }],
+    ['link', { rel: 'icon', type: 'image/png', sizes: '32x32', href: '/assets/favicon-light-32.png', media: '(prefers-color-scheme: light)' }],
+    ['link', { rel: 'icon', type: 'image/png', sizes: '32x32', href: '/assets/favicon-dark-32.png', media: '(prefers-color-scheme: dark)' }],
+    ['link', { rel: 'apple-touch-icon', sizes: '180x180', href: '/assets/apple-touch-icon-light.png' }],
+    ['meta', { property: 'og:site_name', content: 'Dotbrain' }],
+    ['meta', { property: 'og:type', content: 'website' }],
+    ['meta', { property: 'og:image', content: 'https://dotbrain.net/assets/banner-dark.png' }],
+    ['meta', { property: 'og:image:width', content: '1672' }],
+    ['meta', { property: 'og:image:height', content: '941' }],
+    ['meta', { property: 'og:image:alt', content: 'Dotbrain connected brain mark and wordmark' }],
+    ['meta', { name: 'twitter:card', content: 'summary_large_image' }],
+    ['meta', { name: 'twitter:image', content: 'https://dotbrain.net/assets/banner-dark.png' }],
+    ['meta', { name: 'twitter:image:alt', content: 'Dotbrain connected brain mark and wordmark' }],
+  ],
+  // English stays at the root so existing URLs keep working; zh/ mirrors its file names.
+  locales: {
+    root: { label: 'English', lang: 'en-US' },
+    zh: {
+      label: '简体中文',
+      lang: 'zh-CN',
+      link: '/zh/',
+      description: '为 Coding Agent 提供私有的项目上下文，不放进公开代码仓库。',
+      themeConfig: {
+        nav: [
+          { text: '指南', link: '/zh/getting-started', activeMatch: '^/zh/(why-dotbrain|getting-started|prompts|agent-team|architecture|workflow|learning|wiring|session-context|beads-backend|brain-site|troubleshooting)' },
+          { text: '参考', link: '/zh/cli-reference', activeMatch: '^/zh/(cli-reference|configuration|skills|glossary)' },
+          { text: 'PyPI', link: 'https://pypi.org/project/dotbrain/' },
+        ],
+        sidebar: [
+          {
+            text: '指南',
+            items: [
+              { text: '为什么用 Dotbrain？', link: '/zh/why-dotbrain' },
+              { text: '快速开始', link: '/zh/getting-started' },
+              { text: '示例提示词', link: '/zh/prompts' },
+            ],
+          },
+          {
+            text: '使用场景',
+            items: [
+              { text: '开发项目', link: '/zh/workflow' },
+              { text: '和 Agent 团队一起工作', link: '/zh/agent-team' },
+              { text: '学习项目', link: '/zh/learning' },
+              { text: '浏览 Brain', link: '/zh/brain-site' },
+            ],
+          },
+          {
+            text: '工作原理',
+            items: [
+              { text: '架构', link: '/zh/architecture' },
+              { text: '项目连接', link: '/zh/wiring' },
+              { text: '会话上下文', link: '/zh/session-context' },
+              { text: 'Beads 后端', link: '/zh/beads-backend' },
+            ],
+          },
+          {
+            text: '帮助',
+            items: [{ text: '故障排查与常见问题', link: '/zh/troubleshooting' }],
+          },
+          {
+            text: '参考',
+            items: [
+              { text: 'CLI 参考', link: '/zh/cli-reference' },
+              { text: '配置', link: '/zh/configuration' },
+              { text: 'Brain 站点配置', link: '/zh/brain-site-configuration' },
+              { text: '技能', link: '/zh/skills' },
+              { text: '术语表', link: '/zh/glossary' },
+            ],
+          },
+        ],
+        outline: { level: [2, 3], label: '本页目录' },
+        editLink: {
+          pattern: 'https://github.com/arminzou/dotbrain/edit/main/docs/:path',
+          text: '在 GitHub 上编辑此页',
+        },
+        docFooter: { prev: '上一页', next: '下一页' },
+        lastUpdated: { text: '最后更新' },
+        langMenuLabel: '切换语言',
+        returnToTopLabel: '回到顶部',
+        sidebarMenuLabel: '菜单',
+        darkModeSwitchLabel: '外观',
+        lightModeSwitchTitle: '切换到浅色模式',
+        darkModeSwitchTitle: '切换到深色模式',
+        footer: { message: '基于 MIT 许可证发布。' },
+      },
+    },
+  },
+  transformHead: ({ title, description }) => [
+    ['meta', { property: 'og:title', content: title }],
+    ['meta', { property: 'og:description', content: description }],
+  ],
+
+  markdown: {
+    theme: { light: 'github-light', dark: 'github-dark' },
+    // A ```mermaid fence becomes the theme's <Mermaid> component, which draws it in the browser.
+    config(md) {
+      const fence = md.renderer.rules.fence!
+      md.renderer.rules.fence = (tokens, index, ...rest) =>
+        tokens[index].info.trim() === 'mermaid'
+          ? `<Mermaid code="${encodeURIComponent(tokens[index].content)}" />`
+          : fence(tokens, index, ...rest)
+    },
+  },
+
+  themeConfig: {
+    logo: {
+      light: { src: '/assets/mark-light.png', width: 24, height: 24 },
+      dark: { src: '/assets/mark-dark.png', width: 24, height: 24 },
+      alt: 'Dotbrain',
+    },
+    nav: [
+      { text: 'Guide', link: '/getting-started', activeMatch: '^/(why-dotbrain|getting-started|prompts|agent-team|architecture|workflow|learning|wiring|session-context|beads-backend|brain-site|troubleshooting)' },
+      { text: 'Reference', link: '/cli-reference', activeMatch: '^/(cli-reference|configuration|skills|glossary)' },
+      { text: 'PyPI', link: 'https://pypi.org/project/dotbrain/' },
+    ],
+    sidebar: [
+      {
+        text: 'Guide',
+        items: [
+          { text: 'Why Dotbrain?', link: '/why-dotbrain' },
+          { text: 'Getting started', link: '/getting-started' },
+          { text: 'Example prompts', link: '/prompts' },
+        ],
+      },
+      {
+        text: 'Use cases',
+        items: [
+          { text: 'Develop a project', link: '/workflow' },
+          { text: 'Work with an agent team', link: '/agent-team' },
+          { text: 'Learn your project', link: '/learning' },
+          { text: 'Browse the Brain', link: '/brain-site' },
+        ],
+      },
+      {
+        text: 'How it works',
+        items: [
+          { text: 'Architecture', link: '/architecture' },
+          { text: 'Wiring', link: '/wiring' },
+          { text: 'Session context', link: '/session-context' },
+          { text: 'Beads backend', link: '/beads-backend' },
+        ],
+      },
+      {
+        text: 'Help',
+        items: [{ text: 'Troubleshooting & FAQ', link: '/troubleshooting' }],
+      },
+      {
+        text: 'Reference',
+        items: [
+          { text: 'CLI reference', link: '/cli-reference' },
+          { text: 'Configuration', link: '/configuration' },
+          { text: 'Brain site configuration', link: '/brain-site-configuration' },
+          { text: 'Skills', link: '/skills' },
+          { text: 'Glossary', link: '/glossary' },
+        ],
+      },
+    ],
+    outline: { level: [2, 3], label: 'On this page' },
+    search: { provider: 'local' },
+    socialLinks: [{ icon: 'github', link: 'https://github.com/arminzou/dotbrain' }],
+    editLink: {
+      pattern: 'https://github.com/arminzou/dotbrain/edit/main/docs/:path',
+      text: 'Edit this page on GitHub',
+    },
+    footer: { message: 'Released under the MIT License.' },
+  },
+})

{dotbrain-0.6.0 → dotbrain-0.7.0}/docs/.vitepress/theme/style.css

@@ -389,6 +389,12 @@
   width: 100%;
   font-size: 14px;
 }
+.prompt-examples .vp-doc div.language-text code {
+  width: 100%;
+  white-space: pre-wrap;
+  overflow-wrap: anywhere;
+}
+
 .vp-doc td code {
   white-space: nowrap;
 }

{dotbrain-0.6.0 → dotbrain-0.7.0}/docs/AGENTS.md

@@ -16,6 +16,12 @@ npm run build                        # must pass before a push
 - `configuration.md` is tested: `tests/test_configuration_docs.py` loads the first YAML block under
   ``## `config.yaml` `` and ``## `project.yaml` `` through the real config loader. Keep those
   headings exact, keep the fences plain ```` ```yaml ````, and keep every key the test reads.
+- `zh/` holds the Simplified Chinese pages, one per English page with the same file name. They are
+  hand-maintained, best effort: write natural Chinese, keep commands, code, diagrams and terms
+  developers know in English (Agent, Coding Agent, PR, worktree, checkout) as is. When translating a
+  heading that is a link target, keep the English slug with `{#english-slug}`. `zh/cli-reference.md`
+  is a hand translation, not generated. Chinese nav and sidebar live under `locales.zh` in
+  `.vitepress/config.mts`.
 - Name a code block's file in a `# path` comment on its first line. A `[title]` after the language
   only renders inside a `::: code-group`.
 - Use `::: code-group` for alternatives (Claude Code / Codex, macOS / Windows, uv / pipx).

{dotbrain-0.6.0 → dotbrain-0.7.0}/docs/README.md

@@ -7,10 +7,12 @@ fine on GitHub.
 
 - [why-dotbrain.md](why-dotbrain.md) — candid comparisons, trade-offs, and when to skip it.
 - [getting-started.md](getting-started.md) — install, wire a repo, and verify the result.
+- [prompts.md](prompts.md) — example prompts for each common job, and the skill each triggers.
 
 ## Use Cases
 
 - [workflow.md](workflow.md) — develop a project from first idea to closed design, one skill per step.
+- [agent-team.md](agent-team.md) — HITL and handoff, sequential and parallel work, and packaged subagents.
 - [learning.md](learning.md) — learn across sessions, park concepts, and capture demonstrated understanding.
 - [brain-site.md](brain-site.md) — read, search, and navigate the private Brain.