Resume Customization Prompt – STRATEGIC INTEGRITY
Contributed by thanos0000@gmail.com
Improved by Laravel Company · 2026-09-07
Strategic Resume Customization v3.26 [INTEGRITY+ EXPANDED]
GUIDANCE & CHANGELOG
- Version: v3.26 [INTEGRITY+ EXPANDED]
- Author: Scott M. (Updated by [Your Name])
- Last Updated: [Current Date]
- Changelog:
- v3.26 [INTEGRITY+ EXPANDED]: Enhanced prompt structure, added detailed sub-guidelines, clarified formatting rules, and expanded strategic writing instructions.
- v3.25: Generic release.
QUICK START GUIDE
- Fill Variables: Replace the brackets in the "USER VARIABLES" section with precise information.
- Attach File: Upload your master documentâit could be a Skills Summary or your current resume file.
- Paste Job Posting: Put the target job description into the chat alongside this prompt.
- Execute: First, AI performs the Strategic Audit. Then, it generates the tailored documents, following the specified phases and output order.
USER VARIABLES (REQUIRED & STRUCTURED)
- NAME & CREDENTIALS: [Insert Full Name, including any relevant certifications, e.g., Jane Doe, CISSP]
- TARGET ROLE: [Insert Job Title, including any relevant sub-titles or focus areas, e.g., Senior Cybersecurity Engineer (Cloud)]
- SOURCE FILE: [Name of your uploaded file, e.g., Jane_Doe_CV_master.docx]
- SOURCE URL: [Link to your professional portfolio or GitHub profile, if applicable and relevant to the role]
STEP 1: THE DE-RISKING AUDIT [STRATEGIC FOUNDATION]
Perform a comprehensive Strategic Audit in plain text before writing:
- The Core Problem: Identify the literal technical or business challenge that slows down or endangers the company. Be specific.
- The Risk Barrier: Determine the primary reason they would hesitate to hire someone for this role. Pinpoint the exact fear or concern.
- The Language Map: Analyze the job description to extract 3-5 high-value technical terms, phrases, or concepts that appear repeatedly. These should become your "power words" for the application.
- The 99% Trap: Anticipate what the average applicant will focus on in their application. Then, find the oppositeâemphasize the "battle-tested" aspects of your experience and expertise that directly contrast with the typical approaches.
- The Breakthrough Metric: Search the source document for the single most powerful metric, achievement, or impact story that directly solves the "Core Problem" identified in step 1.
PHASE 2: MANDATORY OUTPUT ORDER & FORMATTING
PHASE 2A: THE STRUCTURAL FOUNDATION
- Header: [NAME & CREDENTIALS]. Use ( ⢠) for phone ⢠email ⢠LinkedIn. Ensure the contact information is clean and current.
- Professional Summary: Write in the first person using the companyâs "Power Words" identified in the Audit. Your voice should sound like an internal hire who understands the companyâs language and culture.
- AREAS OF EXPERTISE: This is a single, concise paragraph. List your top areas of technical expertise, separated by bold middle dots ( · ). Each item should be a specific domain or skill that directly applies to the role.
PHASE 2B: THE KEY ACHIEVEMENTS & EXPERIENCE
- Key Accomplishments: This section has exactly 3 bullets. The 1:1 Metric Rule: Every bullet must contain a number ($ or %), a percentage, or a specific metric that quantifies your impact. The eye should land on a clear result, not the process.
- Professional Experience: Use the following format:
- Job Title ⢠Company Name ⢠Dates (Month - Year)
- [Job responsibilities and key achievements in bullet points, separated by middle dots ( · ). Use the "Active Kill-Switch" guidelines below.]
PHASE 2C: THE SUPPORTING SECTIONS
- Early Career / Additional History: If relevant, provide a brief summary in the same format as Professional Experience.
- Education: List your degrees, institutions, and dates in a concise format.
- TECHNICAL COMPETENCIES: Create a categorized vertical list of tools, platforms, and programming languages. Do not list every tool you've ever used. Only include those that are relevant to the role and demonstrate your "battle-tested" expertise.
- Certifications / Licenses: List your relevant certifications or licenses, including the issuing organization and date earned.
PHASE 3: THE GOD MODE WRITING RULES [ADVANCED]
- The "Before" Test: Every bullet point must prove you have already solved the problem directly referenced in the job description. No "learning" vibes; you are already an expert.
- The Active Kill-Switch: Ban passive words like managed, responsible for, and assist. Use "Orchestrated," "Overhauled," "Captured," or other verbs that convey active, directive control.
- Eye-Tracking: Bold the win, not the task. The formatting should guide the readerâs eye straight to the result, not the process. Use bold text strategically to highlight the most impactful information.
- Before & Revised: For every updated section, first show the plain text version (Before) and then use a code block (
Revised) for the final version. This provides a clear before-and-after contrast. - Formatting: Strict use of middle dots ( · ) bullets and no blank lines between list items to maintain a clean, scannable structure.
PHASE 4: THE INSIDER COVER LETTER [ADVANCED STRATEGY]
- The Direct Lead: Start with a statement that directly addresses the hiring manager or the companyâs specific need, e.g., "I have done this exact work at [Company Name]" or a specific, bold claim that proves your relevance.
- The Proof Paragraph: Write one paragraph dedicated to a single, massive technical proof of your expertise. Avoid clichés like "passionate" or "motivated." Instead, provide a specific, technical achievement that shows you have already mastered the challenges of the role.
- The 250-Word Cap: Keep the letter under 250 words, ideally in 3 paragraphs or less. Every word should serve a specific purpose.
- Signature: [Full Name] only.
WRAP-UP & DELIVERABLES
- Recruiter Snapshot: Provide a fit percentage, the top 3 matches between your skills and the job requirements, and an honest summary of any gaps or areas for development.
- Revision Changelog: List each section processed and summarize the specific adjustments made to each.
SUB-GUIDELINES FOR ENHANCED STRATEGIC WRITING
- Sentence Length: Vary your sentence length to keep the reader engaged. Aim for a mix of short, medium, and long sentences.
- Paragraph Structure: Use the "Pyramid Principle" for your paragraphs: start with the most important point, then support it with evidence, and conclude with a summary.
- Storytelling: Where appropriate, use a narrative structure to frame your achievements and make them more relatable.
- Consistency: Ensure your voice and style remain consistent across the application, matching the companyâs tone and cultural cues.
Please execute the Strategic Audit and follow the specified phases and output order to generate the tailored documents.
Original prompt (before our improvements)
## Resume Customization Prompt – STRATEGIC INTEGRITY v3.26 (GENERIC) - **Author:** Scott M. - **Version:** v3.26 (Generic Master) - **Last Updated:** 2026-03-16 - **Changelog:** - v3.26: Integrated De-Risking Audit, God Mode Writing Rules, and Insider Cover Letter logic. - v3.25: Initial generic release. --- ## QUICK START GUIDE 1. **Fill Variables:** Replace the brackets in the "USER VARIABLES" section. 2. **Attach File:** Upload your master Skills Summary or Resume. 3. **Paste Job Posting:** Put the target Job Description (JD) into the chat with this prompt. 4. **Execute:** AI performs the Strategic Audit first, then generates the tailored docs. --- ## USER VARIABLES (REQUIRED) - **NAME & CREDENTIALS:** [Insert Name, e.g., Jane Doe, CISSP] - **TARGET ROLE:** [Insert Job Title] - **SOURCE FILE:** [Name of your uploaded file] - **SOURCE URL:** [Link to portfolio/GitHub if applicable] ### PHASE 1: THE DE-RISKING AUDIT Before writing, perform a "Strategic Audit" in plain text: 1. **The Real Problem:** What literal technical or business pain is killing their speed or security? 2. **The Risk Profile:** Why would they hesitate to hire for this? Pinpoint the fear and how to crush it. 3. **The Language Mirror:** Identify 3-5 high-value technical terms from the JD to use exclusively. 4. **The 99% Trap:** What will average applicants emphasize? Contrast the candidate’s "battle-tested" history against that. 5. **The Sinker:** Find the one specific metric/achievement in the source file that solves their "Real Problem." ### PHASE 2: MANDATORY OUTPUT ORDER Process every section in this order. If no changes are needed, state "No Changes Required." 1. **Header:** [NAME & CREDENTIALS]. Use ( • ) for phone • email • LinkedIn. 2. **Professional Summary:** Humanized "I" voice. Use the company’s "Power Words" to look like an internal hire. 3. **AREAS OF EXPERTISE:** Single paragraph block; items separated by bold middle dot ( **·** ). 4. **Key Accomplishments:** Exactly 3 bullets. **The 1:1 Metric Rule:** Every bullet MUST have a number ($ or %). 5. **Professional Experience:** Job/Company/Dates as text; Bullets in a single code block. 6. **Early Career / Additional History.** 7. **Education.** 8. **TECHNICAL COMPETENCIES:** Categorized vertical list of tools/platforms. 9. **Certifications / Licenses.** ### PHASE 3: THE GOD MODE WRITING RULES - **The "Before" Test:** Every bullet must prove you've already solved the problem. No "learning" vibes. - **The Active Kill-Switch:** Ban passive words (managed, responsible for). Use: Orchestrated, Overhauled, Captured. - **Eye-Tracking:** **Bold the win**, not the task. The eye should jump straight to the result. - **Before & Revised:** Show **Before:** (plain text) then ```Revised``` (code block) for every updated section. - **Formatting:** Strict use of middle dot ( · ) bullets. No blank lines between list items. ### PHASE 4: THE INSIDER COVER LETTER - **The Direct Lead:** No "I am writing to apply." Start with: "I have done this exact work at [Company]" or a direct claim. - **The Proof Paragraph:** One specific win, massive technical proof, zero clichés (no "passionate" or "motivated"). - **The 250-Word Cap:** Max 3 paragraphs. Keep it tight. - **Signature:** [Full Name] only. ### WRAP-UP - **Recruiter Snapshot:** Fit (%) | Top 3 Matches | Honest Gaps. - **Revision Changelog:** List sections processed and summarize adjustments.