# Advanced Claude Code Field Guide Preview

Build, Automate, Debug, Ship, and Monetize With AI

By AI Guide Guy

Preview Edition

Independent guide. Not affiliated with, sponsored by, or endorsed by Anthropic.

---

## What You Get In The Full Guide

The full Advanced Claude Code Field Guide is a 101-page PDF for serious Claude Code users.

Inside the full guide:

- Desktop, web, terminal CLI, and IDE workflows
- Advanced prompting systems
- Build, debug, refactor, and review prompts
- CLAUDE.md guidance and templates
- Safety and permission workflows
- Subagent, skill, MCP, hook, and routine guidance
- Best and worst use cases
- Freelance services and pricing playbooks
- Practical project blueprints
- Advanced prompt bank
- Client operations templates
- Advanced checklists

---

# Sample: The Safe Operating Model

Advanced Claude Code use is not about giving bigger prompts. It is about creating a workflow that makes bigger tasks safe.

The operating model is:

1. Inspect
2. Plan
3. Scope
4. Implement
5. Review
6. Test
7. Document
8. Deliver

Use this for any serious task:

```text
Inspect this project and create a short task plan.

Goal:
[describe the outcome]

Constraints:
- Do not edit files yet.
- Identify the relevant files.
- Recommend the smallest safe sequence of changes.
- List risks and assumptions.

Done when:
I have a plan I can approve before implementation.
```

---

# Sample: Advanced Prompt Formula

Use this formula:

- Role
- Goal
- Project context
- Files or areas to inspect
- Constraints
- Output format
- Done-when criteria
- Risk limits

```text
Role:
Act as a senior software engineer helping me complete a focused project task.

Goal:
[Describe the result.]

Project context:
[Describe the app, stack, user, current behavior, and business goal.]

Inspect:
[List files, folders, pages, or flows to inspect first.]

Constraints:
- Keep the change focused.
- Follow existing patterns.
- Do not touch unrelated files.
- Do not add dependencies unless justified.

Output format:
Start with a short plan. After edits, list changed files, tests/checks, risks, and next steps.

Done when:
[Define finished behavior.]
```

---

# Sample: Service Packaging

Claude Code can help you deliver faster, but your offer still needs a clear business outcome.

Good service categories:

- Websites
- Automations and recurring tasks
- Internal tools
- Dashboards
- Documentation
- Bug fixes
- AI workflow setup
- Maintenance

Example productized service:

| Service | Outcome |
| --- | --- |
| Website Fix Sprint | Fix visible issues that reduce trust or conversions |
| Landing Page Build | Create a focused page for a single offer |
| MVP Prototype | Build a small proof-of-concept product |
| Automation Script | Remove a repeated manual task |

---

# Sample: Client Handoff Prompt

```text
Create a client handoff summary.

Include:
1. What was changed
2. Why it matters
3. How to review it
4. What was tested
5. What was not included
6. Recommended next steps
7. Support or maintenance option

Use professional plain English.
```

---

# Sample: Advanced Project Blueprint

## Website Fix Sprint

Outcome: fix visible issues on a small business website.

Steps:

1. Intake and access
2. Backup or duplicate site
3. Claude Code inspection
4. Issue list
5. Client approval
6. Fix 3-5 issues
7. Mobile review
8. Handoff

Claude Code prompt:

```text
Run a Website Fix Sprint inspection.
Review the site/project for visible issues that hurt trust or conversion.
Focus on mobile layout, broken links, buttons, forms, confusing copy, spacing, and obvious polish.
Return a prioritized list before editing.
```

---

# Full Guide

The full guide includes 101 polished pages, advanced workflows, monetization sections, project blueprints, CLAUDE.md templates, prompt banks, client templates, and professional delivery checklists.