Agent skill

Rewrite Plan

Author a long-running multi-file rewrite plan that subsequent patch-edit + diff-review + build-test stages will execute, with explicit ownership boundaries and patch-safety guarantees.

Apache-2.0Auto-check passedFrontend & Design

Install Rewrite Plan

skills CLI

$ npx skills add nexu-io/open-design --skill rewrite-plan -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install nexu-io/open-design rewrite-plan --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/nexu-io/open-design.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/_official/atoms/rewrite-plan .claude/skills/rewrite-plan && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "rewrite-plan" agent skill from https://github.com/nexu-io/open-design/tree/main/plugins/_official/atoms/rewrite-plan into .claude/skills/rewrite-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rewrite-plan", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/nexu-io/open-design/tree/main/plugins/_official/atoms/rewrite-plan

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add nexu-io/open-design --skill rewrite-plan -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install nexu-io/open-design rewrite-plan --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/nexu-io/open-design.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/_official/atoms/rewrite-plan .agents/skills/rewrite-plan && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "rewrite-plan" agent skill from https://github.com/nexu-io/open-design/tree/main/plugins/_official/atoms/rewrite-plan into .agents/skills/rewrite-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rewrite-plan", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add nexu-io/open-design --skill rewrite-plan -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install nexu-io/open-design rewrite-plan --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/nexu-io/open-design.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/_official/atoms/rewrite-plan .cursor/skills/rewrite-plan && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "rewrite-plan" agent skill from https://github.com/nexu-io/open-design/tree/main/plugins/_official/atoms/rewrite-plan into .cursor/skills/rewrite-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rewrite-plan", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/nexu-io/open-design.git --path plugins/_official/atoms/rewrite-plan

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add nexu-io/open-design --skill rewrite-plan -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install nexu-io/open-design rewrite-plan --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/nexu-io/open-design.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/_official/atoms/rewrite-plan .gemini/skills/rewrite-plan && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "rewrite-plan" agent skill from https://github.com/nexu-io/open-design/tree/main/plugins/_official/atoms/rewrite-plan into .gemini/skills/rewrite-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rewrite-plan", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install nexu-io/open-design rewrite-plan

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add nexu-io/open-design --skill rewrite-plan -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/nexu-io/open-design.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/_official/atoms/rewrite-plan .github/skills/rewrite-plan && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "rewrite-plan" agent skill from https://github.com/nexu-io/open-design/tree/main/plugins/_official/atoms/rewrite-plan into .github/skills/rewrite-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rewrite-plan", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add nexu-io/open-design --skill rewrite-plan -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install nexu-io/open-design rewrite-plan --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/nexu-io/open-design.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/_official/atoms/rewrite-plan .opencode/skills/rewrite-plan && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "rewrite-plan" agent skill from https://github.com/nexu-io/open-design/tree/main/plugins/_official/atoms/rewrite-plan into .opencode/skills/rewrite-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rewrite-plan", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: rewrite-plan
GitHub stars: 100k
Token cost: ~511 tokens
SKILL.md length: 189 words
Files: 2
Skills in repo: 245
Repo updated: Oct 9, 2026
First seen: Oct 7, 2026
Licence: Apache-2.0

At a glance

Author a long-running multi-file rewrite plan that subsequent patch-edit + diff-review + build-test stages will execute, with explicit ownership boundaries and patch-safety guarantees.

Frontend & Design work in your project
SKILL.md covers Inputs, Output, Convergence and Anti-patterns the prompt…, plus 1 more section
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Rewrite Plan is an agent skill from nexu-io/open-design. Author a long-running multi-file rewrite plan that subsequent patch-edit + diff-review + build-test stages will execute, with explicit ownership boundaries and patch-safety guarantees.

Its SKILL.md is about 510 tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `open-design.json`).

It sits in Frontend & Design. The repository describes itself as: 🎨 Best DeepSeek Harness Design Plugin. The open-source Claude Design alternative. 🖥️ Local-first desktop app. 🖼️ Your coding agent becomes the design engine: prototypes… The licence is Apache-2.0.

When your agent uses it

Frontend & Design work in your project

Example prompts

“/rewrite-plan”

What it can do on your machine

Read from SKILL.md and the folder at commit d9dd6fe. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Rewrite Plan loads about 511 tokens when it runs. Until then it costs about 49 tokens; SKILL.md has 189 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~49
When it runs · the whole SKILL.md, loaded when a task matches: ~511

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from nexu-io/open-design at commit d9dd6fe, republished under its Apache-2.0 licence (© nexu-io). 189 words, ~511 tokens.

Download SKILL.mdSave it as .claude/skills/rewrite-plan/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.

name: rewrite-plan
description: Author a long-running multi-file rewrite plan that subsequent patch-edit + diff-review + build-test stages will execute, with explicit ownership boundaries and patch-safety guarantees.
od.scenario: code-migration
od.mode: planning

Rewrite plan

Spec §20.3 / §21.3.2: scenario 4 (design → deliverable production code) requires a contract-shaped rewrite plan before the agent starts editing files. The plan is the audit trail every subsequent stage references; without it the patch path slides into "refactor everything that looks wrong" and the build breaks in unreviewable ways.

Inputs

code/index.json from code-import.
token-map/*.json from token-map.
The active design system DESIGN.md (already in prompt).
The user's tune intent (typically a short brief).

Output

text

project-cwd/
└── plan/
    ├── plan.md           # human-readable narrative
    ├── ownership.json    # { file: '...', layer: 'leaf' | 'shared' | 'route' | 'shell' }
    ├── steps.json        # ordered { id, files[], rationale, risk: 'low' | 'medium' | 'high' }[]
    └── meta.json         # { generatedAt, atomDigest, tokenMapDigest }

steps.json is the input patch-edit reads one entry per iteration. ownership.json is the source of truth for "which files belong to a single component vs. shared infrastructure"; patch-edit refuses to touch a shell-tier file unless the matching step has risk: 'high' and the user explicitly confirmed.

Convergence

The atom completes when plan.md is non-empty AND steps.json contains at least one step.

Anti-patterns the prompt fragment forbids

Plans that include "rewrite the whole component library" as a single step. Break into per-component steps.
Plans that don't classify ownership.
Plans that don't list a build-test step at the end.

Status

Implemented by the daemon runner in apps/daemon/src/plugins/atoms/rewrite-plan.ts. It classifies ownership and writes plan.md, steps.json, and ownership.json.

Files

SKILL.md and 1 other file in plugins/_official/atoms/rewrite-plan of nexu-io/open-design.

SKILL.md
open-design.json

Open the folder on GitHubat commit d9dd6fe

Compare with similar skills

Rewrite Plan next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Rewrite Plan compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Rewrite Plan this skillnexu-io/open-design	100k	—	~511	Automated safety check: Pass	Apache-2.0	today
Web Artifacts Builderanthropics/skills	180k	41 repos	~769	Automated safety check: Pass	Apache-2.0	yesterday
React Doctormakeplane/plane	61k	12 repos	~657	Automated safety check: Pass	AGPL-3.0	yesterday
Impeccablebestofjs/bestofjs	3.1k	27 repos	~2.6k	Automated safety check: Pass	MIT	5 days ago
Figma Design System Builderwarpdotdev/warp	65k	2 repos	~4.4k	Automated safety check: Pass	AGPL-3.0	today
Web Interface Guidelines Reviewervercel-labs/openreview	1.7k	97 repos	~308	Automated safety check: Pass	None	7 mo ago

Similar skills

Web Artifacts Builder
anthropics/skills
Official
Builds multi-component claude.ai HTML artifacts as a small React, TypeScript and Tailwind project, then bundles it into one shareable HTML file.
180k GitHub starsUsed in 41 repos~769 tokens
Frontend & DesignAuto-check passed
React Doctor
makeplane/plane
Scans React code for lint, accessibility, bundle size and architecture issues, reports a health score and checks that changes do not lower it.
61k GitHub starsUsed in 12 repos~657 tokens
Frontend & DesignAuto-check passed
Impeccable
bestofjs/bestofjs
A skill your agent uses when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a…
3.1k GitHub starsUsed in 27 repos~2.6k tokens
Frontend & DesignAuto-check passed
Figma Design System Builder
warpdotdev/warp
Builds or updates a design system in Figma from a codebase in ordered phases: discovery, variables and tokens, components, theming and documentation, with checkpoints.
65k GitHub starsUsed in 2 repos~4.4k tokens
Frontend & DesignAuto-check passed
Web Interface Guidelines Reviewer
vercel-labs/openreview
Official
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my…
1.7k GitHub starsUsed in 97 repos~308 tokens
Frontend & DesignAuto-check passed
Tailwindcss Development
anonaddy/anonaddy
Always invoke when the user's message includes 'tailwind' in any form.
4.9k GitHub starsUsed in 10 repos~865 tokens
Frontend & DesignAuto-check passed

More from nexu-io/open-design

All 245 skills in this repo

Humanize PPT
nexu-io/open-design
Turns raw notes into a talk-ready slide outline with per-page image, diagram or video decisions, then checks the rendered deck against that outline.
100k GitHub stars~4k tokensUpdated today
Auto-check passed
Last 30 Days Trend Research
nexu-io/open-design
Produces a cited Markdown briefing on recent community sentiment and social reaction to a topic, labeling every source it could not actually check.
100k GitHub stars~1.3k tokensUpdated today
Auto-check passed
OpenDesign Contribution Flow
nexu-io/open-design
Helps newcomers contribute to OpenDesign: ship a skill or design system, translate docs, fix docs or report a bug, ending in a pull request or issue.
100k GitHub stars~3.5k tokensUpdated today
Auto-check: notes
Chat Motion Overlay Generator
nexu-io/open-design
Turns a chat transcript or screenshot into a configurable animated chat clip, rendered as a Remotion bundle with optional transparency.
100k GitHub stars~1.1k tokensUpdated today
Auto-check passed
Flowai Live Dashboard Template
nexu-io/open-design
Team-management dashboard skill in the FlowAI aesthetic — three tabs (Team Members, Team Details, Activity Log), KPI stat row, member table, role distribution bar chart, online presence and activity…
100k GitHub stars~865 tokensUpdated today
Auto-check passed
Hatch Pet
nexu-io/open-design
Create, repair, validate, preview, and package Codex-compatible animated pet spritesheets from character art, screenshots, generated images, or visual references.
100k GitHub stars~6k tokensUpdated today
Auto-check passed

Questions about Rewrite Plan

What does Rewrite Plan do?

Author a long-running multi-file rewrite plan that subsequent patch-edit + diff-review + build-test stages will execute, with explicit ownership boundaries and patch-safety guarantees. Rewrite Plan is an agent skill from nexu-io/open-design. Author a long-running multi-file rewrite plan that subsequent patch-edit + diff-review + build-test stages will execute, with explicit ownership boundaries and patch-safety guarantees.

When should I use Rewrite Plan?

Rewrite Plan fits situations like: frontend & Design work in your project.

How do I install Rewrite Plan in Claude Code?

Run `npx skills add nexu-io/open-design --skill rewrite-plan -a claude-code`. Or copy the skill folder (plugins/_official/atoms/rewrite-plan in nexu-io/open-design) into .claude/skills/rewrite-plan in your project. Claude Code loads it when a task matches its description.

How do I install Rewrite Plan in Codex?

Run `npx skills add nexu-io/open-design --skill rewrite-plan -a codex`. Or copy the skill folder (plugins/_official/atoms/rewrite-plan in nexu-io/open-design) into .agents/skills/rewrite-plan in your project. Codex loads it when a task matches its description.

Can I use Rewrite Plan in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add nexu-io/open-design --skill rewrite-plan -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/rewrite-plan, .gemini/skills/rewrite-plan, .github/skills/rewrite-plan and .opencode/skills/rewrite-plan in your project.

What does Rewrite Plan need to run?

SKILL.md names no scripts, command-line tools or credentials: Rewrite Plan is instructions for the agent only.

Does Rewrite Plan access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Rewrite Plan safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Rewrite Plan use?

Rewrite Plan is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Rewrite Plan use?

About 511 tokens (SKILL.md is roughly 2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Rewrite Plan?

Skills that share tags, products or a category with Rewrite Plan: Web Artifacts Builder (anthropics/skills, 180k stars), React Doctor (makeplane/plane, 61k stars), Impeccable (bestofjs/bestofjs, 3.1k stars) and Figma Design System Builder (warpdotdev/warp, 65k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Rewrite Plan?

nexu-io (a GitHub organization) maintains it in nexu-io/open-design, which has 100,100 GitHub stars. The repository holds 245 skills in this directory. The repository was last updated on October 9, 2026.

Source: nexu-io/open-design on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Rewrite Plan

Facts

At a glance

What it does

When your agent uses it

Example prompts

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Rewrite plan

Inputs

Output

Convergence

Anti-patterns the prompt fragment forbids

Status

Files

Compare with similar skills

Similar skills

More from nexu-io/open-design

Related

Questions about Rewrite Plan