
Coding Prefs
- 171 installs
- 27.3k repo stars
- Updated August 5, 2026
- langchain-ai/deepagents
Configure and enforce coding preferences for LangChain Deep Agents so generated patches match team style, frameworks, and repository conventions.
About
coding-prefs from langchain-ai/deepagents teaches Claude how to set and apply coding preferences for Deep Agents, aligning autonomous edits with your stack, lint rules, and team conventions.
- Deep Agents integration
- Team style enforcement
- Framework-aware defaults
- Reduces review churn
- Repo-specific conventions
Coding Prefs by the numbers
- 171 all-time installs (skills.sh)
- +8 installs in the week ending Aug 2, 2026 (Skillselion tracking)
- Ranked #3,124 of 16,546 AI & Agent Building skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/langchain-ai/deepagents --skill coding-prefsAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 171 |
|---|---|
| repo stars | ★ 27.3k |
| Last updated | August 5, 2026 |
| Repository | langchain-ai/deepagents ↗ |
What it does
Configure and enforce coding preferences for LangChain Deep Agents so generated patches match team style, frameworks, and repository conventions.
Files
Coding Preferences Skill
Use this skill to keep /memory/coding-prefs.md in sync with how this specific user wants you to work. This file is user-scoped, so each user has their own copy — anything you write here only affects future conversations with the same user.
When to Read
- Before picking a code style, test framework, or commit message format
- Before deciding whether to add comments, type hints, or docstrings
- Before refactoring beyond what was asked
When to Write
Append a new entry whenever the user gives feedback that should apply to future work:
- "Don't add docstrings unless I ask" → save it
- "I prefer pytest over unittest" → save it
- "Stop summarizing what you did at the end" → save it
Each entry should be one line: the rule, then a brief reason if the user gave one.
How to Write
Read the file first (it may not exist yet), then append. Don't overwrite — preferences accumulate over time. If a new preference contradicts an existing one, replace the old line and note the change.