Menu
Restructure and organize a repository through a staged campaign.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Design, redesign, or review real interfaces, documents, illustrations, and related visual systems from their content, audience, intended action, and existing project direction. Use when creating UI, improving visual hierarchy or coherence, reviewing a rendered artifact, or when "the page works but feels generic/inconsistent". Also use to establish a continuing project's visual direction from selected references when none exists, or to turn an ambiguous style cue into provisional guidance for later design. Triggers include "design this interface", "redesign this page", "review the UI", "make these pages feel unified", "the direction is right but the components feel generic", "polish/refine the interface details", "align this logo or illustration with the product", "art direction", and "审美/视觉设计/组件细节/插画或品牌视觉统一/确立风格". Do not use for a purely functional code fix, naming task, or automatic aesthetic acceptance. Never impose a portable fixed style.
Build or revise an evidence-linked capability profile for a model execution setup by running repeated, representative real tasks under matched conditions. Use when comparing models, providers, plans, coding harnesses, or prompt/tool profiles for task allocation; when asking "which model is good enough for this work?", "evaluate this model", "compare model capability", "模型评测/能力画像/模型适合什么任务", or whether a characterized setup may have degraded. Do not use for provider setup, public leaderboard summaries, one-off response review, automatic routing, or a degradation verdict without an accepted baseline.
Use this Skill, not a named task Skill, when that Skill or capability is the object of user-level setup, installation, migration, or configuration. An installed or runtime-discovered copy is target evidence, not a desired source. If the human has not supplied the selected capability's source, return `NEEDS_INPUT` before reading it, inventory, lookup, planning, or action; never inspect secret values. Use for "set up my agents on this machine", "migrate my AI coding setup", "新设备配置 Codex/Cursor/Claude Code", "update my global agent workflow", or reconstructing selected skills, harness guidance, plugins, MCP, hooks, permissions, runtimes, and authentication prerequisites. Setup does not imply marketplace discovery, CLI/provider installation, or full-toolbox adoption. Do not use for project-local agent workflow design, fleet policy, sessions/caches, or unrelated dotfiles.
Build, verify, or selectively refresh a source-linked working model of a substantial project when later agents or tasks need to reuse its architecture, responsibilities, authority, state, causal, evidence, or change relations. Use for "initialize project cognition", "map this project for future work", "建立项目认知", "更新项目认知", "what existing cognition is invalidated by this change?", or when repeated tasks keep reconstructing the same project model. Do not use for a one-off code review, ordinary repository orientation, context-delivery configuration, or as a mandatory project setup step.
Review a proposed code change, staged diff, commit, patch, or pull request for decision-changing defects before acceptance or merge. Use when asked "review this code", "review the diff/PR", "can this merge", "find regressions", or when a consequential implementation needs an impact-aware independent review. Do not use to implement the change, process already-filed PR comments, settle an unaccepted architecture, review visual design, or orchestrate reviewers.
Audit whether a project's artifact layout still expresses its accepted design, then apply one smallest safe organization transition when a material gap exists. Use for "organize the repo", "组织架构", "根据地", stale project structure, source/projection confusion, or campaign residue. Not for ordinary file cleanup, system-module design, Sequence change, or skill authoring.
| name | project-restructure |
| description | Restructure and organize a repository through a staged campaign. |
| argument-hint | [inventory | model | target | gap | plan | execute | verify] |
Always run every stage in order. Create a restructure/ directory before doing
any analysis and retain every stage file for future agents.
inventory: list every repository file in restructure/INVENTORY.md.model: classify every file and write restructure/MODEL.md.target: design the final tree in restructure/TARGET.md.gap: compare every current and target path in restructure/GAP.md.plan: write all migration waves in restructure/PLAN.md.execute: move every planned file and update all references.verify: write restructure/VERIFY.md after all movement is complete.Never skip a document. More documentation makes restructuring safer. Keep the campaign directory permanently because another agent may need the history.
restructure/.