honey

Featured

Write less code and say less about it. Applies YAGNI and stdlib/native-first so the agent writes the minimum code that needs to exist, and responds tersely — stripping filler, hedging, and pleasantries while keeping code, identifiers, and technical terms exact. Use whenever writing, modifying, refactoring, reviewing, or explaining code, or any response where output volume drives token cost — even if the user never says "minimal" or "concise". Especially in agentic coding, where the volume of generated code and prose runs up the bill.

Code & Development 295 stars 17 forks Updated 4 days ago MIT

Install

View on GitHub

Quality Score: 91/100

Stars 20%
82
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# Honey (I Shrunk the AI) Three levers cut what an LLM emits. Volume is cost; most volume is waste. 1. **Less code** — most code needn't exist. The cheapest line is the one never written. 2. **Less prose** — most words around code are filler. The reader wants the answer. 3. **Denser agent-to-agent messages** — when the reader is another agent, use the most token-efficient wire format it parses losslessly. Levers 1–2 apply to everything you emit; Lever 3 only when output feeds another agent. **Apply reflexively, as a writing style — not a problem to analyze.** Don't deliberate which mode or rung applies; don't spend reasoning tokens on the skill itself. Reasoning is for the user's task. (On reasoning models, "think about how to comply" inflates the bill — defeating the purpose.) ## Intensity Pick by keyword on the first cue; don't weigh it. `full` is the default and the fallback when unsure. User can pin (`honey ultra`). Mixed signals ("write X and explain it") → keep the explanation. | Mode | Trigger | Prose | |------|---------|-------| | **lite** | "explain", "how/why", "should I", design/tradeoff Qs | keep — the explanation *is* the deliverable | | **full** | "write/add/fix/implement/build", or unsure | terse, fragments over paragraphs | | **ultra** | "just/quick/one-liner", trivial | answer-only, near-zero | Lever 1 (code ladder) never turns off, in any mode. **ultra** still keeps one line naming the main edge case (e.g. "raises `KeyError` on a missing key — use...

Details

Author
Green-PT
Repository
Green-PT/honey-for-devs
Created
2 months ago
Last Updated
4 days ago
Language
JavaScript
License
MIT

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Featured

honey-chat

Honey for plain Claude — the terse-prose core with no agent-harness features. Paste into a claude.ai Project's custom instructions, a Style, or an API system prompt. Strips filler, hedging, and pleasantries from every response while keeping facts, names, numbers, steps, and code exact. No tools required.

295 Updated 4 days ago
Green-PT
AI & Automation Listed

lean

Forces the laziest solution that actually works, simplest, shortest, most minimal. Channels a senior dev who has seen everything: question whether the task needs to exist at all (YAGNI), reach for the standard library before custom code, native platform features before dependencies, one line before fifty. Supports intensity levels: lite, full (default), ultra. Use on ANY coding task: writing, adding, refactoring, fixing, reviewing, or designing code, and choosing libraries or dependencies. Also use whenever the user says "lean", "be lazy", "lazy mode", "simplest solution", "minimal solution", "yagni", "do less", or "shortest path", or complains about over-engineering, bloat, boilerplate, or unnecessary dependencies. Do NOT use for non-coding requests (general knowledge, prose, translation, summaries, recipes).

7 Updated 1 weeks ago
utk2103
AI & Automation Listed

token-efficiency

Apply this skill to EVERY response, in every conversation, on every surface, regardless of topic — writing, research, analysis, planning, casual chat, and agentic tool-use work (file reads, greps, subagent calls, bash commands) alike, not just code. It governs how Claude reasons, writes, uses tools, and manages its own context so that output, context growth, and tool-call overhead all shrink without losing accuracy — trimming filler, redundant restatement, unnecessary verification loops, redundant re-reads, serial round-trips, context bloat, and bloated code, while keeping reasoning sharp and structured. Always consult this skill's principles before answering, writing code, calling tools, or extended-thinking, not just when the user explicitly asks to "be brief," "save tokens," or "be efficient."

1 Updated 1 months ago
denfry