Skip to content

feat: Add global Amplifier access system #7

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
wants to merge 5 commits into
base: main
Choose a base branch
from
Open

feat: Add global Amplifier access system #7

wants to merge 5 commits into from
+390 −18

Conversation

@michaeljabbour
Copy link

🌍 Global Amplifier Access

This PR introduces a comprehensive system for using Amplifier's specialized agents and tools on any project, anywhere on your system - not just within the Amplifier directory.

What's New

Global Command Installation

  • New make install-global target that installs amplifier command globally
  • Works from any directory on your system
  • Automatic detection of Amplifier installation location

Universal Script System

  • amplifier-anywhere.sh - Core script for running Amplifier on any project
  • bin/amplifier - Global wrapper that finds your Amplifier installation
  • Robust argument parsing and error handling
  • Preserves original working directory when invoked globally

Enhanced User Experience

  • Clear usage instructions and help text
  • Template messages for proper project isolation
  • Fallback logic for finding Amplifier installation

Usage Examples

# After make install-global
cd ~/my-web-app
amplifier  # Starts Claude with all Amplifier agents for this project

amplifier ~/dev/my-python-api  # Work on specific project
amplifier ~/my-project --model sonnet  # Pass Claude options

Key Benefits

✅ All 20+ specialized agents work on external projects
✅ Shared knowledge base - insights from one project help others
✅ Same powerful automation - quality checks, parallel development
✅ Project isolation - changes only affect your target project
✅ Works anywhere - no need to copy files or modify your projects

Files Changed

  • README.md - Comprehensive documentation for global usage
  • Makefile - New install-global target
  • amplifier-anywhere.sh - Universal access script
  • bin/amplifier - Global command wrapper
  • .gitignore - Allow bin/ directory for global command
  • Additional helper scripts

Installation Locations

The global amplifier command automatically searches for Amplifier in:

  • ~/dev/amplifier (most common)
  • ~/amplifier
  • ~/repos/amplifier
  • ~/code/amplifier
  • /opt/amplifier

Template Usage

Users should start Claude sessions with:

I'm working in [PROJECT_PATH] which doesn't have Amplifier files.
Please cd to that directory and work there.
Do NOT update any issues or PRs in the Amplifier repo.

Use [AGENT_NAME] to [TASK_DESCRIPTION].

Commits in this PR

  1. feat: Add global Amplifier access system - Core implementation of universal access
  2. fix: Improve argument parsing in amplifier-anywhere.sh - Better handling of Claude options and directory paths
  3. fix: Allow bin/ directory in git for global command - Updated .gitignore to include the global command wrapper
  4. fix: Preserve original working directory in global amplifier command - Critical bug fix for proper directory detection

This feature significantly expands Amplifier's utility by making it available system-wide while maintaining proper project isolation.

@michaeljabbour
feat: Add global Amplifier access system
ca1cf68 
🌍 Enable Amplifier's powerful AI agents and tools on any codebase, anywhere

This major enhancement allows developers to harness Amplifier's 20+ specialized
agents (zen-architect, bug-hunter, security-guardian, etc.) on any project
without copying files or modifying existing repositories.

✨ New Features:
- Global 'amplifier' command for system-wide access
- Smart auto-detection of Amplifier installation location
- Enhanced startup scripts with comprehensive error handling
- Seamless integration with existing Claude workflows
- Cross-platform compatibility (macOS, Linux, WSL)

🚀 Usage:
  make install-global    # Install global command
  amplifier ~/my-project # Use Amplifier on any project
  amplifier --help       # Show usage examples

📈 Benefits:
- All 20+ specialized agents available on any codebase
- Shared knowledge base across all projects
- Same powerful automation and quality tools
- Project isolation - changes only affect target project
- No need to modify or copy files to existing projects

🔧 Implementation:
- Enhanced amplifier-anywhere.sh with robust error handling
- New bin/amplifier wrapper for global installation
- Updated Makefile with install-global targets
- Comprehensive documentation in README
- Fixed Claude settings path resolution

This democratizes access to Amplifier's AI development superpowers,
making every codebase instantly compatible with the full Amplifier toolkit.
@michaeljabbour
fix: Improve argument parsing in amplifier-anywhere.sh
2124f5b 
- Fix handling of Claude flags when no directory specified
- Ensure --version flag works correctly without triggering full startup
- Improve argument parsing logic to handle edge cases
- Maintain backward compatibility with all usage patterns

Tested scenarios:
✅ amplifier --version (shows version only)
✅ amplifier --print 'command' (uses current dir + Claude args)
✅ amplifier /path/to/project --model sonnet (explicit dir + args)
✅ amplifier /nonexistent/path (proper error handling)
✅ amplifier --help (shows help text)
@michaeljabbour
fix: Allow bin/ directory in git for global command
3090225 
- Modify .gitignore to permit bin/amplifier global command
- Maintain exclusion of other build artifacts
- Enable proper version control of global installation script
@michaeljabbour
fix: Preserve original working directory in global amplifier command
bf03e27 
- Modified bin/amplifier to capture and pass the original PWD
- Updated amplifier-anywhere.sh to use ORIGINAL_PWD when available
- Fixes issue where 'amplifier' from any directory would default to amplifier repo instead of current dir
@michaeljabbour
Copy link
Author

@microsoft-github-policy-service agree [company="Microsoft"]

@michaeljabbour
Copy link
Author

@microsoft-github-policy-service agree

1 similar comment
@michaeljabbour
Copy link
Author

@microsoft-github-policy-service agree

michaeljabbour added a commit to michaeljabbour/amplifier that referenced this pull request Sep 30, 2025
@michaeljabbour @claude
feat: complete all 44 AI-first principles specifications
8ead3a7 
Complete comprehensive technical specification library with all 44 principles:

**People (6 specs)**
- #1 Small AI-first working groups
- #2 Strategic human touchpoints only
- #3 Prompt engineering as core skill
- microsoft#4 Test-based verification over code review
- microsoft#5 Conversation-driven development
- microsoft#6 Human escape hatches always available

**Process (13 specs)**
- microsoft#7 Regenerate, don't edit
- microsoft#8 Contract-first everything
- microsoft#9 Tests as the quality gate
- microsoft#10 Git as safety net
- microsoft#11 Continuous validation with fast feedback
- microsoft#12 Incremental processing as default
- microsoft#13 Parallel exploration by default
- microsoft#14 Context management as discipline
- microsoft#15 Git-based everything
- microsoft#16 Docs define, not describe
- microsoft#17 Prompt versioning and testing
- microsoft#18 Contract evolution with migration paths
- microsoft#19 Cost and token budgeting

**Technology (18 specs)**
- microsoft#20 Self-modifying AI-first codebase
- microsoft#21 Limited and domain-specific by design
- microsoft#22 Layered virtualization
- microsoft#23 Protected self-healing kernel
- microsoft#24 Long-running agent processes
- microsoft#25 Simple interfaces by design
- microsoft#26 Stateless by default
- microsoft#27 Disposable components everywhere
- microsoft#28 CLI-first design
- microsoft#29 Tool ecosystems as extensions
- microsoft#30 Observability baked in
- microsoft#31 Idempotency by design (reference)
- microsoft#32 Error recovery patterns built in
- microsoft#33 Graceful degradation by design
- microsoft#34 Feature flags as deployment strategy
- microsoft#35 Least-privilege automation
- microsoft#36 Dependency pinning and security scanning
- microsoft#37 Declarative over imperative

**Governance (7 specs)**
- microsoft#38 Access control and compliance
- microsoft#39 Metrics and evaluation everywhere
- microsoft#40 Knowledge stewardship and institutional memory
- microsoft#41 Adaptive sandboxing with explicit approvals
- microsoft#42 Data governance and privacy controls
- microsoft#43 Model lifecycle management
- microsoft#44 Self-serve recovery with known-good snapshots

Each specification includes:
- Plain-language definition
- AI-first development rationale
- 4-6 implementation approaches
- 5 good/bad example pairs with working code
- 6 related principles with relationships
- 7 common pitfalls with examples
- Tools organized by category
- 12 actionable checklist items

Statistics:
- 44 specifications totaling ~10,000+ lines
- 220+ good/bad code example pairs
- 240+ implementation approaches
- 300+ documented anti-patterns
- 500+ tools and frameworks
- 250+ cross-principle relationships

Created through parallel AI agent execution demonstrating
Principle microsoft#13 (Parallel Exploration by Default).

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <[email protected]>
synx-kawai pushed a commit to synx-kawai/amplifier that referenced this pull request Oct 21, 2025
Merge PR microsoft#44 - AI-First Principles and PR microsoft#7 - Glob…
5c62f4a 
…al Amplifier access
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@michaeljabbour