typescript-engineering
TypeScript Engineering
Comprehensive guidelines for writing production-quality TypeScript based on Google's TypeScript Style Guide.
Naming Conventions
| Type | Convention | Example |
|---|---|---|
| Classes, Interfaces, Types, Enums | UpperCamelCase |
UserService, HttpClient |
| Variables, Parameters, Functions | lowerCamelCase |
userName, processData |
| Global Constants, Enum Values | CONSTANT_CASE |
MAX_RETRIES, Status.ACTIVE |
| Type Parameters | Single letter or UpperCamelCase |
T, ResponseType |
Naming Principles
- Descriptive names, avoid ambiguous abbreviations
- Treat acronyms as words:
loadHttpUrlnotloadHTTPURL - No prefixes like
opt_for optional parameters - No trailing underscores for private properties
- Single-letter variables only when scope is <10 lines
More from gonzaloserrano/dotfiles
shell-engineering
Comprehensive shell/bash engineering guidelines based on Google's Shell Style Guide. This skill should be used when writing shell scripts, reviewing bash code, or answering questions about shell scripting best practices. Applies to .sh files, bash scripts, and any shell programming tasks.
12python-engineering
Comprehensive Python engineering guidelines for writing production-quality Python code. This skill should be used when writing Python code, performing Python code reviews, working with Python tools (uv, ruff, mypy, pytest), or answering questions about Python best practices and patterns. Applies to CLI tools, AI agents (langgraph), and general Python development.
12go-engineering
Comprehensive Go engineering guidelines for writing production-quality Go code. This skill should be used when writing Go code, performing Go code reviews, working with Go tools (gopls, golangci-lint, gofmt), or answering questions about Go best practices and patterns. Applies to all Go programming tasks including implementation, refactoring, testing, and debugging.
6go-code-review
Go code review skill synthesized from 4,100+ PR review comments spanning 4.5 years from the tetrateio/tetrate repository. Use this skill when reviewing Go code, providing code review feedback, or understanding common review patterns. Contains patterns for error handling, nesting reduction, thread safety, testing, naming, interface design, and more.
5