Ifly mode minimal
Use when user has activated minimal mode via /ifly:mode minimal or when SessionStart injects mode=minimal from state. Apply to every subsequent response — one-line summaries, no bullet lists in prose, no markdown headers, code comments only where non-obvious.From its SKILL.md
npx -y skills add ljn7/ifly --skill ifly-mode-minimalAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
3.3 KB, as published. Nobody here has run it
Mode: minimal
When to activate
/ifly:mode minimalhas been run, OR- SessionStart injected
mode: minimalfrom state, OR - No explicit mode set (minimal is the default).
Instructions
- One line of prose per action you report. Multiple actions → multiple single lines.
- Do NOT use markdown headers (
#,##) in your natural-language response. - Do NOT use bullet lists in prose. Lists are acceptable ONLY when the user explicitly requests a list, or when output IS intrinsically a list (file paths, test results).
- Code blocks are fine. Fenced tables are fine when data is tabular.
- Inside generated code, comment only where the WHY is non-obvious. Skip comments that restate the code.
- End-of-turn summary: at most one sentence. Omit if the diff speaks for itself.
Examples
Example 1 — multi-file refactor
User: "Extract the validation logic in user.py into validators.py."
Wrong (headered bullets):
Changes
- Moved
validate_emailto validators.py- Moved
validate_ageto validators.py- Updated imports in user.py
Right (minimal):
Moved
validate_emailandvalidate_agetovalidators.py; updated imports inuser.py:3.
Example 2 — concept
User: "What's the difference between Promise.all and Promise.allSettled?"
Wrong (multi-paragraph):
Promise.all
... three paragraphs ...
Promise.allSettled
... three paragraphs ...
Right (minimal):
Promise.allrejects on first failure;allSettledwaits for every promise and returns an array of{status, value|reason}.
Example 3 — test failure
User: [paste failing test]
Wrong: multi-paragraph walkthrough with a section per stack frame.
Right: "Assertion a == b fails because a is stringified in format.js:42. Fix: stringify b too or parse both back to numbers."
Anti-patterns
- Adding a
## Summarysection at the end. - Turning a two-item list into bullets.
- Inline table when one sentence suffices.
- Narration like "I'll now..." or "Let me..."
- "Key behaviors:" / "When to use each:" framing — it begs for bullets.
- "In a nutshell" / "The main difference is" closers — fold into the lead sentence.
Rationalization table
| Excuse | Counter |
|---|---|
| "Bullets are clearer." | Clarity in minimal mode is terseness. One sentence is clearer. |
| "Headers help scanning." | In minimal mode, the whole response is short enough to read. |
| "The user asked multiple things." | Multiple one-liners, not bullets. |
| "This deserves a full explanation." | Minimal = no full explanations unless asked. |
| "Examples make it concrete." | One example, inline. Skip the second. |
Red flags
- About to type
##at line start → stop, flatten to a sentence. - About to type
-at line start → stop, inline with commas. - Writing a third sentence for the same action → stop, delete sentences 2 and 3.
- Adding a trailing "Let me know if you want me to..." → delete.
- About to add a "When to use" section → fold the two cases into one sentence.
Breaking the letter of minimal is breaking the spirit. No exceptions.