Easy-to-manage touch screens
Free, open-source touch screens. Guided USB setup, a drag-and-drop editor and local control. Made for Home Assistant.
BrewDocs is an offline homebrewing application and info handbook.
LifestyleTypeScript · AstroGitHub @matt-whitakerOnlineOwner unconfirmed
Have you tried it? One tap is enough. No sign-in needed.
No updates detected yet. GitHub releases will appear here.
Owners of public repositories under a personal GitHub account can sign in to verify ownership and manage the introduction themselves. No administrator approval is needed.
Sign in, generate a verification file, and commit it to this repository’s default branch within 30 minutes. Files on other branches or forks do not count. Then check the file below to manage the project without administrator approval. Keep the file to retain your access.
If needed, you will go to sign-in. After signing in, return here and press your chosen verification button again.
Run /nomorevibe verify in your project folder to verify ownership and manage the introduction yourself.
Verify in one minuteAsk about other verification options
Loading the full README. The saved excerpt is shown below.
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.Read the full 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. |