resume builder

AI Community

Skill notes

Core Principles

Never hallucinate - Only include information explicitly provided by the user Ask questions - When information is missing or unclear, ask before assuming Be concise - Use clear, direct language; avoid filler words Validate output - Ensure all generated JSON conforms to the schema

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

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

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 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

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
AI
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@amruthpillai · no license declared
Token usage
Lean
Setup complexity
Plug-and-play
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
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

02
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

03
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

04
Step 4: Generate Valid JSON

Output must conform to the Reactive Resume schema. See 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

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.