From shipshitdev-planning
Automatically detects and documents user preferences, coding rules, and style guidelines expressed in conversations, appending to markdown files after user confirmation.
npx claudepluginhub shipshitdev/libraryThis skill uses the workspace's default tool permissions.
This skill automatically detects when users express preferences, rules, or coding standards during conversations and documents them for future sessions.
Automatically detects and documents user preferences, coding rules, and style guidelines expressed in conversations, appending to markdown files after user confirmation.
Captures lessons from code reviews, error corrections, and convention violations as persistent rules saved to global, project, or category config files. Triggers on /evolve or phrases like 'we should remember this' for recurring patterns.
Promotes patterns from MEMORY.md to CLAUDE.md or .claude/rules/ for permanent enforcement via /si:promote. Supports auto-detection, scoped targets, and rule distillation.
Share bugs, ideas, or general feedback.
This skill automatically detects when users express preferences, rules, or coding standards during conversations and documents them for future sessions.
Automatically activate when the user mentions ANY of these:
When a rule/preference is detected:
I noticed you expressed a preference/rule. Let me capture this.
Parse the user's statement to identify:
Append to .agents/SYSTEM/CAPTURED-RULES.md:
### [YYYY-MM-DD HH:MM] - [Category]: [Short Title]
**User said:**
> "[Exact quote from user]"
**Rule extracted:**
- **Type**: [ALWAYS | NEVER | PREFER | AVOID]
- **Action**: [What to do/not do]
- **Context**: [When this applies]
- **Category**: [coding | naming | imports | patterns | tools | communication | workflow]
**Example:**
```[language]
// Good
[good example]
// Bad
[bad example]
```
Status: PENDING_REVIEW
### 4. Confirm with User
Captured this rule:
Should I add this to the permanent rules? [Yes/No/Modify]
### 5. On Confirmation
- Move to `USER-PREFERENCES.md` under appropriate section
- Or create new section in `RULES.md` if it's a coding standard
- Remove from `CAPTURED-RULES.md` (or mark as PROCESSED)
---
## Rule Categories
### Coding Rules
- Pattern preferences
- Import conventions
- Naming conventions
- File structure
- Component patterns
### Workflow Rules
- Build/test preferences
- Git workflow
- Documentation requirements
- Communication style
### Tool Rules
- CLI preferences
- IDE settings
- Terminal behavior
- Background processes
### Communication Rules
- Response style
- Verbosity preferences
- Explanation depth
- Acknowledgment patterns
---
## Storage Locations
| Rule Type | Storage Location |
|-----------|------------------|
| Personal preferences | `../.agents/SYSTEM/ai/USER-PREFERENCES.md` |
| Coding standards | `.agents/SYSTEM/RULES.md` |
| Critical rules | `../.agents/SYSTEM/critical/CRITICAL-NEVER-DO.md` |
| Pending review | `../.agents/SYSTEM/CAPTURED-RULES.md` |
---
## Auto-Capture File Format
File: `../.agents/SYSTEM/CAPTURED-RULES.md`
```markdown
# Captured Rules - Pending Review
Rules automatically captured from conversations. Review and promote to permanent docs.
---
## Pending Rules
[Auto-captured rules appear here]
---
## Processed Rules
[Rules that have been promoted to permanent docs]
This skill works with:
When user says "clean up rules" or "process captured rules":
CAPTURED-RULES.mdUser: "stop using console.log for debugging, use the logger service"
Claude:
I noticed a new rule. Let me capture it:
Rule: Use logger service instead of console.log for debugging
Category: Coding
Type: NEVER (console.log) / ALWAYS (logger service)
Added to captured rules. Should I promote this to permanent coding rules?
The skill activates on these regex patterns:
# Direct commands
(always|never|don't|stop|from now on|going forward)\s+.+
(prefer|like|want|need)\s+(you to|it to|this to)\s+.+
(the rule is|the standard is|the convention is)\s+.+
# Frustration signals
(why (did|do) you|stop doing|I told you|I already said)\s+.+
(that's (wrong|not right|incorrect)|fix this|change this)\s+.+
# Questions about standards
(what's the (rule|standard|convention) for|how should I|which way is)\s+.+
When this skill is active, you will automatically capture and document any rules, preferences, or standards the user expresses, ensuring nothing is forgotten between sessions.