[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"project-93537":3},{"id":4,"name":5,"fullName":6,"owner":7,"repo":5,"description":8,"homepage":9,"htmlUrl":9,"language":9,"languages":9,"totalLinesOfCode":9,"stars":10,"forks":11,"watchers":12,"openIssues":13,"contributorsCount":14,"subscribersCount":14,"size":14,"stars1d":15,"stars7d":16,"stars30d":16,"stars90d":14,"forks30d":14,"starsTrendScore":17,"compositeScore":18,"rankGlobal":9,"rankLanguage":9,"license":19,"archived":20,"fork":20,"defaultBranch":21,"hasWiki":22,"hasPages":20,"topics":23,"createdAt":9,"pushedAt":9,"updatedAt":24,"readmeContent":25,"aiSummary":9,"trendingCount":14,"starSnapshotCount":14,"syncStatus":13,"lastSyncTime":26,"discoverSource":27},93537,"icm-architect","RinDig\u002Ficm-architect","RinDig","Claude skill: design any process, idea, or problem into an ICM workspace (folder structure as agent architecture), or restructure an existing folder into one",null,210,46,4,2,0,32,84,148,93.36,"MIT License",false,"main",true,[],"2026-07-22 04:02:09","# icm-architect\n\nA Claude skill that designs any process, idea, or problem into an **ICM workspace** — folder structure as agent architecture — or restructures an existing folder, repo, or vault into one.\n\nICM (Interpretable Context Methodology) replaces orchestration code with structure: numbered folders carry sequencing, hierarchy carries context scoping, plain markdown files carry state. One agent, reading the right files at the right moment, does the work of a multi-agent framework — and a human can open any folder and see exactly what state the system is in.\n\nThe workspace is a library. The routing files are the catalog: small, stable, they point at everything and store almost nothing. One librarian — one model — walks the building, and the question decides which shelf gets walked to.\n\n- Paper: [Interpretable Context Methodology: Folder Structure as Agent Architecture](https:\u002F\u002Farxiv.org\u002Fabs\u002F2603.16021) (Van Clief & McDermott)\n- Community: [Clief Notes](https:\u002F\u002Fwww.skool.com\u002Fcliefnotes)\n\n## What it does\n\nTwo modes:\n\n- **Build** — extracts the structure already present in how you describe your work (the stages, the human gates, what's stable vs. per-run), picks one of five proven forms, and scaffolds the smallest workspace that carries it.\n- **Restructure** — audits an existing folder, classifies every file (catalog \u002F contract \u002F factory \u002F product \u002F dead), proposes a migration map for approval, then migrates and validates.\n\nFive forms, one skeleton: **Pipeline** (production line), **Umbrella** (portfolio of pipelines), **Record library** (people\u002Fclients\u002Fsessions), **Knowledge bundle** (a navigable brain), **Context map** (an organization as a graph). They compose and recurse.\n\nEvery result is validated with the **walk test**: an agent with no memory must orient, act, and report status from the files alone.\n\n## Install\n\n**Claude Code:** copy this folder to `~\u002F.claude\u002Fskills\u002Ficm-architect\u002F` (or `.claude\u002Fskills\u002Ficm-architect\u002F` inside a project), then ask Claude to \"ICM this\" \u002F \"structure this for agents\" \u002F \"build me a workspace for X\".\n\n**Claude apps:** upload `icm-architect.skill` (build it with the skill-creator packager, or zip this folder's contents) via Settings → Capabilities.\n\n## Layout\n\n```\nicm-architect\u002F\n├─ SKILL.md              the method: invariants, build mode, restructure mode, walk test\n├─ references\u002F\n│  ├─ core.md            five principles, five-layer hierarchy, naming, token discipline\n│  └─ forms.md           the five forms in depth: skeletons, moves, failure modes\n└─ assets\u002Ftemplates\u002F     copyable starters: CLAUDE.md, CONTEXT.md, stage contract,\n                         node card, schema, setup questionnaire\n```\n\nMIT licensed, like the protocol it serves.\n","2026-07-20 02:30:05","CREATED_QUERY"]