# The Codebreaker AI Build Lab — Employee Prompt Library

## The employee prompt library

Use these templates with real source material. Remove bracketed instructions before sending. Save the final prompt and result in the project log.

### 1. Audit before editing
> Inspect [SITE] and [FILES]. Inventory current pages, CTAs, media, forms, accessibility, policies, and deployed status. Identify what already works and what is unverified. Propose a small change map preserving existing work. Cite the exact source for names, prices, claims, and links.

### 2. Write executive copy
> Draft [PAGE] for [AUDIENCE] and [ACTION]. Use only facts in [SOURCE REGISTER]. Separate direct achievements from supported business scale. Give the first 30 seconds a clear headline, proof, and action. Flag gaps. Avoid generic hype and unsupported numbers.

### 3. Build an accessible page
> Implement [PAGE MAP] in [PLATFORM]. Match [DESIGN TOKENS]. Use semantic headings, descriptive buttons, responsive images, keyboard focus, and reduced motion. Keep an editable path for the owner. Test 375-pixel mobile and desktop layouts; report actual results.

### 4. Match products to checkout
> Make a table of [PRODUCT/SKU], price, variant, photo, and approved payment URL. Open and verify each destination and amount. Do not enable purchase when variants, shipping, tax, fulfillment, or terms are unresolved. Report live and pending states per product.

### 5. Improve a form
> Reproduce the reported form problem at [URL]. Test focus, typing, validation, submission, confirmation, and delivery. Keep existing submissions safe. Fix the smallest cause and retest on phone and keyboard. Include the recipient's proof of delivery where available.

### 6. Prepare an image edit
> The attached image is the identity reference for [PERSON]. Preserve recognizable features and only adjust [BACKGROUND/ATTIRE/CROP]. Match the team's [STYLE]. Do not substitute another person. Inspect the result against the source before it is used publicly.

### 7. Research a link or claim
> Verify [NAME/CLAIM/URL] against the official organization and a second reliable source where useful. Distinguish similar domains and people. Record the source, date, exact supported claim, and any uncertainty. Do not infer affiliation from proximity in search results.

### 8. Troubleshoot access
> We are authorized to edit [SITE], but [EXACT ERROR] blocks [ACTION]. Inspect supported access routes and current tool state. Try one fresh authorized session or supported connector. Do not bypass security controls or request a password in chat. Continue preparing reviewable changes and identify the minimum owner action needed.

### 9. Verify a launch
> Inspect the actual production URL [URL]. Test [CRITICAL JOURNEYS] on phone and desktop, including downstream confirmation. Compare against the approved brief and current assets. Report deployed version, observed pass/fail, untested items, and owner actions. Do not call it live based only on a preview.

### 10. Preserve context across a handoff
> Summarize the project for another employee: objective, source-of-truth files, current production URL/version, approved decisions, completed changes, tested results, blockers, credentials/access route (without secrets), and the next three actions. Separate verified facts from assumptions.

---