Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Coding style memory that adapts to your preferences, conventions, and patterns for consistent coding.
Coding style memory that adapts to your preferences, conventions, and patterns for consistent coding.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
User has coding style preferences, stack decisions, or patterns they want remembered. Agent learns ONLY from explicit corrections and confirmations, never from observation.
Memory lives in ~/coding/ with tiered structure. See memory-template.md for setup. ~/coding/ โโโ memory.md # Active preferences (โค100 lines) โโโ history.md # Archived old preferences
TopicFileCategories of preferencesdimensions.mdWhen to add preferencescriteria.mdMemory templatesmemory-template.md
All data stored in ~/coding/. Create on first use: mkdir -p ~/coding
This skill ONLY: Learns from explicit user corrections ("I prefer X over Y") Stores preferences in local files (~/coding/) Applies stored preferences to code output This skill NEVER: Reads project files to infer preferences Observes coding patterns without consent Makes network requests Reads files outside ~/coding/ Modifies its own SKILL.md
User corrects output โ ask: "Should I remember this preference?" User confirms โ add to ~/coding/memory.md Never infer from silence or observation
No preference is stored without explicit user confirmation: "Actually, I prefer X" โ "Should I remember: prefer X?" User says yes โ store User says no โ don't store, don't ask again
Keep each entry 5 words max: python: prefer 3.11+ naming: snake_case for files tests: colocated, not separate folder
Group by type (see dimensions.md): Stack โ frameworks, databases, tools Style โ naming, formatting, comments Structure โ folders, tests, configs Never โ explicitly rejected patterns
memory.md โค100 lines When full โ archive old patterns to history.md Merge similar entries: "no Prettier" + "no ESLint" โ "minimal tooling"
Load ~/coding/memory.md if exists Apply stored preferences to responses If no file exists, start with no assumptions
User can ask: "Show my coding preferences" โ display memory.md "Forget X" โ remove from memory "What do you know about my Python style?" โ show relevant entries
Adding preferences without confirmation โ user loses trust Inferring from project structure โ privacy violation Exceeding 100 lines โ context bloat Vague entries ("good code") โ useless, be specific
Data that stays local: All preferences stored in ~/coding/ No telemetry or analytics This skill does NOT: Send data externally Access files outside ~/coding/ Observe without explicit user input
If useful: clawhub star coding Stay updated: clawhub sync
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.