Problem
.github/ has no ISSUE_TEMPLATE/ directory — every one of this repo's 150+ issues (opened by maintainers, automated audits, and external contributors alike) has been filed against GitHub's completely blank default issue form, with no structured prompts for labels, reproduction steps, or which area of the app (src/app/, src/components/, src/lib/, etc.) is affected.
Impact
For a repo that clearly relies on a high volume of externally-filed issues (visible from the sheer number of good first issue/help wanted-labeled issues intended for outside contributors to pick up), a blank issue form means bug reports and feature requests vary wildly in quality and completeness depending on how thorough the individual filer happens to be, and nothing nudges a filer toward specifying the label(s) this repo's own convention clearly expects (every closed/open issue in this repo carries 2+ labels — type plus difficulty — a pattern a structured template could bake in as guided fields).
Suggested fix
Add .github/ISSUE_TEMPLATE/bug_report.yml and .github/ISSUE_TEMPLATE/feature_request.yml (GitHub's YAML issue-form format) with fields for affected file/route, reproduction steps or motivation, and expected labels — matching the level of structure this repo's own issue bodies already informally follow.
Problem
.github/has noISSUE_TEMPLATE/directory — every one of this repo's 150+ issues (opened by maintainers, automated audits, and external contributors alike) has been filed against GitHub's completely blank default issue form, with no structured prompts for labels, reproduction steps, or which area of the app (src/app/,src/components/,src/lib/, etc.) is affected.Impact
For a repo that clearly relies on a high volume of externally-filed issues (visible from the sheer number of
good first issue/help wanted-labeled issues intended for outside contributors to pick up), a blank issue form means bug reports and feature requests vary wildly in quality and completeness depending on how thorough the individual filer happens to be, and nothing nudges a filer toward specifying the label(s) this repo's own convention clearly expects (every closed/open issue in this repo carries 2+ labels — type plus difficulty — a pattern a structured template could bake in as guided fields).Suggested fix
Add
.github/ISSUE_TEMPLATE/bug_report.ymland.github/ISSUE_TEMPLATE/feature_request.yml(GitHub's YAML issue-form format) with fields for affected file/route, reproduction steps or motivation, and expected labels — matching the level of structure this repo's own issue bodies already informally follow.