Leaderboard/Software Engineering/icm-architect
Last commit on August 25, 2026·Created on July 18, 2026

RinDig/icm-architect

Turns folders into legible architecture for repeatable agent work.
Combined rank
#215
across all skills
In Software Engineering
#16
category rank
Stars
1.6k
+5.9% in last 7d
Forks
226
+5.1% in last 7d
Watchers
42
+7.7% in last 7d
Traction scoreGitHub stars can be faked, so popularity alone can be misleading. Traction Score looks for broader signs of recent attention, adoption, and active maintenance.
TL;DR

ICM Architect restructures processes, knowledge collections, and codebases into plain-text workspaces where folders encode sequence, context, and state. It gives automation builders and technical leads explicit routing files, stage contracts, human review points, and walkable edit maps so one agent can load only the material needed for each step.

WHO IT'S FOR
AI agent / automation builders
turn recurring workflows into agent-runnable pipelines
Knowledge management specialists
organize scattered notes into AI-walkable libraries
Technical leads / architects
audit codebases into walkable edit maps
Platform / DevEx teams
restructure workspaces to ICM conventions
Repository contents

1 skill file

Compatible AgentsThe repository documents support for these agents. The skills may also work with other agents that can load SKILL.md files, but they may need some setup or small changes.

Use this skill

Follow the documented setup, then try a first task.

I’m using

Claude Code — user scope

Installs: User-wide installation of the icm-architect skill folder · Claude Code

  1. Copy the repository's `icm-architect` folder to `~/.claude/skills/icm-architect/`.

README.md · Checked Sep 18, 2026

Give it something to do.

Suggested first task

Design a small recurring workflow

Uses icm-architect

  • A description of the recurring workflow
  • Its repeating unit of work
  • Known steps or human review points
  • Stable rules, references, or templates
  • The desired final artifact
Use icm-architect in Build mode to design the smallest ICM workspace for [describe one recurring workflow]. Start by asking me a few questions about the repeating unit, the steps and review points, what stays stable between runs, and the final artifact. Then propose the folder structure and explicit folder-level contracts for my review.
SKILL.md · Checked Sep 18, 2026
Suggested first task

Propose an ICM restructure map

Uses icm-architect

  • Path to the existing folder, repository, or vault
  • A short description of what the workspace is used for
  • Any files or directories that must remain unchanged
Use icm-architect in Restructure mode to audit [path to an existing folder, repository, or vault]. Propose an ICM migration map for approval, but do not move or delete anything. Keep stable reference material separate from per-run working artifacts and identify where human review gates belong.
SKILL.md · Checked Sep 18, 2026README.md · Checked Sep 18, 2026
Suggested first task

Create a system-map proposal

Uses icm-architect

  • Path to the code or mixed-content repository
  • The area or change scenario to map first
Use icm-architect's System map form to inspect [path to a code or mixed-content repository] and propose a small, walkable edit map covering its main objects, processes, and change-impact relationships. Do not modify the repository; return the proposed map for review.
SKILL.md · Checked Sep 18, 2026README.md · Checked Sep 18, 2026