bacoco

Insight Forge — Design skill for Claude Code

Design community

Cross-session ARA-style learner for Claude Code & Codex CLI — extracts typed events from JSONL transcripts, maintains a structured knowledge base, proposes CLAUDE.md / AGENTS.md diffs.

How to install Insight Forge

This entry records only its repository, not the path inside it, so there is no exact command to give. Open bacoco/insight-forge and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Insight Forge does

Cross-session ARA-style learner for Claude Code & Codex CLI — extracts typed events from JSONL transcripts, maintains a structured knowledge base, proposes CLAUDE.md / AGENTS.md diffs.

Alternatives in Design

  • Brainstorming — Transform rough ideas into fully-formed designs through structured questioning and alternative exploration 27.9k ★
  • Taiyi Forge — TaiyiForge engine control — init, next, harness, continue (OMX-style) 881 ★
  • Platform Design Skills — 300+ design rules from Apple HIG, Material Design 3, and WCAG 2.2 for cross-platform apps 261 ★

README

Insight Forge

![Insight Forge](assets/banner.jpg)

Your AI sessions know more than you think.


You've been building with AI for months.

You've discovered what works. What breaks silently. What you should never try again. You've earned that knowledge — one session at a time, across hundreds of conversations.

And most of it is gone.

Buried in JSONL files. Scattered across transcripts. Half-remembered in a `CLAUDE.md` that's grown into a graveyard of overconfident rules nobody dares touch.

**insight-forge reads every session you've ever had and tells you what you actually learned.**

Not summaries. Not guesses. Project rules and dead ends — quoted from your own words, dated, with the moment you confirmed each one.


Install

**Claude Code** — tell Claude:

"Install the insight-forge skill from https://github.com/bacoco/insight-forge"

**Codex CLI** — tell Codex:

"Install the insight-forge skill from https://github.com/bacoco/insight-forge"

That's it. Your agent handles the rest.


What you'll see

Run it once. You'll get a friendly summary in your terminal:

  Insight Forge — proposal for CLAUDE.md
  ────────────────────────────────────────────────────────
  ✓ 3 project rules ready
      • Use pnpm not npm
      • Always run lint:fix before committing
      • Tests live in tests/, not __tests__/
  ✗ 1 dead end to avoid
      • Don't use the npm run validate script
  · 5 observations still in staging (need more sessions)

  Full proposal — open or paste from:
    .insight-forge/proposals/2026-05-05T12-28-15Z.md

Open the proposal and every suggestion shows you why it's there:

### Heuristics (project rules)

- **H01**: Use pnpm not npm
  - *You said* (May 1): "Always use pnpm for this repo, never npm."
  - *You confirmed* (May 1): "yes parfait, on part sur pnpm"
  - *Sessions*: [aaaa1111]

Nothing is invented. Every line cites the moment in your transcripts where you actually earned it.


How it decides wh