Download the PHP package mischasigtermans/laravel-altitude without Composer
On this page you can find all versions of the php package mischasigtermans/laravel-altitude. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package laravel-altitude
Altitude
Opinionated Claude Code agents and commands for TALL stack development.
Note: This package is opinionated. It assumes you're building with the TALL stack (Tailwind, Alpine, Livewire, Laravel) and optionally Filament, Flux UI, and Pest. If you use a different stack, this package may not be for you.
Altitude provides specialized AI agents that focus on decision-making and workflow patterns while Laravel Boost handles version-specific documentation via MCP.
Installation
Quick Start
Altitude syncs automatically when Laravel Boost runs boost:install or boost:update.
Recommended: Add to your composer.json scripts for automatic updates:
This keeps agents and documentation in sync whenever you run composer update.
Manual sync: For more control, run directly:
How Syncing Works
On Install
When you install Altitude, agents sync automatically on the next console command if .claude/agents doesn't exist yet. This ensures you get agents immediately without needing to run a separate command.
On Boost Updates
When boost:install or boost:update runs, Altitude syncs with --force, updating all agents to the latest versions.
File Conflicts
Altitude agents use common names like architect, database, and livewire. If you have custom agents with the same names, they will be overwritten on boost updates.
To keep custom agents, use different names:
Alternatively, disable auto-sync and manage updates manually:
Why Altitude?
AI assistants need context about your stack to give good advice. But documentation changes between versions, and copy-pasting docs into prompts wastes tokens and goes stale.
Altitude solves this by:
- Separating concerns — Agents handle decisions and workflow, Boost handles docs
- Package-aware publishing — Only get agents for packages you actually use
- Workflow commands — Common tasks like
/ship,/test,/debugwork out of the box - Never stale — Agents reference
mcp__laravel-boost__search-docsinstead of embedding version-specific code
Agents
Altitude publishes agents based on your installed packages:
Always Included
| Agent | Purpose |
|---|---|
architect |
Multi-file features and architecture decisions |
database |
Schema design, migrations, Eloquent models |
docs |
Documentation lookup via MCP tools |
security |
Security audits and vulnerability checks |
Package-Specific
| Package | Agents |
|---|---|
livewire/livewire |
livewire, alpine |
livewire/flux |
flux |
filament/filament |
filament |
pestphp/pest |
pest |
laravel/reverb |
realtime |
How Agents Work
Each agent defines:
- Responsibilities — What it handles
- Decision guides — Common choices and tradeoffs
- Workflow — Steps to follow
- References — Points to
mcp__laravel-boost__search-docsfor implementation details
Example usage in Claude Code:
Commands
Workflow commands are always published:
| Command | Purpose |
|---|---|
/ship |
Commit, push, and create pull request |
/test |
Run tests related to current changes |
/debug |
Debug using logs and application state |
/review |
Review code for quality and security |
/catchup |
Resume work after a break |
/pint |
Format code with Laravel Pint |
Command Examples
Optional: Enhanced Debugging
Herd Pro
If you're using Laravel Herd Pro, the /debug command can access logs and dumps via MCP:
| Tool | Purpose |
|---|---|
mcp__herd__get-logs |
Application logs |
mcp__herd__get-dumps |
Dump output |
Telescope MCP
If you have Laravel Telescope installed, add the MCP wrapper for Claude access:
| Tool | Purpose |
|---|---|
mcp__laravel-telescope__requests |
HTTP requests with exceptions |
mcp__laravel-telescope__exceptions |
Stack traces and error details |
mcp__laravel-telescope__queries |
Slow and failed database queries |
mcp__laravel-telescope__jobs |
Failed queue jobs |
mcp__laravel-telescope__logs |
Application logs |
mcp__laravel-telescope__mail |
Sent emails |
Without these tools, /debug falls back to reading storage/logs/laravel.log.
What Gets Published
Configuration
Publish the config to customize:
Re-syncing
When you add packages, re-run sync to get their agents:
Use --force to update existing agents with latest versions:
Use Cases
New Feature Development
Debugging Production Issues
Code Review Before PR
Resuming After a Break
Requirements
- PHP 8.2+
- Laravel 11 or 12
- Laravel Boost (installed automatically)
Credits
License
MIT
All versions of laravel-altitude with dependencies
illuminate/support Version ^11.0|^12.0|^13.0
laravel/boost Version ^1.0|^2.0