Skip to content
Back to search

ijbol

MarketplaceWorks with Claude CodeGitHub

IJBOL - It Just Builds, Obviously Lean. Skill pack for Claude Code.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/froilansam--ijbol/badge.svg)](/listings/froilansam--ijbol)

HTML

<a href="/listings/froilansam--ijbol"><img src="/api/listings/froilansam--ijbol/badge.svg" alt="findsafeskills safety rating" /></a>

Install

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

**As a plugin (recommended).** Its session hook turns IJBOL on for every session automatically. This is the setup the benchmark measures. Skill names get a prefix, e.g. `/ijbol:ijbol-review`:

/plugin marketplace add froilansam/ijbol
/plugin install ijbol@ijbol

**As personal skills.** You type the names without a prefix (`/ijbol`, `/ijbol-review`, and so on), and edits in this repo apply right away. Any skill with the same name, and any skill with one of the old names, is moved to `~/.claude/skills-backup-<date>/` first. Nothing is deleted.

git clone https://github.com/froilansam/ijbol && cd ijbol && ./install.sh

Personal skills get no session hook. To turn the core on anyway, import it into `~/.claude/CLAUDE.md` with one line (use your clone's path):

@~/ijbol/hooks/core.md

Use one install method or the other. If you install both, every skill loads twice.

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/marketplace.json · Manifest · 16 lines
  1. {
  2. "$schema": "https://anthropic.com/claude-code/marketplace.schema.json",
  3. "name": "ijbol",
  4. "description": "IJBOL - It Just Builds, Obviously Lean. Skill pack for Claude Code.",
  5. "owner": {
  6. "name": "Froilan Malibiran"
  7. },
  8. "plugins": [
  9. {
  10. "name": "ijbol",
  11. "description": "IJBOL: ijbol, ijbol-lean, ijbol-clean, ijbol-ux, ijbol-visual, ijbol-review",
  12. "source": "./",
  13. "category": "productivity"
  14. }
  15. ]
  16. }
README.md · README · 167 lines
  1. <p align="center">
  2. <img src="assets/banner.svg" alt="IJBOL: It Just Builds, Obviously Lean. A diff that removes 142 lines of over-engineering and adds 2." width="100%">
  3. </p>
  4. <p align="center">
  5. <a href="#install"><img alt="Claude Code plugin" src="https://img.shields.io/badge/Claude%20Code-plugin-d97757"></a>
  6. <img alt="6 skills" src="https://img.shields.io/badge/skills-6-3b82f6">
  7. <a href="#benchmark"><img alt="Benchmarked" src="https://img.shields.io/badge/benchmarked-vs%20no%20skill%20%26%20ponytail-22c55e"></a>
  8. <a href="#built-on-ponytail"><img alt="Built on ponytail" src="https://img.shields.io/badge/built%20on-ponytail-8b5cf6"></a>
  9. </p>
  10. **IJBOL: It Just Builds, Obviously Lean.** The diff is so small you burst
  11. out laughing.
  12. This is a Claude Code skill pack for lean, clean, good-looking code. One
  13. conductor (`ijbol`) loads the right specialist for the job. Each specialist
  14. answers one question, and each rule is written down in only one skill.
  15. ## The skills
  16. | | Skill | Answers | Use it directly when |
  17. |---|---|---|---|
  18. | 🎼 | `ijbol` | What's the workflow? Understand → write → verify → report | Any code change (load it first) |
  19. | ✂️ | `ijbol-lean` | How small? YAGNI, smallest complete change | "be lazy", "simplest", over-engineering |
  20. | 🧹 | `ijbol-clean` | Where and how does it fit? Placement, components, types, naming, no regression, security, project profiles | Refactors, "make it clean", conventions |
  21. | 🧭 | `ijbol-ux` | Does it work for the user? UX lens, states, accessibility, design chain | UI reviews, any visible change |
  22. | 🎨 | `ijbol-visual` | Does it look right? Hierarchy, spacing, type, color, depth | "looks off", polish, design systems |
  23. | 🔍 | `ijbol-review` | Is it ready to ship? Must / Should / Nice findings plus a verdict | "review this", staged changes, PRs |
  24. ## How they fit together
  25. ```mermaid
  26. flowchart LR
  27. hook[["⚡ session hook<br/>injects the IJBOL core once"]] --> core{{"IJBOL core<br/>✂️ lean rules + routing"}}
  28. req([Your request]) --> core
  29. core -- "self-contained task" --> ship(["write it, test it, done<br/>no extra skill calls"])
  30. core -- "multi-file or risky" --> ijbol["🎼 ijbol<br/>full workflow"]
  31. core -- "existing codebase" --> clean["🧹 ijbol-clean<br/>Where does it fit?"]
  32. clean -.-> prof[("profiles/*.md<br/>local, gitignored")]
  33. core -- "visible change" --> ux["🧭 ijbol-ux<br/>Works for the user?"]
  34. ux --> visual["🎨 ijbol-visual<br/>Looks right?"]
  35. core -- "review asked" --> rev["🔍 ijbol-review<br/>Ready to ship?"]
  36. ```
  37. The core rules ([`hooks/core.md`](hooks/core.md), about 430 words) are
  38. always on. The specialists load only when a task needs them, so a small task
  39. costs no extra tool calls.
  40. Every change goes through the same four steps:
  41. ```mermaid
  42. flowchart LR
  43. A["1 · Understand<br/>restate goal, read callers,<br/>search before building,<br/>map the reach"] --> B["2 · Write<br/>YAGNI, DRY, KISS,<br/>right place, cascade"]
  44. B --> C["3 · Verify<br/>lint, types, tests,<br/>see the UI running,<br/>read your own diff"]
  45. C --> D["4 · Report<br/>blast radius,<br/>what was skipped"]
  46. ```
  47. ## Install
  48. **As a plugin (recommended).** Its session hook turns IJBOL on for every
  49. session automatically. This is the setup the benchmark measures. Skill names
  50. get a prefix, e.g. `/ijbol:ijbol-review`:
  51. ```
  52. /plugin marketplace add froilansam/ijbol
  53. /plugin install ijbol@ijbol
  54. ```
  55. **As personal skills.** You type the names without a prefix (`/ijbol`,
  56. `/ijbol-review`, and so on), and edits in this repo apply right away. Any
  57. skill with the same name, and any skill with one of the old names, is moved to
  58. `~/.claude/skills-backup-<date>/` first. Nothing is deleted.
  59. ```
  60. git clone https://github.com/froilansam/ijbol && cd ijbol && ./install.sh
  61. ```
  62. Personal skills get no session hook. To turn the core on anyway, import it
  63. into `~/.claude/CLAUDE.md` with one line (use your clone's path):
  64. ```
  65. @~/ijbol/hooks/core.md
  66. ```
  67. Use one install method or the other. If you install both, every skill loads
  68. twice.
  69. ## Project profiles
  70. The skills are generic. Conventions for one codebase go in a profile:
  71. `skills/ijbol-clean/profiles/<repo>.md`. It is gitignored, so private or
  72. company rules never get pushed. Start the file with which repo it applies to,
  73. then add whatever that codebase needs: file structure, naming table, UI kit,
  74. state library, test/lint commands, gotchas. `ijbol-clean` reads the matching
  75. profile before editing, and its rules beat the generic ones.
  76. ## Benchmark
  77. Each cell below is a real headless Claude Code session on Opus 5.5: 9 tasks,
  78. scored by hidden correctness and safety checks. It runs on
  79. [ponytail's harness](#built-on-ponytail), with ponytail and IJBOL run side by
  80. side, 3 runs each. The full method, per-task numbers and limits are in
  81. [benchmarks/](benchmarks/README.md).
  82. | vs no skill | source LOC | output tokens | total tokens | cost | time | pass |
  83. |---|--:|--:|--:|--:|--:|--:|
  84. | no skill | | | | | | 89% |
  85. | ponytail | **−67%** | **−42%** | −1% | **−17%** | **−37%** | 93% |
  86. | **IJBOL** | **−62%** | **−39%** | +4% | **−12%** | **−34%** | **96%** |
  87. ```mermaid
  88. xychart-beta
  89. title "Hidden checks passed, % (higher is better)"
  90. x-axis ["no skill", "ponytail", "IJBOL"]
  91. y-axis "%" 80 --> 100
  92. bar [89, 93, 96]
  93. ```
  94. ```mermaid
  95. xychart-beta
  96. title "Cost in USD, 9 tasks (lower is better)"
  97. x-axis ["no skill", "ponytail", "IJBOL"]
  98. y-axis "USD" 0 --> 1.3
  99. bar [1.17, 0.97, 1.04]
  100. ```
  101. **The honest read:**
  102. - IJBOL passed more hidden checks than any other arm.
  103. - Compared with no skill, it is cheaper, faster, and writes far less code.
  104. - Ponytail is still a few points leaner on cost and tokens. At this sample
  105. size, a gap that small is close to noise.
  106. - IJBOL v1 loaded every skill with its own tool call. That doubled the turns
  107. and cost 24% *more* than no skill. v3 injects the core once through a hook,
  108. and the [benchmark notes](benchmarks/README.md#how-we-got-here-v1--v3)
  109. show how the numbers changed.
  110. ## Renamed from
  111. | Old | New |
  112. |---|---|
  113. | `ulti` | `ijbol` ("ulti" still triggers it) |
  114. | `ponytail` | `ijbol-lean` |
  115. | `clean-code-implementation` | `ijbol-clean` |
  116. | `ui-ux-frontend-review` | `ijbol-ux` |
  117. | `refactoring-ui` | `ijbol-visual` |
  118. | review mode inside `ulti` | `ijbol-review` |
  119. ## Credits
  120. - `ijbol-visual` summarizes tactics from *Refactoring UI* by Adam Wathan and
  121. Steve Schoger.
  122. ## Built on ponytail
  123. IJBOL stands on [**ponytail**](https://github.com/DietrichGebert/ponytail) by
  124. [Dietrich Gebert](https://github.com/DietrichGebert), the "lazy senior dev"
  125. skill: the best code is the code you never wrote.
  126. - `ijbol-lean` is ponytail's skill with only the name and trigger words
  127. changed (MIT, see [`skills/ijbol-lean/LICENSE`](skills/ijbol-lean/LICENSE)).
  128. - The benchmark above runs on ponytail's
  129. [agentic benchmark harness](https://github.com/DietrichGebert/ponytail/tree/main/benchmarks/agentic)
  130. with one extra `ijbol` arm.
  131. - The full ponytail plugin adds things IJBOL does not have: session hooks,
  132. `ponytail-review`, `ponytail-audit` and `ponytail-debt`. If you only want
  133. the lean part, install ponytail itself.

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.