peterish8 Google Common Lisp Style (Quick Reference)
Source: https://google.github.io/styleguide/lispguide.xml
When to load the detailed skill
Read google-common-lisp-style-detailed when you need:
- Section-by-section rules, examples, or edge cases
- PR review with non-trivial style questions
- Resolving conflicts between local habits and Google style
The detailed skill is linked here so agents can load it automatically alongside this quick reference.
Core rules
- Follow Google Common Lisp style for packages, naming, and formatting.
- Use packages to partition namespaces;
:useonly common packages like:cl. - Naming:
*global*,+constant+,foo-bar-bazfor functions/variables. - Keep lines ≤ 80 columns; indent with spaces reflecting nesting.
- Document public APIs with docstrings.
Quick checklist
- Match Google Common Lisp naming and formatting conventions
- Keep code readable; prefer consistency within the file and package
- Run language-appropriate linters/formatters when available
- Document non-obvious behavior with brief, accurate comments
- Defer to the official guide when this skill is silent