How to Turn Approved Feedback Into a Working Style Guide With Claude

Warning: Only use approved feedback and approved references for this workflow. Mixing approved and rejected directions creates a style guide that fights itself.

Problem and who this is for

Most execution drift happens because the team keeps re-learning the client's taste on every new draft. A short working style guide fixes that by turning approved comments, references, and call notes into reusable guidance for future work.

This workflow is for freelancers, consultants, and small agencies who deliver iterative work and want cleaner consistency across future drafts.

Prerequisites

• Claude access.
• Approved client feedback from email, comments, or call notes.
• Example references the client explicitly liked.
• A place to store the final style guide, such as a project wiki, internal doc, or folder note.

How to capture or gather the source material

1. Pull together only the approved comments and approved examples.
2. Create one plain text note called approved-feedback.txt that contains the phrases, changes, and preferences the client clearly accepted.
3. Create one reference note or small file set that shows the examples the client liked.
4. If there were calls that clarified taste or standards, summarize those notes into one short document.
5. Leave rejected directions out. This guide should show what to repeat, not every option that was ever discussed.

Numbered workflow steps

1) Upload the approved source pack to Claude

Use a direct upload or a Claude project if the guide will be updated over time. Upload the approved feedback note, approved references, and any call summary that explains why those choices were approved.

2) Extract repeatable preferences first

Ask Claude to identify recurring approved patterns, not just individual one-off edits. Look for tone, structure, visuals, pacing, level of detail, naming preferences, and approval boundaries.

3) Review the extracted preferences

Delete anything that feels too broad or too subjective to guide future work. A style guide works best when it focuses on repeatable patterns that actually help the next draft.

4) Generate the short working style guide

Ask Claude for a compact guide with sections like approved traits, do this, avoid this, reference examples, and checklist before sending the next draft.

5) Keep updating the guide as approvals accumulate

This is a living working document. Add new approved signals after each major review round so the guide becomes more useful over time.

Tool-specific instructions

Claude is the best primary tool here because this workflow depends on turning mixed uploaded source material into a compact reusable document. It works especially well when you want a clear internal guide rather than a polished client-facing deck.

NotebookLM is a good alternative when you want more grounded question answering across the source set before drafting the final guide. ChatGPT can work for a smaller source pack when you just need a fast first version.

Copy and paste prompt blocks

Preference extraction prompt

{
  "task": "Extract repeatable approved preferences from the uploaded client feedback sources",
  "goal": "Identify patterns that should guide future drafts",
  "instructions": [
    "Use only approved feedback, approved examples, and approved call notes.",
    "Look for recurring patterns, not one-off cosmetic edits.",
    "Separate clear preferences from uncertain interpretation.",
    "Do not include rejected directions."
  ],
  "output_format": {
    "approved_patterns": [],
    "do_this": [],
    "avoid_this": [],
    "reference_examples": [],
    "uncertain_items": []
  }
}

Working style guide prompt

{
  "task": "Turn the reviewed extraction into a short working style guide",
  "input": {
    "reviewed_preference_map": "PASTE THE REVIEWED OUTPUT"
  },
  "instructions": [
    "Write for the person creating the next draft.",
    "Keep the guide short and practical.",
    "Use sections for approved traits, do this, avoid this, and final pre-send checks.",
    "Do not invent taste rules that the source did not support."
  ],
  "output_format": {
    "working_style_guide": []
  }
}

Quality checks

1. The guide is based on approved feedback only.
2. Patterns are specific enough to guide the next draft.
3. Rejected directions and vague interpretations are excluded.
4. The final guide is short enough to use before each delivery.

Common failure modes and fixes

The guide becomes a vague mood board summary

Fix: ask for repeatable traits, concrete do-this rules, and avoid-this rules instead of broad brand adjectives.

Conflicting client comments slip in

Fix: keep only clearly approved material in the source pack.

The guide is too long to use

Fix: limit the final guide to one page or a short checklist that can be reviewed before delivery.

Sources Checked

• Anthropic Claude Help Center: Uploading files to Claude (accessed 2026-03-24) https://support.claude.com/en/articles/8241126-uploading-files-to-claude
• Anthropic Claude Help Center: What are projects? (accessed 2026-03-24) https://support.anthropic.com/en/articles/9517075-what-are-projects
• Anthropic Claude Help Center: How can I create and manage projects? (accessed 2026-03-24) https://support.claude.com/en/articles/9519177-how-can-i-create-and-manage-projects
• Google Workspace: NotebookLM product page (accessed 2026-03-24) https://workspace.google.com/products/notebooklm/
• OpenAI Help Center: Data analysis with ChatGPT (accessed 2026-03-24) https://help.openai.com/en/articles/8437071-data-analysis-with-chatgpt

Quarterly Refresh Flag

Review on 2026-06-22 to confirm any changes to tool availability, file handling, supported source types, limits, plan requirements, and mobile workflow steps.