Optimize the content quality of programmer Markdown resumes, improving technical descriptions, quantifying results, and highlighting strengths to enhance resume competitiveness.
Workflow
1. Read Resume
Read the resume file or content provided by the user.
2. Analyze Current State
Analyze the current state of the resume:
- Identify weak descriptions (lack of quantification, use of passive voice, piling up tech stacks)
- Check the depth and persuasiveness of project experience
- Evaluate the completeness of skill descriptions
- Identify missing key information
3. Optimize Content
Optimize content according to best practices:
Project experience optimization:
- Apply the STAR method (Situation, Task, Action, Result)
- Add quantified metrics (performance improvement, user growth, data volume processed)
- Use strong technical verbs (see action-verbs.md)
- Highlight technical challenges and solutions
- Demonstrate architecture design and technical decision-making abilities
Skill description optimization:
- Present skills grouped by technical domain (frontend, backend, engineering, etc.)
- Add specific features and use cases for core technologies
- Ensure alignment with the target role's tech stack (refer to keywords.md)
- Remove outdated or irrelevant technologies
Language optimization:
- Replace weak verbs ("responsible for", "participated in") with strong verbs ("designed", "implemented", "optimized")
- Ensure every project has quantified results
- Use active voice and present perfect tense
- Keep descriptions concise and powerful
4. Validate
Check the optimized resume:
- Every project has quantified data
- Starts with strong verbs
- Tech stack descriptions are complete and clearly grouped
- No grammatical errors
- Key technical terms are aligned with industry standards
- Overall length is appropriate (1-2 pages)
5. Output
Output the complete optimized Markdown resume.
Key Principles
Quantify Everything
Use specific numbers to demonstrate impact:
- Performance improvement: "Response time reduced from 800ms to 50ms, a 94% decrease"
- Business value: "Daily PV 500,000, GMV exceeded 10 million"
- Technical metrics: "System availability reached 99.9%, supporting 100,000+ DAU"
Show Technical Depth
Do not just list the tech stack; show how it was used and what problems it solved:
- ❌ "Used React to develop the frontend"
- ✅ "Used React 18 Hooks + TypeScript to refactor core pages, reducing first-screen load time by 40% and increasing the Lighthouse performance score from 65 to 92"
Use Strong Action Verbs
Avoid passive and weak verbs:
- ❌ "responsible for, participated in, assisted, helped"
- ✅ "designed, implemented, optimized, refactored, built, led"
See references/action-verbs.md for the complete verb library.
Align with Target Role
Ensure the tech stack matches the target role:
- Read the job description (JD) and extract key technical terms
- Cover more than 80% of the core technical requirements in the resume
- Refer to references/keywords.md to learn keywords for different tech stacks
Resources
references/best-practices.md
Detailed best practices for resume optimization, including:
- Core optimization principles (quantified results, STAR method, technical depth)
- Project experience optimization strategies (weakened vs. optimized examples)
- Common issue fixes
- Structural suggestions and checklist
references/action-verbs.md
A library of strong action verbs for technical fields, organized by category:
- Development and implementation, optimization and improvement, analysis and problem-solving
- Architecture and design, leadership and collaboration, testing and quality
- Innovation and research, automation and tooling, documentation and dissemination
references/keywords.md
Keyword libraries for different tech stacks, covering:
- Front-end development (frameworks, languages, state management, build tools, testing)
- Back-end development (Node.js ecosystem, other language frameworks, API design)
- Databases (relational, NoSQL, ORM, optimization)
- DevOps & cloud services (containerization, CI/CD, monitoring)
- Architecture and patterns, message queues, engineering practices
assets/template-fullstack.md
An excellent full-stack engineer resume template, showcasing:
- A complete, grouped presentation of the tech stack
- Quantified project results descriptions
- A combination of technical depth and business value
- A clear information hierarchy
assets/template-frontend.md
An excellent front-end engineer resume template, showcasing:
- A detailed presentation of the front-end tech stack
- Performance optimization and engineering practices
- Specific technical metrics and results
- Open-source contributions and technical blogs
Usage Examples
Example 1: Basic Optimization
User: 帮我优化这份简历
Assistant:
[读取简历]
[分析并识别改进点]
[应用最佳实践优化内容]
[输出优化后的完整简历]
Example 2: Targeted Optimization
User: 我的简历缺少量化数据，帮我改进一下
Assistant:
[读取简历]
[重点为每个项目添加量化指标]
- 性能提升百分比
- 用户量、访问量
- 业务指标
[输出优化后的简历]
Example 3: Tech Stack Alignment
User: 我要应聘 React 高级工程师，帮我优化简历以匹配这个岗位
Assistant:
[读取简历和 JD（如有）]
[参考 keywords.md 确保 React 技术栈完整]
[突出 React 相关项目经验]
[优化技能描述，展示 React 深度]
[输出优化后的简历]