arm-pz

Pre Ship Performance Audit — Security skill for Claude Code

Security community

Agent skill that audits and fixes web app performance before launch: four read-only subagents check images, fonts, bundles, database queries and servers, then same-condition mobile Lighthouse medians.

How to install Pre Ship Performance Audit

This entry records only its repository, not the path inside it, so there is no exact command to give. Open arm-pz/pre-ship-performance-audit and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Pre Ship Performance Audit does

Alternatives in Security

Mobile First Audit.Skill — mobile-first-audit.skill.md 265 ★
Postgres — Execute safe read-only SQL queries against PostgreSQL databases with multi-connection support and defense-in-d 159 ★
Reactnative Expo AI Agent System Workflow — AI-powered development toolkit with 7 production agents for React Native/Expo mobile apps 125 ★

README

pre-ship-performance-audit

Make a web app measurably faster before you ship it. An agent skill for Claude Code, Cursor and Qoder: four independent read-only subagents audit twenty known slow-downs across images and fonts, frontend bundles and rendering, database queries and APIs, and servers and networks — then your agent fixes them and proves each fix with mobile Lighthouse medians run under identical conditions, before and after. For developers shipping a site they own or are authorized to maintain.

Install

npx skills add arm-pz/pre-ship-performance-audit --skill pre-ship-performance-audit

Or place `SKILL.md` in your agent's skills directory, for example:

# Claude Code (project)
mkdir -p .claude/skills/pre-ship-performance-audit && cp SKILL.md .claude/skills/pre-ship-performance-audit/
# Qoder (user)
mkdir -p ~/.qoder/skills/pre-ship-performance-audit && cp SKILL.md ~/.qoder/skills/pre-ship-performance-audit/

This repo is also a Claude Code plugin (`.claude-plugin/plugin.json`); it is listed in the `arm-pz/caffeinity-skills` marketplace.

Ask it things like

/pre-ship-performance-audit — check this site before I deploy
The homepage feels slow on mobile, find out why and fix it
Run the four audits and give me before/after Lighthouse numbers
Why is this list page slow? Check queries and indexes

How it works

Baseline — production build (or approved preview), mobile Lighthouse ×3 per page, medians recorded. If a production build cannot run, the limitation is stated; no numbers are invented.
Four read-only subagent audits — one per group: images/fonts/third-party scripts; frontend bundle and rendering; database and APIs (query plans, indexes, RLS, N+1, pagination, caching, background jobs — run at higher effort); server/network/routing plus main user flows under low-end mobile emulation.
Consolidated findings — prioritized P0–P3 backlog; every finding names file, route, measured evidence, proposed fi