尚未偵測到更新。GitHub 發布版本後會顯示在這裡。
個人 GitHub 帳號下公開儲存庫的擁有者可以登入並驗證所有權,自行管理介紹,無需管理員核准。
登入並產生驗證檔案,在 30 分鐘內將其提交至此儲存庫的預設分支。其他分支或分叉儲存庫中的檔案無效。然後在下方檢查檔案,即可無需管理員核准直接管理專案。請保留檔案以維持管理權限。
如需登入,將前往登入頁面。登入後請回到此處,再次點擊所選的驗證按鈕。
在專案資料夾中執行 /nomorevibe verify,即可驗證所有權並自行管理介紹。
一分鐘完成驗證正在載入完整 README。 以下為已儲存的摘錄。
BrewDocs is a homebrewing application and info handbook for planning and recording brew days.
Design System & Component Library (design.brewdocs.beer)
• Storybook
• Tailwind CSS
• Daisy UI
A GitHub + Claude Code workforce drives a majority of the work, with human oversight supported by frequent check-in phases for course correction and review. I've been having great success with it so far.檢視完整 README ↗BrewDocs is a homebrewing application and info handbook for planning and recording brew days.
| Package | Role |
|---|---|
app | App |
core | Shared types, helpers, and config |
design | Design System + Component Library |
e2e | E2E test suite |
kb | Knowledge base |
www | Marketing Site |
A GitHub + Claude Code workforce drives a majority of the work, with human oversight supported by frequent check-in phases for course correction and review. I've been having great success with it so far.
The engine lives in matt-whitaker/claude-team. This repo holds only the consumer side: a stub workflow pinning a version of it (v4.3 today), and the role overlays in .claude-team/prompts/. Prompts, hooks and the job graph are fetched from that repo at the pinned version when a run starts.
Applying the @claude label to an issue is the front door; a script reads the issue and picks which of the eight roles takes it.
| Where | What |
|---|---|
CLAUDE.md | Repo-wide guidance. Each package carries its own, loaded on demand. |
.claude/rules/ | Modules installed by claude-team: how a session conducts itself, and how the backlog works. Replaced wholesale on upgrade, never edited here. |
.claude/skills/ | Named procedures a session can invoke — filing a finding, diagnosing a run, driving a story. |