简历生成器
- 作者仓库星标 38,186
- 作者仓库 reactive-resume
- 领域
- 人工智能
- 作者声明的智能体
- 未找到明确声明;不据此推断已兼容或已测试
- 静态检查
- 88 / 100 · 启发式扫描,不代表运行安全
- 运行环境证据
- 未执行;当前没有隔离运行测试证据
- 作者 / 版本 / 许可证
- @amruthpillai · 未声明许可证
- 上下文用量评级
- 低消耗
- 接入复杂程度
- 即装即用
- 是否需要外部接口密钥
- 不需要
- 兼容的系统
- 未声明(默认跨平台)
- 运行环境要求
- 未检出明确要求
- 检测到的文件与系统行为
-
- 只读
- 允许写入 / 修改
- 网络行为
- 仅限本地
- 安装命令数
- 无(仅作为资料)
需要注意: 未声明工具权限范围;实际权限由运行环境决定。
{
"picture": { "hidden": true, "url": "", "size": 80, "rotation": 0, "aspectRatio": 1, "borderRadius": 0, "borderColor": "rgba(0, 0, 0, 0.5)", "borderWidth": 0, "shadowColor": "rgba(0, 0, 0, 0.5)", "shadowWidth": 0 },
"basics": { "name": "", "headline": "", "email": "", "phone": "", "location": "", "website": { "url": "", "label": "" }, "customFields": [] },
"summary": { "title": "Summary", "columns": 1, "hidden": false, "content": "" },
"sections": { ... },
"customSections": [],
"metadata": { "template": "onyx", "layout": { ... }, ... }
}
第 1 步:收集基本信息
首先询问基本详细信息,除非用户已经提供: 全名 专业标题/职位 电子邮件地址 电话号码
第 2 步:收集部分内容
对于用户想要包含的每个部分,收集具体的详细信息。切勿发明日期、公司名称或成就。经验:公司、职位、地点、时期(例如“2020 年 1 月至今”)、职责/成就描述 教育背景:学校、学位、学习领域、年级(可选)、地点、时期 技能:姓名、熟练程度(初级/中级/高级/专家)、关键字
步骤 3:配置布局和设计
询问偏好: 模板偏好(15 种可用:azurill、bronzor、chikorita、ditto、ditgar、gengar、glalie、kakuna、lapras、leafish、meowth、onyx、pikachu、rhyhorn、scizor) 页面格式:A4 或 Letter 要包含哪些部分及其顺序
第 4 步:生成有效的 JSON
输出必须符合反应式简历架构。有关完整的模式结构,请参阅references/schema.md。关键要求: 所有项目 `id` 字段必须是有效的 UUID 描述字段接受 HTML 格式的字符串 网站字段需要 `url` 和 `label` 属性
# Resume Builder for Reactive Resume
Build professional resumes through conversational AI for [Reactive Resume](https://rxresu.me), a free and open-source resume builder.
## Core Principles
1. **Never hallucinate** - Only include information explicitly provided by the user
2. **Ask questions** - When information is missing or unclear, ask before assuming
3. **Be concise** - Use clear, direct language; avoid filler words
4. **Validate output** - Ensure all generated JSON conforms to the schema
## Workflow
### Step 1: Gather Basic Information
Ask for essential details first, unless the user has already provided them:
- Full name
- Professional headline/title
- Email address
- Phone number
- Location (city, state/country)
- Website (optional)
### Step 2: Collect Section Content
For each section the user wants to include, gather specific details. Never invent dates, company names, or achievements.
**Experience**: company, position, location, period (e.g., "Jan 2020 - Present"), description of responsibilities/achievements
**Education**: school, degree, area of study, grade (optional), location, period
**Skills**: name, proficiency level (Beginner/Intermediate/Advanced/Expert), keywords
**Projects**: name, period, website (optional), description
**Other sections**: languages, certifications, awards, publications, volunteer work, interests, references
### Step 3: Configure Layout and Design
Ask about preferences:
- Template preference (15 available: azurill, bronzor, chikorita, ditto, ditgar, gengar, glalie, kakuna, lapras, leafish, meowth, onyx, pikachu, rhyhorn, scizor)
- Page format: A4 or Letter
- Which sections to include and their order
### Step 4: Generate Valid JSON
Output must conform to the Reactive Resume schema. See [references/schema.md](references/schema.md) for the complete schema structure.
Key requirements:
- All item `id` fields must be valid UUIDs
- Description fields accept HTML-formatted strings
- Website fields require both `url` and `label` properties
- Colors use `rgba(r, g, b, a)` format
- Fonts must be available on Google Fonts
## Resume Writing Tips
Share these tips when helping users craft their resume content:
### Content Guidelines
- **Lead with impact**: Start bullet points with action verbs (Led, Developed, Increased, Managed)
- **Quantify achievements**: Use numbers when possible ("Increased sales by 25%", "Managed team of 8")
- **Tailor to the role**: Emphasize relevant experience for the target position
- **Be specific**: Replace vague terms with concrete examples
- **Keep it concise**: 1-2 pages maximum for most professionals
### Section Order Recommendations
For most professionals:
1. Summary (if experienced)
2. Experience
3. Education
4. Skills
5. Projects (if relevant)
6. Certifications/Awards
For students/recent graduates:
1. Education
2. Projects
3. Skills
4. Experience (if any)
5. Activities/Volunteer
### Common Mistakes to Avoid
- Including personal pronouns ("I", "my")
- Using passive voice
- Listing job duties instead of achievements
- Including irrelevant personal information
- Inconsistent date formatting
## Output Format
When generating the resume, output a complete JSON object that conforms to the Reactive Resume schema. The user can then import this JSON directly into Reactive Resume at https://rxresu.me.
Example minimal structure:
```json
{
"picture": { "hidden": true, "url": "", "size": 80, "rotation": 0, "aspectRatio": 1, "borderRadius": 0, "borderColor": "rgba(0, 0, 0, 0.5)", "borderWidth": 0, "shadowColor": "rgba(0, 0, 0, 0.5)", "shadowWidth": 0 },
"basics": { "name": "", "headline": "", "email": "", "phone": "", "location": "", "website": { "url": "", "label": "" }, "customFields": [] },
"summary": { "title": "Summary", "columns": 1, "hidden": false, "content": "" },
"sections": { ... },
"customSections": [],
"metadata": { "template": "onyx", "layout": { ... }, ... }
}
```
For the complete schema, see [references/schema.md](references/schema.md).
## Asking Good Questions
When information is missing, ask specific questions:
- "What was your job title at [Company]?"
- "What dates did you work there? (e.g., Jan 2020 - Dec 2022)"
- "What were your main responsibilities or achievements in this role?"
- "Do you have a specific target role or industry in mind?"
Avoid compound questions. Ask one thing at a time for clarity.
章节与文件索引
按说明文件中的顺序排列。
核心原则
第 1 步:收集基本信息
第 2 步:收集部分内容
步骤 3:配置布局和设计
第 4 步:生成有效的 JSON
文件/命令 -> url · label · rgba(r, g, b, a) · headline/title · state/country · responsibilities/achievements · Beginner/Intermediate/Advanced/Expert · references/schema.md
内容校验值 -> 3469fa617542
当前原文的自动摘译,尚未人工审校。
核心原则
切勿产生幻觉 - 仅包含用户明确提供的信息 提出问题 - 当信息缺失或不清楚时,在假设之前询问 简洁 - 使用清晰、直接的语言;避免填充词验证输出 - 确保所有生成的 JSON 符合架构