great-resume

/great-resume: Resume Enhancement

Translate what the user has done into expressions that recruiters can easily understand, can follow up on, and that can be supported by evidence. Resume enhancement is role positioning and evidence organization, not fabricating titles, companies, projects, tech stacks, or data.

Workflow

1. First confirm the target role, job description, job-search channel, and the direction the user wants to highlight.
2. Read the existing resume, project descriptions, portfolio, public repositories,/contributor evidence cards, or screenshots provided by the user; when cross-Skill, conflicting, or containing strong claims, follow Claim-Evidence Ledger to create or update the factual baseline; when involving business analysis, strategy operations, business review, or AI productization experience, additionally follow Business Analysis Evidence Workflow to distinguish the nature of results, personal actions, and follow-up-able evidence. When materials are insufficient, first provide a draft based on existing facts and list at most 5 key items to be supplemented.
3. Output 1-3 role positionings, distinguishing a safe version and an aggressive version; the aggressive version must state the evidence that needs to be supplemented.
4. Rewrite experience and project bullet points as "action -> system capability -> business value -> result evidence -> personal boundary".
5. Generate a resume summary, a short Boss Zhipin/WeChat HR opening pitch, and a slightly more complete self-introduction.
6. Audit every strong claim with "original wording - suggested wording - factual evidence - personal boundary - risk/to be confirmed"; when using the ledger, simultaneously update candidate expressions, confirmation status, and expandable interview details.

Expression Boundaries

• Keep formal job titles, companies, dates, and educational background truthful.
• Use strong verbs such as "led", "person in charge", or "Owner" only when decisions, delivery, and results can be explained.
• When there are no reliable numbers, use verifiable qualitative results; do not fabricate percentages, user counts, latency, or rankings.
• For content the user was not directly responsible for, explicitly write "handled by the team" or "to be confirmed"; do not claim it on the user's behalf.
• When the user requests creating HTML/PDF files, replicating the ASu style, or selecting a resume template, switch to /make-resume mode; when the user requests recording applications and offers, switch to /offer mode.
• Upon receiving /contributor PR list, summarize small contributions such as typos, README, and formatting fixes as "cross-project documentation quality governance, developer experience optimization, and open-source collaboration loop"; keep real links, and write unmerged PRs as "in collaboration".

Default Output

Unless the user only wants one of these, deliver in the following order:

1. One-sentence role positioning;
2. Resume top summary;
3. 2-4 project/experience rewrites;
4. Short and complete-but-concise versions of the HR opening pitch;
5. Evidence reinforcement checklist and possible follow-up questions.

When used in combination with /contributor or /make-resume , also deliver the updated Claim-Evidence Ledger; do not force creation when only generating simple short copy.

For BOSS Zhipin or WeChat openers, by default keep it to about 80–160 characters: first state your identity and direction, then mention one real achievement, and finally invite further conversation.