Analyze accumulated feedback memories and turn recurring patterns into permanent controls (rules, permissions, hooks) or common-mistakes entries. Use when the user says "improve", "iyileştir", "apply feedback", "kurallaştır", or "turn feedback into rules".
Project onboarding and template setup. Use when the user says onboard, setup, initialize, init, configure this project, or first-time setup. Guides through detecting project mode and stack, configuring CLAUDE.md, permissions, hooks, rules, and architecture docs.
Save session learnings, patterns, and corrections to persistent memory. Use when the user says "save learnings", "save memory", "remember this session", or at the end of a productive session.
Add a new Claude Code control following project conventions. Use when the user says "new rule", "add rule", "create rule", "yeni rule ekle", or wants to enforce behavior consistently. Guides through choosing enforcement surfaces, writing effective rule files, and keeping controls consistent.
Create a new Claude Code skill following project conventions. Use when the user says "new skill", "add skill", "create skill", or "yeni skill ekle". Guides through gathering requirements, writing effective SKILL.md files, and structuring skill directories.
Add a new Claude Code hook — shell script wired into settings.json. Use when the user says "new hook", "add hook", "yeni hook ekle", or wants to automate something that runs on every tool use, session start, or stop.
Add or remove permissions in .claude/settings.json. Use when the user says "add permission", "allow X", "deny X", "block X", "izin ver", "engelle", or "update-permissions".
Update an existing Claude Code rule and keep enforcement surfaces consistent. Use when the user says "update rule", "change rule", "rule güncelle", or "update-rule <name>". This workflow can update rule text, settings.json, and hooks together when needed.