Table of Contents
You have eleven resume files named “Resume_final,” “Resume_final_v2,” and “Resume_FINAL_actually_final,” and no idea which one has the right dates.
Then a job post lands that you want, and you spend an hour copying bullets between documents, hoping you did not paste last year’s job title into this year’s application.
That is a file problem, not a writing problem. Claude Cowork is built for file problems. These Claude Cowork prompts for resume work turn a messy folder of old resumes, work documents, and saved job posts into a clean master resume, tailored versions for each job, and a tracker that tells you who to follow up with.
You get 10 prompts, each with a role, your context, a step-by-step process, firm rules, and an exact output format. Every one tells Claude to leave your originals untouched and to use only facts found in your files, because a made-up number on a resume is a risk you never need to take.
What Claude Cowork Changes for Resume Work
In regular chat, you paste text and get text back. With Cowork, you point Claude at a folder and ask for a finished result.
You describe the outcome you want, and Claude plans the work, carries out the steps with the tools and files it needs, and returns a real deliverable. For a job search, that means reading a pile of old documents and producing Word files, spreadsheets, and PDFs you can use straight away.
Several features matter here. Cowork works with Word, PDF, Excel, PowerPoint, image, and CSV files, splits large projects into subtasks that run together, runs scheduled tasks unattended, and shows every step it takes. Parallel subtasks are what make batch tailoring practical. You can tailor ten resumes without doing the same chore ten times.
One note on the product itself. Cowork has been changing, and Anthropic has merged Cowork and chat into one Claude. The new experience makes everything Cowork does available from any conversation, and it is rolling out gradually to Pro and Max plans. So you may not see a separate Cowork area. Open a conversation, give Claude access to a folder, and paste the prompt. Availability depends on your plan and rollout stage, so check your own account.
How to Set Up Your Resume Folder for Claude Cowork
A tidy folder makes every prompt below work better. Five minutes of setup saves you from confusion later.
- Create one main folder called Job-Search, and give Claude access to that folder only.
- Add six subfolders: 01-Source, 02-Master, 03-Jobs, 04-Tailored, 05-Packs, and 06-Tracker.
- Copy your material into 01-Source. Include old resumes, a LinkedIn profile export, performance reviews, and project documents. Use copies, not your only versions.
- Save job posts into 03-Jobs. Use PDF, Word, or text files, and put the company name in each file name.
- Leave sensitive documents out. Skip ID scans, bank details, and anything with personal data you would not put on a resume.
Cowork works with permission per folder and per tool, and it asks before irreversible actions such as deleting files. Even so, the safest habit is working on copies, and every prompt below saves new files instead of overwriting your originals.
A practical limit to know about: tasks that use local files, your browser, or desktop apps need Claude Desktop to be open and connected. Keep the app running while a job is in progress.
Claude Cowork Prompts for Resume Foundations
Start with your raw material. These two prompts turn scattered files into a master resume and an evidence bank.
1. Build a Master Resume From All Your Old Files
This prompt reads everything in your source folder and builds one complete, consistent record of your career.
<role>
You are a senior resume writer and document analyst. You are careful, you never invent facts, and you flag every inconsistency instead of silently fixing it.
</role>
<context>
The folder 01-Source contains my old resumes, a LinkedIn export, performance reviews, and project documents. Build a master resume that contains my complete career record. Do not modify, move, or delete any original file.
</context>
<inputs>
My target direction (roles or fields): {{PASTE}}
City or region to show, and which contact details to include: {{PASTE}}
Anything I know is outdated or wrong in my old files: {{PASTE, OR WRITE "NONE"}}
</inputs>
<instructions>
1. List every file you read, with its type and last modified date.
2. Extract all roles (job title, employer, location, start and end dates), education, certifications, skills, tools, awards, and achievements.
3. Compare the information across files. List every conflict, such as different dates, titles, employer names, or numbers, with the file names where each version appears.
4. Where files conflict, provisionally use the most recent and most detailed version, and mark it clearly as "Needs my confirmation."
5. Create a Word document named Master-Resume-YYYY-MM in the 02-Master folder. Use plain formatting with no tables, columns, text boxes, or images. Use reverse-chronological order and these headings: Professional Summary, Experience, Education, Certifications, Skills. Include every role and every achievement, and do not shorten for length. This is the full record, not the final application version.
6. Create a second Word document named Conflicts-and-Gaps in the same folder. It should list the conflicts, employment gaps of more than three months (shown as dates only, with no commentary), and achievements that lack numbers, each with where I might find the numbers.
7. In your reply, summarize what you built and the five most important items I need to confirm.
</instructions>
<rules>
- Use only facts found in my files. Never invent titles, dates, numbers, tools, or achievements.
- Keep all original files exactly as they are.
- Do not include ID numbers, home address, date of birth, or other sensitive personal data.
- Mark every uncertain item instead of choosing silently.
</rules>
<output_format>
Two saved Word documents in 02-Master, plus a chat summary with the top five items needing my confirmation.
</output_format>
Resolve the conflicts list before running any other prompt. Every later resume inherits whatever errors remain in the master.
2. Mine Your Work Files for Achievements You Forgot
Your best proof is probably buried in a report, a deck, or a review document. This prompt finds it and records where it came from.
<role>
You are an evidence-focused career analyst who finds quantified achievements inside work documents and records exactly where each one came from.
</role>
<context>
The folder 01-Source/Work-Evidence contains reports, presentations, spreadsheets, performance reviews, and project documents I created or was involved in. Find achievements I can use on a resume.
</context>
<inputs>
My roles and the periods I held them: {{PASTE}}
The kind of roles I am targeting next: {{PASTE}}
</inputs>
<instructions>
1. Read every file in the folder. For each file, note what it is, the date, and which of my roles it relates to.
2. Extract every result, outcome, number, improvement, award, or piece of positive feedback that appears in the files and that I plausibly contributed to. Include only items where my role is clear from the document. If my role is unclear, list the item separately under "Needs my confirmation."
3. Write each achievement in Challenge, Action, Result form, using only what the files show.
4. Create an Excel workbook named Achievement-Bank in 02-Master with one row per achievement and these columns: Role, Achievement, Challenge, Action, Result, Metric, Source File, Location in File (page, slide, or sheet), Skills Shown, Strength for Target Roles (Strong, Medium, Weak), Verified (Yes, Partly, or No), Notes.
5. Add a second sheet named Numbers to Find, listing achievements with no metric, and where a number might exist.
6. Add a third sheet named Discrepancies, listing any case where two files give different numbers for the same result.
7. In your reply, list my fifteen strongest achievements for my target roles, each in one line.
</instructions>
<rules>
- Use only facts shown in the files. Do not estimate or round up.
- Record the source file and location for every row so I can verify it.
- Do not include confidential client names unless I listed them as allowed here: {{PASTE ALLOWED NAMES, OR WRITE "NONE"}}
- Do not modify any original file.
</rules>
<output_format>
One Excel workbook with three sheets saved in 02-Master, plus a chat summary listing the fifteen strongest achievements.
</output_format>
Check the Source File column before you trust any row. That column is what makes this a safe evidence bank instead of a pile of claims.
Claude Cowork Prompts for Tailoring Resumes at Scale
Once your master record is solid, tailoring becomes a repeatable process instead of a late-night chore.
3. Turn a Folder of Job Posts Into a Requirements Map
Ten postings for the same role show you what employers actually want. This prompt reads them all and counts.
<role>
You are a labor market analyst who reads job postings for patterns. You report counts and quotes, not impressions.
</role>
<context>
The folder 03-Jobs contains job postings I saved, in PDF, Word, or text form. Analyze them together. Use only the text in the files.
</context>
<inputs>
The role I am targeting: {{PASTE}}
My master resume location: 02-Master
</inputs>
<instructions>
1. Read every posting. For each, extract: company, job title, location and work mode (remote, hybrid, on-site), seniority signals, salary or pay range if stated, required skills, preferred skills, tools, and years of experience asked.
2. Create an Excel workbook named Job-Library in 03-Jobs with these sheets:
- Postings: one row per posting with the fields above and the file name.
- Requirements: every distinct requirement or skill found, with the number of postings that mention it, calculated with formulas, sorted from most to least frequent.
- Keywords: the exact phrases used across postings, grouped by theme, with counts.
- Warning Signs: any posting that shows concerns, such as a request for payment, no company details, or vague duties, with a quote.
3. Create a Word summary named Market-Summary in 03-Jobs with: the ten most common requirements, which are must-haves and which are nice-to-haves, stated salary ranges with company names, the language employers use for the role, and the limits of the analysis.
4. Compare my master resume with the top ten requirements. Show matches, partial matches, and gaps in a table.
5. In your reply, give a five-line summary and flag any posting with warning signs.
</instructions>
<rules>
- Use only the text of the files. Write NOT STATED for missing information.
- Use formulas for counts so I can audit them.
- Do not modify the original postings.
- Do not guess at salaries.
</rules>
<output_format>
One Excel workbook and one Word summary in 03-Jobs, plus a chat summary.
</output_format>
The Warning Signs sheet is easy to ignore, and it is worth a glance. A posting that asks you to pay for anything should leave your list.
4. Find the Gaps Between Your Record and the Roles You Want
Before tailoring, learn where your evidence is thin. This prompt shows the honest picture and a plan for closing it.
<role>
You are a career strategist who gives candid, practical gap analyses. You are honest about weak fit and specific about fixes.
</role>
<context>
Compare my record with the roles I am targeting. Use my master resume, my achievement bank, and the Job-Library workbook. Do not edit any of them.
</context>
<inputs>
Files: 02-Master (Master Resume and Achievement-Bank) and 03-Jobs (Job-Library)
My timeline for landing a role: {{PASTE}}
Hours per week I can spend building skills: {{PASTE}}
</inputs>
<instructions>
1. Take the ten most frequent requirements from the Job-Library. For each, find my best evidence in the master resume or achievement bank and cite the source row or file.
2. Rate each requirement: Strong (clear evidence with a metric), Partial (some evidence), or Gap (no evidence).
3. For each Partial or Gap, suggest the fastest honest way to build or show evidence: a small project, a short course, volunteer work, a certification, or a way to describe past work differently. Give an estimated time and the evidence I could add to my resume when done.
4. Identify the requirements that matter most across postings, and rank the gaps by their effect on my chances.
5. Identify any postings in the library where my fit is weak enough that I should not apply yet, and say why.
6. Create a Word document named Gap-Analysis in 02-Master with a summary table, the plan, and a 60-day schedule that fits my available hours.
7. In your reply, give me the three gaps worth closing first.
</instructions>
<rules>
- Be honest about weak matches.
- Cite my files for every claim about my experience.
- Do not suggest claiming skills I do not have.
</rules>
<output_format>
One Word document saved in 02-Master, plus a chat summary with three priorities.
</output_format>
Closing one gap with a real, visible project often does more than rewording ten bullets.
5. Tailor a Resume for Every Job Post in a Folder
This is the prompt that saves the most time. It creates one tailored resume per posting and records exactly what changed.
<role>
You are a professional resume writer who tailors resumes to specific job postings while keeping every statement truthful and provable.
</role>
<context>
Create a tailored resume for each job posting in 03-Jobs, using only my Master Resume and Achievement-Bank from 02-Master. Treat each posting as a separate subtask.
</context>
<inputs>
Postings to process: {{PASTE FILE NAMES, OR WRITE "ALL NEW POSTINGS"}}
Length rule: one page if I have under 10 years of experience, otherwise a maximum of two pages. My years of experience: {{PASTE}}
Anything I want emphasized or avoided: {{PASTE, OR WRITE "NONE"}}
</inputs>
<instructions>
For each posting:
1. Identify the employer's five most important requirements.
2. Decide which of my experiences prove those requirements best, and lead with them.
3. Keep three to five bullets for each recent role and two or three for older roles. Cut anything irrelevant to this posting. Draw bullets only from my master resume and achievement bank.
4. Write each bullet in 18 to 28 words, starting with a specific action verb and leading with the result where possible. Mirror the posting's wording only where it truthfully describes what I did.
5. Write a professional summary of 45 to 65 words tailored to the role.
6. Build a skills section grouped into three or four categories, ordered by relevance to the posting, using only skills my records support.
7. Save a Word document in 04-Tailored named Company_Role_Resume_YYYY-MM-DD, using plain formatting: standard headings, no tables, columns, text boxes, or images.
8. Save a short change note for each resume in the same folder, named Company_Role_Changes, listing what was led with, what was cut, which keywords were added and where, and every number used with its source row.
After all postings are done:
9. Create an Excel workbook named Tailoring-Summary in 04-Tailored listing each resume file, the five requirements matched, the three lead bullets, and any claims I should verify.
10. If my fit for a posting is weak (fewer than three of its top five requirements supported by evidence), do not tailor it. Add it to a "Weak Fit" sheet with the reasons.
</instructions>
<rules>
- Use only facts from my master resume and achievement bank. Never invent numbers, titles, tools, or outcomes.
- No first-person pronouns. Keep tense consistent.
- Do not overwrite existing files. If a file name exists, add a number.
- Do not use filler such as "results-driven," "team player," or "responsible for."
</rules>
<output_format>
Tailored resumes and change notes in 04-Tailored, a Tailoring-Summary workbook with a Weak Fit sheet, and a chat summary.
</output_format>
Read the change notes for your top three applications before sending anything. They tell you in thirty seconds whether the tailoring is sound.
6. Check Every Resume for ATS and Formatting Problems
A resume can look perfect and still parse badly. This prompt tests the files, not just the wording.
<role>
You are a resume formatting and applicant tracking system specialist. You test documents methodically and report exactly what you find.
</role>
<context>
Check every Word document in 04-Tailored for formatting and readability problems. Never overwrite the originals. Save corrected copies separately.
</context>
<inputs>
Posting files for keyword checks: 03-Jobs
Whether any posting asks for a PDF: {{YES, NO, OR LIST WHICH}}
</inputs>
<instructions>
For each resume:
1. Check structure: no tables, columns, text boxes, images, or shapes; contact details placed in the body of the page, not only in a header or footer; standard section headings; consistent date format; a standard, readable font; bullets made with normal list formatting.
2. Extract the document's plain text and compare it with what the document shows. Report any content that goes missing, scrambles, or reorders.
3. Check page count and word count against the length rule.
4. Check spelling, punctuation, tense consistency, repeated opening verbs, and capitalization of names and tools.
5. Check that each number and claim matches the master resume or achievement bank, and report any difference.
6. Check keyword coverage against the matching posting: list the top ten posting requirements and mark each as Present or Missing in the resume.
7. Check the file name for clarity and a professional format.
8. If you find fixable issues, save a corrected copy named with the suffix _fixed. Keep wording changes minimal and list each one.
9. If a posting asks for a PDF, export a PDF copy and confirm the text can be selected.
10. Create an Excel workbook named ATS-QA-Report in 04-Tailored with one row per check per resume: File, Check, Result (Pass or Fail), Details, and Fix Applied.
11. In your reply, list every resume with at least one failed check.
</instructions>
<rules>
- Never overwrite an original. Save corrections as new files.
- Do not add keywords that my records do not support.
- Report problems plainly. Do not soften failures.
</rules>
<output_format>
An ATS-QA-Report workbook, corrected copies where needed, and a chat summary listing failures.
</output_format>
Open one corrected file yourself and scroll through it. Checking one by eye catches what no checklist covers.
Claude Cowork Prompts for Application Packs, Tracking, and Interviews
Applying is more than a resume. These four prompts handle everything around it.
7. Build a Complete Application Pack for One Job
A pack puts everything for one application in a single folder, so nothing gets sent to the wrong company.
<role>
You are a professional job application writer who prepares complete, consistent application packs. You write short, specific, employer-focused documents and you never exaggerate.
</role>
<context>
Prepare an application pack for the posting below, using my tailored resume, my master resume, and my achievement bank. Create a new folder for this application inside 05-Packs.
</context>
<inputs>
Posting file name in 03-Jobs: {{PASTE}}
Tailored resume file in 04-Tailored: {{PASTE}}
Company website address (if web access is on, read it; otherwise use the text I paste here): {{PASTE URL OR TEXT FROM THE COMPANY'S ABOUT AND CAREERS PAGES}}
Hiring manager's name, if known: {{PASTE, OR WRITE "UNKNOWN"}}
Screening questions from the application, if any: {{PASTE, OR WRITE "NONE"}}
</inputs>
<instructions>
1. Create a folder named Company_Role inside 05-Packs.
2. Copy the tailored resume into the folder, and create a PDF version if the posting asks for one.
3. Write a cover letter of 200 to 280 words in a Word document, using short paragraphs of 2 to 4 lines and no bullet points. Open with a simple, human sentence connected to a specific detail from the company's own material. Show the employer's need first, then two proof points with metrics from my files, and end with a simple invitation to talk.
4. Write a short application email of no more than 100 words.
5. If screening questions were provided, write an answer of 40 to 90 words for each, starting with a direct answer and supporting it with one specific example from my files.
6. Create a Word document named Verify-Before-Sending listing every claim and number used in the pack, with the file and location in my records that supports it, and any detail I must double-check.
7. Create a short Word document named Company-Notes with three sentences on what the company does, the problem this role appears to solve, and the specific details used in the letter, each with its source.
8. In your reply, list the files created and the three things I should check first.
</instructions>
<rules>
- Use only facts from my files and the company material I provided. Never invent results, company news, or quotes.
- Banned phrases: "I am writing to apply," "I am excited to apply," "I believe I would be a great fit," "passionate," "team player," "results-driven," "proven track record."
- If you cannot find a specific company detail, say so instead of using a generic compliment.
</rules>
<output_format>
One folder per application in 05-Packs containing the resume, cover letter, email, screening answers (if any), Verify-Before-Sending, and Company-Notes, plus a chat summary.
</output_format>
Review Verify-Before-Sending last, right before you submit. It is the one document that protects you from a wrong number.
The JSON Prompt Mastery for Claude collection includes 70+ pre-built structured prompts organized by business workflow, so you run the prompt and get the output without building anything from scratch. If you want ready-made prompts for the rest of your work once you land the job, it is built for that.
8. Create an Application Tracker That Does the Reminding
A tracker is only useful when it flags what needs attention. This prompt builds one with working formulas.
<role>
You are a spreadsheet specialist who builds clear, simple trackers with working formulas and sensible formatting.
</role>
<context>
Build an application tracker from the application packs in 05-Packs and the resumes in 04-Tailored. Save it in 06-Tracker.
</context>
<inputs>
Follow-up timing rules: {{PASTE, FOR EXAMPLE "FOLLOW UP 7 DAYS AFTER APPLYING, THEN 14 DAYS"}}
Status labels I want: {{PASTE, OR WRITE "USE A STANDARD SET"}}
</inputs>
<instructions>
1. Create an Excel workbook named Application-Tracker with a sheet named Applications and these columns: Company, Role, Posting File, Resume File Used, Pack Folder, Source (where I found it), Date Applied, Contact Person, Status, Next Action, Next Action Date, Follow-Up Due, Days Since Applied, Notes.
2. Fill in rows from the folders in 05-Packs. Fill Company, Role, Posting File, Resume File Used, and Pack Folder from the files. Leave Date Applied, Contact Person, Source, and Notes empty for me. Do not guess dates.
3. Set Status as a drop-down list with these options: Shortlisted, Pack Ready, Applied, Follow-Up Sent, Interview Scheduled, Interviewed, Offer, Rejected, Withdrawn.
4. Use formulas for Days Since Applied and for Follow-Up Due, based on my timing rules and Date Applied. Make the formulas return blank when Date Applied is empty.
5. Add conditional formatting to highlight rows where the follow-up date has passed and the status is Applied.
6. Create a second sheet named Summary with formulas showing the number of applications by status, the number applied in the last 7 days, the number of follow-ups overdue, and the response rate (applications that reached any interview status divided by applications marked Applied or later).
7. Freeze the header row and set sensible column widths.
8. Test the formulas by checking one row with a sample date, then clear the test value and tell me you did so.
9. In your reply, explain in four short lines how to use the tracker.
</instructions>
<rules>
- Do not invent application dates or contacts.
- Keep formulas simple and visible.
- Do not modify files in other folders.
</rules>
<output_format>
One Excel workbook saved in 06-Tracker and a short usage note in chat.
</output_format>
Fill in the Date Applied column on the day you apply. Everything else in the sheet depends on it.
9. Schedule a Weekly Job Search Digest
Scheduled tasks are where Cowork stops being a helper and starts being a habit. Cowork can run scheduled tasks unattended. Describe the schedule in the same request.
<role>
You are a job search assistant who prepares a short weekly plan from my tracker and saved postings. You are practical and specific.
</role>
<context>
Set this up as a recurring weekly task. Each run should read only the Job-Search folder and produce a one-page plan.
</context>
<inputs>
Schedule: {{FOR EXAMPLE: EVERY MONDAY AT 8 AM}}
Weekly goals: {{FOR EXAMPLE: 8 TAILORED APPLICATIONS, 5 NETWORKING MESSAGES}}
Roles and fit criteria I care about: {{PASTE}}
</inputs>
<instructions>
1. Read the tracker in 06-Tracker. List every application whose follow-up is due or overdue, with the company, role, date applied, and days since applied.
2. For each follow-up due, write a draft message of no more than 60 words that adds one useful point instead of only asking for an update. Use only facts in my files.
3. List applications with no change for 21 days or more and suggest one action for each.
4. Check 03-Jobs for postings added since the last digest. Rate each new posting against my fit criteria and the Job-Library requirements, from strongest to weakest, with one line of reasoning.
5. Write a Word document named Weekly-Digest-YYYY-MM-DD in 06-Tracker with these sections: Follow-Ups Due, Stale Applications, New Postings Ranked, and Five Priorities for This Week (aligned to my weekly goals).
6. If no postings or follow-ups exist, say so at the top rather than padding the document.
7. Mark anything uncertain with "Needs confirmation."
</instructions>
<rules>
- Do not send any message. Draft only.
- Do not change the tracker or any other file.
- Read only the Job-Search folder.
- Use only what is in the files.
</rules>
<output_format>
One Word document saved each week and a two-line summary in chat after each run.
</output_format>
Read the first two digests closely and adjust the goals. After that, a quick weekly skim is enough.
10. Prepare an Interview Pack From Your Own Application
When an interview invitation arrives, everything you need is already in your folders. This prompt assembles it into a single prep pack.
<role>
You are an interview coach who prepares candidates using only their real background. You are specific, honest, and practical.
</role>
<context>
I have an interview coming up. Build an interview prep pack using the application pack for this role, my achievement bank, and the original posting.
</context>
<inputs>
Pack folder in 05-Packs: {{PASTE}}
Interview type and date: {{PASTE}}
Interviewer names and roles, if known: {{PASTE, OR WRITE "UNKNOWN"}}
The salary range I am willing to share, if any: {{PASTE, OR WRITE "NONE"}}
</inputs>
<instructions>
1. Create a Word document named Interview-Prep in the pack folder with these sections:
- Role and Company Brief: what the company does, the problem the role solves, and the five requirements that matter most, based on the pack files.
- Likely Questions: ten questions, including four that probe specific lines in my resume (quote each line), three behavioral, two role-specific, and one about any gap or weakness visible in my record.
- Answer Outlines: for each question, a 60 to 100 word outline in Situation, Task, Action, Result form built only from my achievement bank. Cite the source row. Where my files lack a needed detail, write "YOU MUST ADD:" and say what is needed.
- A 30-Second Introduction: 80 to 100 words, in a natural spoken voice, built from my summary and strongest result.
- Questions I Should Ask: eight questions tailored to this role and company, ranked.
- Warning Signs to Listen For: five things that would suggest the role or team is not as described.
- Salary Approach: how to respond if asked about expectations, using only the range I gave, or a response that asks about the range for the role if I gave none.
2. Create a one-page PDF cheat sheet named Interview-Cheat-Sheet with my introduction, my five best proof points with metrics, the company's three key facts, and my top three questions to ask.
3. In your reply, list the three answers that need the most practice because my files lack detail.
</instructions>
<rules>
- Use only facts from my files. Never invent achievements, numbers, or situations.
- Keep every outline concise and written in spoken language.
- Do not state salary figures I did not provide.
</rules>
<output_format>
Two files saved in the pack folder, Interview-Prep (Word) and Interview-Cheat-Sheet (PDF), plus a chat summary.
</output_format>
Practice the introduction out loud until it sounds natural. It is the only part of the interview you can fully script.
Mistakes That Make Claude Cowork Resume Runs Go Wrong
Most failed runs trace back to a handful of habits.
Giving access to too much. Share the Job-Search folder, not your whole drive. A small folder keeps the task focused and the risk low.
Skipping the conflicts list. Prompt 1 surfaces errors in your own records. If you ignore it, those errors spread into every tailored resume.
Tailoring before the gap analysis. Applying to roles you are far from wastes effort. Run prompt 4 first and respect the Weak Fit list.
Trusting numbers you have not checked. Every output cites a source file. Open the file for any figure that appears in a letter or an interview answer.
Letting files pile up. Use consistent names and the folder structure above, or you recreate the original mess.
Forgetting the app must stay open. If a task reads local files and your computer sleeps, it may stall.
How to Combine These Claude Cowork Prompts Into a Job Search Routine
You do not need to run all ten at once. A simple order works.
Spend the first day on prompts 1 and 2 to build your master record. On day two, run prompts 3 and 4 to understand the market and your gaps.
For each batch of applications, run prompt 5 to tailor, prompt 6 to check the files, and prompt 7 for the packs you will send. Run prompt 8 once to create the tracker and prompt 9 once to schedule the digest. Prompt 10 comes out whenever an interview invitation arrives.
Keep the folder structure the same for every search. Next time you need a resume, the hard work will already be done.
Better Resumes Start With Better Files
All ten prompts follow the same pattern: real documents from you, a specific task, firm rules, and a defined output. That is why Cowork can return finished files you can check, instead of text you have to rebuild.
Start with prompt 1 on a copy of your old resumes. The conflicts list alone will show you what has been wrong in your documents for years.
When you want a larger set of structured prompts for everyday work, JSON Prompt Mastery for Claude has them organized by workflow. Build your master resume first, and see how much easier the next application feels.