ijbol
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
Markdown
[](/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
- {
- "$schema": "https://anthropic.com/claude-code/marketplace.schema.json",
- "name": "ijbol",
- "description": "IJBOL - It Just Builds, Obviously Lean. Skill pack for Claude Code.",
- "owner": {
- "name": "Froilan Malibiran"
- },
- "plugins": [
- {
- "name": "ijbol",
- "description": "IJBOL: ijbol, ijbol-lean, ijbol-clean, ijbol-ux, ijbol-visual, ijbol-review",
- "source": "./",
- "category": "productivity"
- }
- ]
- }
README.md · README · 167 lines
- <p align="center">
- <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%">
- </p>
- <p align="center">
- <a href="#install"><img alt="Claude Code plugin" src="https://img.shields.io/badge/Claude%20Code-plugin-d97757"></a>
- <img alt="6 skills" src="https://img.shields.io/badge/skills-6-3b82f6">
- <a href="#benchmark"><img alt="Benchmarked" src="https://img.shields.io/badge/benchmarked-vs%20no%20skill%20%26%20ponytail-22c55e"></a>
- <a href="#built-on-ponytail"><img alt="Built on ponytail" src="https://img.shields.io/badge/built%20on-ponytail-8b5cf6"></a>
- </p>
- **IJBOL: It Just Builds, Obviously Lean.** The diff is so small you burst
- out laughing.
- This is a Claude Code skill pack for lean, clean, good-looking code. One
- conductor (`ijbol`) loads the right specialist for the job. Each specialist
- answers one question, and each rule is written down in only one skill.
- ## The skills
- | | Skill | Answers | Use it directly when |
- |---|---|---|---|
- | 🎼 | `ijbol` | What's the workflow? Understand → write → verify → report | Any code change (load it first) |
- | ✂️ | `ijbol-lean` | How small? YAGNI, smallest complete change | "be lazy", "simplest", over-engineering |
- | 🧹 | `ijbol-clean` | Where and how does it fit? Placement, components, types, naming, no regression, security, project profiles | Refactors, "make it clean", conventions |
- | 🧭 | `ijbol-ux` | Does it work for the user? UX lens, states, accessibility, design chain | UI reviews, any visible change |
- | 🎨 | `ijbol-visual` | Does it look right? Hierarchy, spacing, type, color, depth | "looks off", polish, design systems |
- | 🔍 | `ijbol-review` | Is it ready to ship? Must / Should / Nice findings plus a verdict | "review this", staged changes, PRs |
- ## How they fit together
- ```mermaid
- flowchart LR
- hook[["⚡ session hook<br/>injects the IJBOL core once"]] --> core{{"IJBOL core<br/>✂️ lean rules + routing"}}
- req([Your request]) --> core
- core -- "self-contained task" --> ship(["write it, test it, done<br/>no extra skill calls"])
- core -- "multi-file or risky" --> ijbol["🎼 ijbol<br/>full workflow"]
- core -- "existing codebase" --> clean["🧹 ijbol-clean<br/>Where does it fit?"]
- clean -.-> prof[("profiles/*.md<br/>local, gitignored")]
- core -- "visible change" --> ux["🧭 ijbol-ux<br/>Works for the user?"]
- ux --> visual["🎨 ijbol-visual<br/>Looks right?"]
- core -- "review asked" --> rev["🔍 ijbol-review<br/>Ready to ship?"]
- ```
- The core rules ([`hooks/core.md`](hooks/core.md), about 430 words) are
- always on. The specialists load only when a task needs them, so a small task
- costs no extra tool calls.
- Every change goes through the same four steps:
- ```mermaid
- flowchart LR
- 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"]
- B --> C["3 · Verify<br/>lint, types, tests,<br/>see the UI running,<br/>read your own diff"]
- C --> D["4 · Report<br/>blast radius,<br/>what was skipped"]
- ```
- ## Install
- **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.
- ## Project profiles
- The skills are generic. Conventions for one codebase go in a profile:
- `skills/ijbol-clean/profiles/<repo>.md`. It is gitignored, so private or
- company rules never get pushed. Start the file with which repo it applies to,
- then add whatever that codebase needs: file structure, naming table, UI kit,
- state library, test/lint commands, gotchas. `ijbol-clean` reads the matching
- profile before editing, and its rules beat the generic ones.
- ## Benchmark
- Each cell below is a real headless Claude Code session on Opus 5.5: 9 tasks,
- scored by hidden correctness and safety checks. It runs on
- [ponytail's harness](#built-on-ponytail), with ponytail and IJBOL run side by
- side, 3 runs each. The full method, per-task numbers and limits are in
- [benchmarks/](benchmarks/README.md).
- | vs no skill | source LOC | output tokens | total tokens | cost | time | pass |
- |---|--:|--:|--:|--:|--:|--:|
- | no skill | | | | | | 89% |
- | ponytail | **−67%** | **−42%** | −1% | **−17%** | **−37%** | 93% |
- | **IJBOL** | **−62%** | **−39%** | +4% | **−12%** | **−34%** | **96%** |
- ```mermaid
- xychart-beta
- title "Hidden checks passed, % (higher is better)"
- x-axis ["no skill", "ponytail", "IJBOL"]
- y-axis "%" 80 --> 100
- bar [89, 93, 96]
- ```
- ```mermaid
- xychart-beta
- title "Cost in USD, 9 tasks (lower is better)"
- x-axis ["no skill", "ponytail", "IJBOL"]
- y-axis "USD" 0 --> 1.3
- bar [1.17, 0.97, 1.04]
- ```
- **The honest read:**
- - IJBOL passed more hidden checks than any other arm.
- - Compared with no skill, it is cheaper, faster, and writes far less code.
- - Ponytail is still a few points leaner on cost and tokens. At this sample
- size, a gap that small is close to noise.
- - IJBOL v1 loaded every skill with its own tool call. That doubled the turns
- and cost 24% *more* than no skill. v3 injects the core once through a hook,
- and the [benchmark notes](benchmarks/README.md#how-we-got-here-v1--v3)
- show how the numbers changed.
- ## Renamed from
- | Old | New |
- |---|---|
- | `ulti` | `ijbol` ("ulti" still triggers it) |
- | `ponytail` | `ijbol-lean` |
- | `clean-code-implementation` | `ijbol-clean` |
- | `ui-ux-frontend-review` | `ijbol-ux` |
- | `refactoring-ui` | `ijbol-visual` |
- | review mode inside `ulti` | `ijbol-review` |
- ## Credits
- - `ijbol-visual` summarizes tactics from *Refactoring UI* by Adam Wathan and
- Steve Schoger.
- ## Built on ponytail
- IJBOL stands on [**ponytail**](https://github.com/DietrichGebert/ponytail) by
- [Dietrich Gebert](https://github.com/DietrichGebert), the "lazy senior dev"
- skill: the best code is the code you never wrote.
- - `ijbol-lean` is ponytail's skill with only the name and trigger words
- changed (MIT, see [`skills/ijbol-lean/LICENSE`](skills/ijbol-lean/LICENSE)).
- - The benchmark above runs on ponytail's
- [agentic benchmark harness](https://github.com/DietrichGebert/ponytail/tree/main/benchmarks/agentic)
- with one extra `ijbol` arm.
- - The full ponytail plugin adds things IJBOL does not have: session hooks,
- `ponytail-review`, `ponytail-audit` and `ponytail-debt`. If you only want
- the lean part, install ponytail itself.
Ratings and comments
Sign in to rate this skill.
Sign inFree to use. If it’s helped, pass it on.