BUG_REPORTS
Report reproducible bugs through the GitHub issue tracker. Before opening an issue, search existing reports and confirm the behavior with the latest CLI release. Include the exact command, CLI version, operating system, package manager, selected stack, error output, and the smallest reproduction that demonstrates the problem.
FEATURE_REQUESTS
Use GitHub issues for feature ideas and integration proposals. Explain the user problem, the desired workflow, affected stack choices, and why the change belongs in the core generator. Major features should be discussed before implementation so maintainers and contributors can agree on scope and compatibility expectations.
Public discussion keeps decisions searchable for future contributors and coding agents.
GENERAL_CONTACT
For project questions that do not belong in a public issue, email amanvarshney.work@gmail.com. Please use a descriptive subject and avoid sending secrets, access tokens, private project files, or unnecessary personal information.
Documentation questions are usually resolved fastest by linking the relevant page and describing what information was missing or unclear.
SECURITY_REPORTS
If a report describes a vulnerability that could put users at risk, do not publish exploit details or credentials in a public issue. Email the project contact with “Security” in the subject, affected versions, impact, reproduction steps, and any suggested mitigation. Allow time for investigation before public disclosure.
Never include real production secrets in a report. Replace them with clearly marked test values and revoke any credential that may already have been exposed.