Code Import Agent Skill

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.

605 tokens

context cost

SKILL.md, read when the skill is used

files

plus reference files

copies elsewhere

how many repositories repackaged it

83 386

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/nexu-io/open-design --skill code-import

What comes with it

853 bytes besides the instruction

open-design.json

The instruction itself

6 sections, as written by the author

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

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 is the input every other Phase 7 atom reads. The

walk respects the runner's budgetMs option (default 60s) so

large monorepos don't burn an entire run on import.

Convergence

The atom completes when code/index.json exists and contains at

least one entry. Empty repos abort with a clear error event so the

user re-imports.

Anti-patterns the prompt fragment forbids

Walking node_modules / .git / .next / dist / build (record in

code/index.json.skipped[] with reason).

Inferring a framework from a single file; require at least

package.json's declared dep + a build-config presence

(next.config.*, vite.config.*, etc.).

Treating commented-out imports as live edges.

Status

Implemented by the daemon runner in

apps/daemon/src/plugins/atoms/code-import.ts. The walker enforces its

exclusions and time budget, detects framework evidence, and writes

code/index.json.

Other skills for the same job

different authors, same section of the catalogue

MCP Builder

by anthropics

vendor ×16

Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).

2.3k tokens scripts

Finishing A Development Branch

by ZhanlinCui

×9

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup

Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.

Vercel React Best Practices

by ratacat

×7

React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.

1.3k tokens

Vercel React Native Skills

by vercel-labs

vendor ×6

React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.

Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification

Next.js best practices - file conventions, RSC boundaries, data patterns, async APIs, metadata, error handling, route handlers, image/font optimization, bundling

1k tokens

How to use it

Copy the folder

Take nexu-io/code-import from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.