Common Lisp Coding Practices
Application skill for Common Lisp style learning (from the archived awesome-guidelines style capsules). For Emacs Lisp, use emacs-lisp-coding-practices when ingested.
Core Principle
Common Lisp quality is idiomatic names + explicit packages + documented CLOS, small libraries, exported APIs only, SLIME-consistent layout.
When to Use / NOT
- Common Lisp libraries, ASDF systems, SBCL/CCL deployments.
- Setting up SLIME indent, SBCL warnings, ASDF test-op in CI.
NOT when:
- Clojure/Scheme/Racket, use language-specific practice skills.
- Generated system stubs only, validate generator.
Workflow
- Format & files, indent, columns, headers (
lisp-style-formatting-files.md). - Naming, lisp-case, *, +, predicates (
lisp-style-naming-symbols.md). - Packages, defpackage, ASDF (
lisp-style-packages-systems.md). - CLOS & control, classes, when/unless (
lisp-style-clos-control.md). - Verify, load/test system; SBCL
(declaim (optimize ...))policy; review exports.
Red Flags
- camelCase or snake_case symbols
:useheavy packages (beyond:cl)other-package::internalin production- Missing docstrings on exported API
slot-valuein application logic- Unrelated generic function overloads
- Commented-out code blocks
- Monolithic system with no library boundaries
- Abbreviated symbol names
Verification
asdf:test-system/ project test script- SBCL compile with project warning policy
- SLIME/common-lisp-indent style check
- Capsule checklist on package export list
References
awesome-guidelines/references/lisp-style-learning-note.mdawesome-guidelines/references/lisp-style-formatting-files.mdawesome-guidelines/references/lisp-style-naming-symbols.mdawesome-guidelines/references/lisp-style-packages-systems.mdawesome-guidelines/references/lisp-style-clos-control.md