code-import
Read an existing repository's structure into the project cwd as a normalised snapshot the agent can analyse without re-walking the tree on every turn.
Profile →npx skills add nexu-io/open-design --skill code-import --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Code import Spec §10 / §21.3.2: a code-migration / tune-collab run starts from a real repo (cloned via `od project import` or a path the user provided). This atom turns the raw checkout into a normalised on-disk record that subsequent atoms (`design-extract`, `rewrite-plan`, `patch-edit`) operate against. The point is to **stop re-walking the tree on every turn** — the agent reads `code/index.json` once and trusts the snapshot until the next explicit re-import. ## Inputs | Source | Required | Notes | | --- | --- | --- | | `repoPath` | yes | Absolute path to the repo's root, supplied via `od project import` or an upstream `od.context.assets[]` reference | | `targetStack` | yes | { framework, packageManager, styleSystem, componentLibrary } via the matching `form` GenUI surface | ## Output ```text project-cwd/ └── code/ ├── index.json # { files: { path, size, language, imports[] }[], packageJson?, lockfileKind, framework, styleSystem } ├── components.json # detected components with file path + props snapshot ├── routes.json # detected routing model (next/app, react-router, vite-router, …) └── meta.json # { repoPath, gitSha, walkedAt, atomDigest, walkBudgetMs } ``` `code/index.json`
- Inputs
- Output
- Convergence
- Anti-patterns the prompt fragment forbids
- Status
What does the code-import skill do?
Read an existing repository's structure into the project cwd as a normalised snapshot the agent can analyse without re-walking the tree on every turn.
How do I install it?
Run `npx skills add nexu-io/open-design --skill code-import --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From nexu-io/open-design, a repository with 83,577 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.