ast-grep
Use ast-grep for syntax-aware structural code search, analysis, linting, and safe rewrite planning. Load this when a task asks to find code by shape/AST, refactor repeated code patterns, inspect function/component/import usage structurally, write ast-grep rules, or when ripgrep would be too imprecise.
devlog
Keep DEVLOG.md up to date and use it to resume project context in the user's personal developer-log style. Use when the user asks to update, write, continue, summarize, resume, catch up from, or maintain @DEVLOG.md / DEVLOG.md after or before a work session, or asks to capture what they did, learned, decided, got stuck on, where to continue next, or what happened last time.
guide
>
petar-writing
Drafts, rewrites, and reviews prose in Petar's personal voice while removing generic AI writing patterns. Use whenever writing on Petar's behalf, including blog posts, technical notes, documentation, proposals, PR descriptions, emails, and messages. Do not use for code or routine assistant status updates.
pr-description
>
smart-commit
Analyzes all uncommitted changes (staged and unstaged), groups them into atomic commits by logical purpose, and generates clear conventional commit messages with practical, context-rich bodies. Use when the user asks to "smart commit", "group my commits", "split into atomic commits", "organize my changes into commits", or when there are many uncommitted changes across multiple files that should be separated into well-scoped commits. Don't use for a single, simple commit message request, for push/pull operations, for rebasing or squashing existing commits, or when the user just says "commit this" without asking for grouping or splitting.