prompts/prompts/CODE_STYLEGUIDE_JS.md
sneak e97b48eea4
All checks were successful
check / check (push) Successful in 9s
Fix review issues: front matter, headings, consistency, typos
- Move title and last_modified to YAML front matter (all policy docs)
- Make all document sections H1, subsections H2
- Update version rule to reference front matter format
- Fix "our" → "your" typo in Go styleguide
- Fix Python styleguide numbering (2. → 1.)
- Fix README: "flat collection" → accurate description, remove stale TODO
- Remove Makefile items from code styleguides (repo stuff, not code),
  add note linking to Repository Policies
- Change zerolog → slog in Go styleguide
- Fix JS styleguide npm reference: both work, but use make targets
- Drop .json from healthcheck path, add JSON content-type requirement
- Add Author/License to Go HTTP Server Conventions
- Convert hyperlinks to backtick URLs in checklists for consistency
- Add version/front matter to both checklists
2026-02-22 17:15:06 +01:00

865 B

title last_modified
Code Styleguide — JavaScript 2026-02-22
  1. Use const for everything. If you need to reassign, use let. Never use var.

  2. Use yarn for package management, avoid using npm.

  3. Use LTS node versions.

  4. Use prettier for code formatting, with four spaces for indentation.

  5. At a minimum, both yarn run test/yarn run build and npm run test/npm run build should work (complete the appropriate scripts in package.json). However, prefer make test and make build instead — the Makefile is authoritative on how to interact with the repo. See Repository Policies for details.

Author

@sneak <sneak@sneak.berlin>

License

MIT. See LICENSE.