Contributing & support

Feature requests

Have an idea for a new preset, rule, skill, or IDE adapter?

• Open a GitHub Issue with:
  • Problem — what friction you hit today
  • Proposal — what you want generated or changed
  • Example — stack (framework, ORM, IDE) and sample output if possible

Maintainers can triage and align with the project scope (opinionated Node.js backend AI instructions).

Bug reports

• Use Issues with:
  • Node version (node -v)
  • Package version (npm ls backend-ai-starter-recipes or commit SHA if from git)
  • Command you ran (e.g. full npx … --preset … --output …)
  • Expected vs actual (error text, missing files, wrong adapter output)
  • Minimal repro (empty folder + preset name is ideal)

Contributing code

Summary of CONTRIBUTING.md in the repo:

Topic	Guideline
Branches	feature/… or fix/… from main
PRs	Open against main; keep changes focused
Before PR	npm run build passes; update user-facing docs if behavior changes
Commits	Clear, imperative messages (Conventional Commits optional)

Maintainers: protect main, require CI, and follow release workflow described in the same file.

Security

Report vulnerabilities via GitHub Security Advisories or read SECURITY.md.

License

MIT — see LICENSE.

---

← Back to home · Guide: The problem