Designr is an automated invention and development system using Rube Goldberg iterative loops to build digital inventions 10x faster. This meta-project creates the infrastructure for zero-intervention software development.
# No dependencies to install - uses Claude Code CLI
# Ensure permissions are configured
cat .claude/settings.local.json# Create new invention
./inventions/scripts/new-invention.sh <invention-name>
# Edit invention specification
vim inventions/active/<invention-name>.md
# Build invention with Rube Goldberg
./inventions/scripts/start-invention.sh <invention-name>
# Create automation workflow
./automation/quick-start.sh <tool-name>
# Run automation with Rube Goldberg
./automation/start-rube-goldberg.sh <tool-name># Test invention creation
./inventions/scripts/new-invention.sh test-invention
# Test Rube Goldberg loop (dry run)
cat .claude/rube-goldberg-loop.local.md
# Verify permissions
grep -A 5 "permissions" .claude/settings.local.json# Check current iteration
grep '^iteration:' .claude/rube-goldberg-loop.local.md
# View Rube Goldberg's current task
tail -50 .claude/rube-goldberg-loop.local.md
# Watch git commits (Rube Goldberg commits progress)
git log --oneline -10
# Cancel Rube Goldberg loop
rm .claude/rube-goldberg-loop.local.md- Use
set -efor error handling - Add descriptions for all prompts
- Make scripts executable:
chmod +x - Use absolute paths where possible
- Clear headings and structure
- Code blocks with language specification
- Examples for all concepts
- Keep concise and actionable
- Invention files:
lowercase-with-dashes.md - Scripts:
kebab-case.sh - Directories:
lowercase(no special characters)
- Specifications (
specs/*.md) - Detailed requirements - Rube Goldberg Control (
.claude/rube-goldberg-loop.local.md) - Loop configuration - TODO List (
fix_plan.md) - Prioritized tasks managed by Rube Goldberg - AGENTS.md - Build/test instructions (this file)
- Auto-accept (
.claude/settings.local.json) - No permission prompts
- One task per iteration
- Search before assuming code doesn't exist
- Use subagents to extend context window
- Test after every change
- Commit when tests pass
- Update fix_plan.md continuously
- Self-improve AGENTS.md with learnings
- Specifications must be detailed and specific
- Each feature needs clear success criteria
- Tests specified in invention spec
- Verification commands for each step
- Scripts must be executable
- All paths must work from project root
- Rube Goldberg loops must complete without errors
- Git commits should happen automatically
Before starting:
- Read
INVENTOR-QUICKSTART.md - Study example:
inventions/active/example-smart-clipboard.md - Understand Rube Goldberg loop:
rube-goldberg-setup-template.md
Workflow:
- Run
./inventions/scripts/new-invention.sh <name> - Edit
inventions/active/<name>.mdwith:- Clear problem statement
- Detailed solution
- Specific build steps (not vague!)
- Verification for each step
- Success criteria
- Run
./inventions/scripts/start-invention.sh <name> - Monitor progress with
tail -f .claude/rube-goldberg-loop.local.md - Review completed prototype
Workflow:
- Get complex setup instructions (e.g., from Claude Desktop)
- Run
./automation/quick-start.sh <tool-name> - Paste instructions into
automation/workflows/<tool-name>-setup.md - Add verification steps
- Run
./automation/start-rube-goldberg.sh <tool-name> - Tool installs automatically
For inventions built by Rube Goldberg:
- Tests must pass
- Build must succeed
- Type checking (if applicable)
- Linting (if applicable)
- All specs requirements met
- DO NOT use vague specifications ("build the thing")
- DO NOT skip verification steps
- DO NOT set max_iterations too low (< 15)
- DO search codebase before assuming code doesn't exist
- DO capture WHY tests are important, not just WHAT they test
- DO resolve unrelated test failures discovered during work
Location: inventions/templates/ and automation/templates/
- Use
invention-template.mdfor new inventions - Use
setup-template.mdfor automation workflows - Follow
example-smart-clipboard.mdpatterns
- Use up to 50 parallel subagents for searches
- Use only 1 subagent for builds/tests (avoid backpressure)
- Subagents extend context window
- Use subagents to update fix_plan.md and AGENTS.md
ideas/ → Quick notes for future inventions
↓
active/ → Currently building (3-10 at a time)
↓
completed/ → Finished and verified prototypes
specs/*.md- Read every loop for requirementsfix_plan.md- Updated every loop with progressAGENTS.md- Updated when learning new commands.claude/rube-goldberg-loop.local.md- Loop control file
- Auto-accept enabled: review sensitive operations
- Git commits are automatic: use .gitignore properly
- Scripts run with user permissions
- No secrets in specifications or code
- Script execution < 5 seconds
- Rube Goldberg iterations: 1-3 minutes each
- Full invention: 15-30 iterations typical
- Complex setups: 20-40 iterations
Fix: Add more specific instruction to rube-goldberg-loop.local.md
9999999. IMPORTANT: [Specific instruction for the stuck issue]Fix: Emphasize in rube-goldberg-loop.local.md:
9999999999. DO NOT IMPLEMENT PLACEHOLDER OR SIMPLE IMPLEMENTATIONS. WE WANT FULL IMPLEMENTATIONS. DO IT OR I WILL YELL AT YOUFix: Add search instruction:
Before making changes search codebase (don't assume not implemented) using subagents. Think hard.Fix: Increase subagent usage in rube-goldberg-loop.local.md:
You may use up to 100 parallel subagents for all operations but only 1 subagent for build/tests.Fix: Either:
git reset --hard <last-good-commit>and restart with better instructions- Create rescue prompt in rube-goldberg-loop.local.md with specific fixes needed
When Rube Goldberg commits (automatic):
- Format: Descriptive message of changes made
- Includes: Changed code + updated fix_plan.md
- Co-authored:
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
Manual commits (when you intervene):
- Format:
[type]: [description] - Types: feat, fix, docs, refactor, chore
- Update fix_plan.md if discovering issues
- Document WHY, not just WHAT
- Include verification commands
- Be specific about success criteria
- Add examples when helpful
- Capture importance of tests in docstrings
- Explain WHY implementation is important
- Leave "notes" for future Rube Goldberg iterations
- Rube Goldberg updates when learning new commands
- Keep sections brief and actionable
- Add to "Common Rube Goldberg Issues" when resolving problems
- Remove outdated information
./inventions/scripts/new-invention.sh my-invention
vim inventions/active/my-invention.md # Be specific!
./inventions/scripts/start-invention.sh my-inventiongrep '^iteration:' .claude/rube-goldberg-loop.local.md
tail -20 .claude/rube-goldberg-loop.local.md
git log --oneline -5rm .claude/rube-goldberg-loop.local.md
# Or edit and set: active: falsegit log --oneline -20 # Find last good commit
git reset --hard <commit-hash>
# Adjust rube-goldberg-loop.local.md with better instructions
# Restart Rube Goldberg- Full setup guide:
RUBE_GOLDBERG-AGENTS-SETUP-GUIDE.md - Inventor quickstart:
INVENTOR-QUICKSTART.md - Rube Goldberg template:
rube-goldberg-setup-template.md - Example invention:
inventions/active/example-smart-clipboard.md - Automation guide:
automation/HOW-TO-USE.md