What problem does this solve?
Users who skip python setup.py profile (or who want to hand-edit later) need to know the exact JSON schema for data/profile.json and data/master-resume.json. Right now they have to read Pydantic models in backend/models/schemas.py.
What to do
Add two example files:
agent/data/profile.example.json — a complete, fictional sample profile with every field populated
agent/data/master-resume.example.json — same, with a fake person's experience history
Use a clearly fake identity (e.g. "Jane Doe", "jane@example.com", "Acme University", "BigCo Inc.") so nobody mistakes it for a real person.
Proposed solution
Acceptance
- Both files exist and parse as valid JSON
- All fields the wizard writes are present
- README / QUICKSTART has a one-line note: "To skip the wizard, copy
data/profile.example.json to data/profile.json and edit."
Alternatives you considered
No response
Are you up for contributing this?
What problem does this solve?
Users who skip
python setup.py profile(or who want to hand-edit later) need to know the exact JSON schema fordata/profile.jsonanddata/master-resume.json. Right now they have to read Pydantic models inbackend/models/schemas.py.What to do
Add two example files:
agent/data/profile.example.json— a complete, fictional sample profile with every field populatedagent/data/master-resume.example.json— same, with a fake person's experience historyUse a clearly fake identity (e.g. "Jane Doe", "jane@example.com", "Acme University", "BigCo Inc.") so nobody mistakes it for a real person.
Proposed solution
Acceptance
data/profile.example.jsontodata/profile.jsonand edit."Alternatives you considered
No response
Are you up for contributing this?