60 Million Installs, I Only Use 1 Plugin After 11 Days

by




EDIBLOG · CLAUDE CODE · 11 DAYS IN

60 Million Installs, I Only Use 1 Plugin After 11 Days

Bottom line first. I’m running exactly one plugin, and 11 days in my blog’s readability has jumped a tier. This isn’t a deep review. It’s the install-count Top 5 and a quick note on what I actually use.

1 of 5 in use
Day 11
600K+ installs
Review coming

01 · BEFORE → AFTERWhat 11 days did to my blog

Before April 2026
Old post
Text-heavy, 0 visual blocks
Design almost none
Infographics 0
Readability low
→
After plugin
↓
May 2026 (now)
v2 layout
Infographics + 1st-person
Design auto-generated
Infographics 5+ per post
Readability way ↑

The Before is an old post of mine (jessyt.tistory.com/50), and the After is yesterday’s post (jessyt.tistory.com/369). Same writer, same toolchain otherwise. 11 days makes that much difference.

02 · THE TRIGGERInstalled April 26, posted this on May 7

frontend-design plugin — 11 days in
0 visual blocks
→
8+ blocks

Infographic system, every post

This isn’t a feature pitch. The HTML structures I used to hand-write are now generated for me, every single time. Click an old post, click yesterday’s — the gap is obvious.

↗ See Before
↗ See After

03 · THE NUMBERSInstall counts make it pretty clear

#1
installs
617K
frontend-design
Top 5
combined
1.93M+
unique installs
What
I use
1
of 5
Time
used
11d
4/26 → 5/8

04 · TOP 5Marketplace’s most-installed plugins right now

Claude Code Plugins · as of 2026/4/26
unique installs
1
frontend-design  · the one I use
617,078
2
superpowers
532,114
3
context7
285,485
4
code-review
273,616
5
code-simplifier
226,745

Below #5, the runners-up are github (210K), skill-creator (190K), playwright (190K), feature-dev (180K), and claude-md-management (160K). Honest take: 9 of the Top 10 I haven’t even tried. That surprised me.

05 · WHY NOT YETWhy I’m still on just one

▮ Why I haven’t moved on
  • Once I install one, I spend 11 days digging into only that. Settling-in time is real.
  • The #1 plugin’s payoff is so obvious that I had no urgency to add a second.
  • A new tool means a new mental model. Stacking several at once is a tax I don’t want.
  • Automation tools shouldn’t be piled up. Validate one at a time — that’s the answer I keep landing on.

▮ MY POSITION · 11D
2026 / 04 / 26 →

Honest verdict after 11 days. “All upside, no downside — so far.”

What worked

Blog readability and quality jumped. Infographic blocks generated for me each time. Time spent on design ≈ zero.

What I haven’t seen yet

No downside surfaced. 11 days is short — I’ll re-evaluate after another month.

06 · NEXT UP3 candidates I’ve already lined up

▮ Candidates + why
  • hookify — helper for writing PostToolUse hooksMaps directly onto my existing automation infra
  • skill-creator — build your own skillsI have 3 more skills queued up. Could automate the whole flow
  • playwright — browser automationCore to my Tistory/WP publishing. I already have a hand-rolled version, so a side-by-side post is on the table
  • Honest writeup after I actually use themGood is good, meh is meh — I’ll write it as it lands

“600K people installing it doesn’t mean you have to. I picked one and dug in for 11 days.“

— Eddie · after 11 days

If you’re new to Claude Code, start with frontend-design alone. Run it for a month before adding the next one — you won’t be late. The next review post is on its way.

References · Sources
Claude Code official

Claude Code documentation
claude-code GitHub

Install-count data

claude-plugins-official marketplace (install-counts-cache.json, fetched 2026-04-26)

Primary sources

ediblog — Before post (pre frontend-design)
ediblog — After post (May 7, v2 system)

Disclosure: Personal experience and judgment. Snapshot at day 11. No ads, no affiliate links.

This post is part of an English mirror of a Korean dev experiments blog. Cross-posted for the global developer audience.

​




Leave a Comment