@magic-resume-kit/* from npm.
Kenmet is MIT-licensed and accepts contributions. PRs that come with reproductions, tests, and a clear why tend to land fast.
What should I do before contributing?
- Search existing issues and the PR list to avoid duplicate work.
- For anything bigger than a small fix or doc tweak, open an issue first and describe the approach. This saves us both from a “thanks but no” on a finished PR.
- New deployment modes, new auth flows, or new local/cloud switches require maintainer signoff before you write code — these are intentionally narrow.
What is the contribution workflow?
- Fork the repo and clone your fork.
- Create a branch off
master:git checkout -b feat/<short-name>. pnpm installat the repo root.- Make your change. Keep the diff scoped — one PR, one concern.
- Run the gates:
pnpm run lint && pnpm run test. The Husky pre-commit hook runs a subset automatically, but the full sweep is cheaper than a red CI. - Open a PR with a description of what and why. Link the issue if there is one.
What rules must contributors follow?
Which workspace should a change go in?
See Architecture for the why behind each of these.
What commit style should I follow?
Conventional commits, present tense. Rungit log --oneline to see the house style:
