coding-prefs

To keep coding preferences consistent across sessions, this skill synchronizes your style decisions to a persistent memory file. It reads existing rules before making style choices and appends new durable feedback to maintain a unified coding history.

Persistent memory for code style works by reading and writing rules to a local markdown file. Whenever you provide durable feedback during coding or reviews, the skill appends these preferences to resolve conflicts and guide future tasks.

Yes, you can use coding preferences memory for linting and testing configurations. The skill applies synchronized style rules across coding tasks, code reviews, and interactive sessions where linting, testing, or documentation decisions matter.

The best way to maintain a user-scoped history of coding style rules is using a persistent markdown memory store. This approach resolves conflicts by updating entries and ensures future interactions reflect your known style preferences.

To append new durable coding feedback without losing previous rules, the skill reads existing preferences from the memory file and adds new entries. It maintains conflict resolution by updating the user-scoped history as style decisions evolve.