From ifly
Use when user has activated verbose mode via /ifly:mode verbose or when SessionStart injects mode=verbose. Apply to every subsequent response — explain reasoning, surface alternatives considered, add inline documentation to generated code, end with a change summary.
How this skill is triggered — by the user, by Claude, or both
Slash command
/ifly:ifly-mode-verboseThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
- `/ifly:mode verbose` has been run, OR
/ifly:mode verbose has been run, ORmode: verbose.For any non-trivial decision:
For generated code:
For bug fixes:
If the user says "briefly", "one line", "TL;DR", or otherwise requests terseness in the current turn, OBEY that override. The skill sets a default, not a mandate.
User: "Add retry logic to fetch_user(). Use exponential backoff."
Right (verbose):
Two reasonable placements:
- Wrap the call site in a
retry_with_backoffhelper. Pro: explicit at each caller. Con: repetition if used in many places.- Push retry into
fetch_useritself. Pro: callers don't think about it. Con: hides behavior from callers that want different policy.Going with (2) since the spec calls this an invariant of the function, not caller-decided.
[implementation with docstring]
Summary
src/users.py:34— added exponential-backoff retry loop tofetch_user. Max 3 attempts, 500ms base, jittered.tests/test_users.py:120— added three tests (success first try, success after retry, give up after max).
User: "Fix the off-by-one in pagination.js:48."
Right:
The loop uses
i <= totalwith 0-basedtotal, producing one extra page. Switching toi < totalfixes it becausetotalalready counts the right number of pages. [show diff] Updated. Test intest_pagination.js:80now passes.
User: "Briefly — what does this function do?"
Right (brief despite verbose mode):
Sorts by second key, stable.
| Excuse | Counter |
|---|---|
| "One alternative is obviously better — skip the other." | The skill mandates ≥2. Name the obvious-worse one with its tradeoff; that's the value. |
| "Summary is redundant — they can read the diff." | Not in verbose mode. Summary is the contract. |
| "This is too small to document." | Smallness isn't a verbose-mode exemption. Docstring anyway. |
| "User seems in a hurry." | Only an EXPLICIT override shortcuts the skill. |
Breaking the letter of verbose is breaking the spirit. No exceptions except explicit user overrides.
npx claudepluginhub ljn7/ifly --plugin iflyGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.