# Claude Code prompt pack for the Remotfix website

These prompts are designed for Claude Code working inside this repository.

---

## 1) Full repository audit
```text
Read CLAUDE.md, then inspect the full repository.
Create a concise audit of:
1. information architecture
2. strongest conversion sections
3. weakest pages or sections
4. broken links or missing metadata
5. top 10 improvements by impact

Do not change files yet.
```

## 2) Homepage conversion upgrade
```text
Read index.html and CLAUDE.md.
Upgrade the homepage for conversion:
- stronger hero headline
- better section order
- clearer business outcomes
- stronger CTA language
- more explicit cross-links to service pages

Keep the existing design system and asset paths.
Then summarize what changed and why.
```

## 3) Add proof and trust signals
```text
Review all public pages.
Add trust-building elements without inventing fake claims:
- process clarity
- response expectations
- service boundaries
- FAQ improvements
- security-minded wording where relevant

Do not add fake client logos, fake testimonials, or fake certifications.
```

## 4) Remote Access Agent positioning pass
```text
Review remote-access-agent.html, remote-it-support.html, and services.html.
Strengthen the positioning of the Remote Access Agent offer:
- emphasize business value
- explain unattended support clearly
- show how it improves support readiness
- cross-sell security and AI-integrated workflows

Keep copy concise and premium.
```

## 5) AI Integrated service refinement
```text
Review ai-integration.html and all related pages.
Improve the AI Integrated service so it feels practical and trustworthy.
Make sure the page emphasizes:
- human review
- workflow value
- content and documentation leverage
- cross-sell with website and Google Business Profile work

Avoid hype and vague “AI transformation” language.
```

## 6) SEO pass for all pages
```text
Audit every HTML page for:
- title tags
- meta descriptions
- canonical links
- heading hierarchy
- internal linking opportunities

Apply fixes directly and then update sitemap.xml if needed.
```

## 7) Accessibility pass
```text
Audit the site for likely accessibility issues.
Focus on:
- link clarity
- alt text quality
- heading hierarchy
- form labels
- color contrast risks
- button text quality

Apply fixes directly where obvious and list any manual follow-up items.
```

## 8) Mobile polish pass
```text
Review the CSS and HTML with a mobile-first QA mindset.
Improve:
- spacing
- nav usability
- CTA stacking
- card readability
- section density on small screens

Do not introduce a framework.
```

## 9) Build a new landing page for a campaign
```text
Create a new static HTML landing page for [INSERT OFFER].
Requirements:
- one focused offer
- hero, benefits, FAQ, CTA
- use existing CSS classes where possible
- keep the shared header/footer
- add metadata and include the page in sitemap.xml
```

## 10) Bundle/package refinement
```text
Review services.html and improve the bundle section.
Create 3 clearer package tiers with:
- audience fit
- deliverables
- business outcomes
- CTA text

Do not use exact pricing unless already provided by the user.
```

## 11) Content repurposing for Google Business Profile
```text
Read google-business-profile-management.html.
Create 10 short GBP post ideas based on the current service positioning.
Save them to a markdown file named `gbp-content-ideas.md`.
Keep the tone practical and local-business friendly.
```

## 12) FAQ generation for every service page
```text
Read each service page and generate 4 to 6 FAQs that reduce buyer hesitation.
Use real objections and real clarifications.
Add them directly to the page using the existing FAQ pattern.
```

## 13) Create a Netlify deployment checklist
```text
Create `DEPLOYMENT-CHECKLIST.md` for this repository.
Include:
- pre-deploy QA
- asset checks
- metadata checks
- sitemap and robots checks
- form test
- mobile QA
- post-deploy verification
```

## 14) Create a stronger README for future collaborators
```text
Rewrite README.md so a future collaborator can understand:
- site purpose
- page map
- brand tone
- editing rules
- deployment steps
- common mistakes to avoid
```

## 15) Generate a new Claude Code skill for service page creation
```text
Create a new skill under `.claude/skills/create-service-page/SKILL.md`.
The skill should help Claude Code generate new Remotfix service pages that:
- follow the design system
- include metadata
- include CTA sections
- cross-link related services
- update sitemap.xml
```

## 16) Structured content QA after major edits
```text
Use the content-qa skill.
Run a repository-wide QA pass after the latest changes.
Return:
1. files checked
2. issues fixed
3. issues still needing manual review
```

## 17) Hook idea prompt
```text
I want a Claude Code hook strategy for this repository.
Propose hooks that automatically:
- remind the agent to update sitemap.xml when new pages are added
- run a link check when HTML files change
- verify required metadata fields exist
Do not implement yet. First write a plan in `docs/claude-hook-strategy.md`.
```

## 18) Brand voice tightening
```text
Review all visible marketing copy.
Tighten the tone so it sounds:
- more premium
- more direct
- more business-oriented
- less generic

Keep the voice consistent across every page.
```


## Premium v3 follow-up prompts

- Refactor this static site into reusable HTML partials while keeping it Netlify-ready.
- Convert the pricing cards into a JSON-driven component so package details can be edited in one place.
- Add schema markup for FAQPage, Service, and Offer on pricing and solution pages.
- Build a lightweight site config file for contact links, booking URL, and social links.
- Generate an accessibility pass report and fix contrast, focus states, and landmark labels.