/mobile
Find out why your page looks broken on phones
Audit one screen for mobile readiness and hand back a numbered plan you can give to /preflight.
What it does
Half your visitors are on phones, and the page you built on a 27-inch monitor is silently unusable for them. /mobile audits one screen you name for text that overflows, tap targets too close together, and layouts that assume width, then returns a numbered fix plan.
It detects whether your project is a web app or phone-native first, then audits against the matching checklist. It deliberately doesn't edit anything: you review the plan, hand it to /preflight, and the fixes happen with your eyes open.
What it looks like
/mobile the pricing page
Web app detected, auditing against the responsive checklist. Five findings: 1. The plan-comparison table overflows and can't scroll sideways. 2. The buy buttons sit 4 pixels apart, but thumb-sized targets need 44. 3. The FAQ text is 12px on phones. 4. The hero image loads full-size, 1.8MB on cell data. 5. The sticky header covers the first heading when you scroll. Hand this list to /preflight when you're ready.
Illustrative exchange. Output adapts to your actual project.
When to type /mobile
- Someone opened your app on a phone and sent a screenshot of the damage
- You built desktop-first and it's time to pay the bill
- One specific page looks wrong on mobile and you want the full list, not one fix
- You want a mobile plan you can review before code changes
Pairs well with
Works in every major agent
/mobile installs as a plain file in your project and runs wherever your agent does.
Get /mobile and 21 more commands
Install it once. One license gets your agent the full Boost OS menu, seven always-on guards, and a memory of your project that survives between sessions. Lifetime updates.
From $99 · 7-day refund · license key emailed instantly