Run pnpm check after every change. It is the same command CI runs, and a failing check names the
command that fixes it (pnpm check:fix repairs everything a machine can).
Follow the shared
developer workflow
for bootstrap, preflight, validation, audits and explicit staging-to-production promotion. Keep
application-specific checks in Turbo validate; change reusable rules upstream.
Use the mandatory github-contribution skill from the lvbt-contributions plugin whenever a user
authorizes creating an issue or pull request. It carries the organization checklist, readable
templates, and the only approved creation helper:
node node_modules/@lasvegasfortransit/cli/plugins/lvbt-contributions/scripts/github-create.mjs issue \
--type bug|feature --title <title> --body-file <file>
node node_modules/@lasvegasfortransit/cli/plugins/lvbt-contributions/scripts/github-create.mjs pr \
--title <title> --body-file <file> --base mainPreview with --dry-run --json and inspect the complete Markdown before creating anything. Do not
call gh issue create, gh pr create, equivalent gh api routes, or connector creation tools
directly.
Subjects are conventional: type(scope): description, at most 72 characters. Scopes are optional
and come only from .lvbt/commit-scopes.txt. Omit the scope when a
change crosses boundaries; never invent one for a feature, file, task, or role.
Lint, format, TypeScript, and test settings extend the @lasvegasfortransit/* packages from
LasVegasForTransit/repository-tooling. Change a shared rule there, not here.