Thanks for helping improve Hyperstrate.
- Fork the repository.
- Create a feature branch:
git checkout -b feat/my-change. - Make focused changes with tests where behavior changes.
- Run the relevant checks:
npm run type-check
npm run lint
npm run test:unit -- --run
npm run build-only- Open a pull request and describe the behavior change, tests, and any API/client-generation impact.
- Keep pull requests focused on one topic.
- Include tests for bug fixes and behavior changes.
- Regenerate the API client with
npm run codegenafter server OpenAPI changes. - Do not commit
.env, build outputs, TypeScript build info, API keys, Supabase secrets, or provider credentials. - Open an issue before large UI, routing, or design-system changes so maintainers can discuss the direction.
Follow the existing Vue 3, TypeScript, class-component, Pug, and Tailwind patterns in src/features/.