iplaylf2
Publisher on askill
Use when documentation or long-form prose needs structural or clarity-focused revision without intent drift. Goal: documentation is clear, structurally coherent, and faithful to the original intent an...
Use when optional values, fallbacks, defaults, or failure paths materially influence behavior and need explicit governance. Goal: optionality and failure semantics are explicit, and non-happy paths re...
Use when declaration contracts need design or refactoring decisions across signatures, type shapes, schemas, or generic parameters. Goal: declaration contracts are explicit, coherent, and stable at us...
Use only when the user explicitly asks for a git branch name or naming suggestion. Goal: branch names are convention-aligned and communicate type, scope, and intent at a glance.
Use when block order in a single file obscures the public surface or disrupts top-down comprehension. Goal: file structure exposes the public surface first and supporting details in a clear top-down f...
Use only when the user explicitly asks for a git commit message or semantic commit guidance. Goal: commit messages are semantic and communicate the change intent and effect clearly.