# RapidAir Reference Playbook Outline

**Document type:** Guide / resource  
**Audience:** Designers and operators picking up future audit-farming work  
**Prepared for:** RoleModel Software  
**Estimated length:** 8 pages (cover + 7 interior pages)

## Cover
- Title: RapidAir Reference Playbook
- Subtitle: How the first audit run became a repeatable farming workflow
- Meta: Prepared for RoleModel Software · May 2026

## Page 2 - Why this example matters
- Purpose of the playbook
- End-to-end pipeline
- Component treatment: body text, note box

## Page 3 - Start from the running product
- Run the product code
- Audit the experience
- Component treatment: body text, two-column definition list

## Page 4 - Turn findings into a report artifact
- Build the coded report
- What the first run taught us about narrative, scope, and cleanup
- Component treatment: body text, numbered list

## Page 5 - Move from report to design
- Figma review surface
- Figma Make exploration
- Component treatment: body text, note box

## Page 6 - Prove interaction when interaction is the argument
- React demo role
- When a demo is worth the extra work
- Component treatment: body text, highlight list

## Page 7 - Publish and preserve the system boundary
- Vercel role
- Why reports, demos, and reusable skill code live separately
- Component treatment: body text, note box

## Page 8 - The reusable operating model
- Future-state checklist
- What to copy, avoid, and improve
- Component treatment: numbered list, final takeaway box