Core coding standards and best practices for code review and generation. Provides guiding principles (DRY, KISS, YAGNI, SOLID), priority frameworks for feedback, tooling baselines, dependency management guidelines, and response formats. Use when reviewing code, generating code, asking about coding standards, or when the user needs general engineering guidance that applies across all languages.
Organize feedback by impact:
| Priority | Description | Examples | |----------|-------------|----------| | Critical | Security vulnerabilities, bugs that break functionality, data loss risks | Injection flaws, hardcoded secrets, unhandled exceptions | | Recommended | Performance issues, maintainability problems, scalability concerns | N+1 queries, tight coupling, missing error handling | | Optional | Style improvements, future-proofing, minor optimizations | Naming tweaks, code comments, minor refactors |
| Language | Linting/Formatting | Security |
|----------|-------------------|----------|
| Python | ruff + black, pylint (≥9.0) | pip-audit |
| Bash | shfmt + shellcheck | - |
| Go | gofmt + golangci-lint | govulncheck |
| JS/TS | eslint --max-warnings=0 | npm audit |
| Terraform | terraform fmt + tflint | - |
| All | ggshield + gitleaks | Dependency scanning on PRs |
acme.com for examples (never example.com)ACME or AcmeEvaluation Areas: Security, Error Handling, Testing, Observability, Resource Management, Concurrency, Performance
For detailed review patterns and formats, see references/code-review.md.
What to Include: Error handling, logging, type hints, externalized configuration, docstrings
What NOT to Include: Over-engineered abstractions, premature optimization, extensive test suites, complex frameworks when stdlib suffices
For detailed generation patterns, see references/code-generation.md.
Adding a dependency is a long-term commitment. Prefer stdlib or existing dependencies.
Vetting criteria for new dependencies:
Before delivering code or feedback:
For commit message standards, branch naming, PR hygiene, and repository scaffolding, see references/git-workflow.md.
| Language | Key Practices |
|----------|--------------|
| Python | Type hints, PEP 8, context managers, prefer stdlib |
| Go | Handle all errors, use defer, small interfaces |
| JS/TS | async/await, destructuring, strict mode |
| Bash | set -euo pipefail, quote variables, use functions |
| Docker | Multi-stage builds, non-root user, pinned versions |
"Perfection is achieved not when there is nothing more to add, but when there is nothing left to take away." — Antoine de Saint-Exupéry
Search for places (restaurants, cafes, etc.) via Google Places API proxy on localhost.
Interact with GitHub using the `gh` CLI. Use `gh issue`, `gh pr`, `gh run`, and `gh api` for issues, PRs, CI runs, and advanced queries.
Create or update AgentSkills. Use when designing, structuring, or packaging skills with scripts, references, and assets.
Start voice calls via the OpenClaw voice-call plugin.
Notion API for creating and managing pages, databases, and blocks.
Gemini CLI for one-shot Q&A, summaries, and generation.
Category:developer