mcpField
R
rebuild-or-improve-advisor

rebuild-or-improve-advisor

github.com/sergekostenchukDesign & UI3251 installsUpdated 18w ago
Repository

About rebuild-or-improve-advisor

rebuild-or-improve-advisor is a skill that turns evidence about an existing site into a strategy recommendation. It compares improvement, redesign, partial rebuild, and full rebuild options without implementing changes to production systems.

Key features

  1. 01Decision and tradeoff modes
  2. 02Comparison of four site strategies
  3. 03Evidence-based decision record
  4. 04Migration-planner routing
  5. 05Council input for conflicting constraints

Use cases

  1. 01Choose a path for an underperforming site
  2. 02Compare rebuild risks and tradeoffs
  3. 03Prepare implementation handoff
  4. 04Resolve conflicts across UX, SEO, and migration

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/sergekostenchuk/ui-ux-agent-skill-system --skill rebuild-or-improve-advisor

After installing, type/rebuild-or-improve-advisorin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

agents/
openai.yaml
assets/
rebuild-decision-record.template.md
evals/
evals.json
references/
rebuild-decision-contract.md

Details

From the project README

Rebuild Or Improve Advisor

This skill converts existing-site evidence into a strategy decision. It does not implement the redesign and does not change production systems.

Operating Modes

  • decision: choose improve, redesign, partial rebuild, or full rebuild.
  • tradeoff: compare strategy options with risks, costs, and proof needed.
  • handoff: prepare next steps for migration-planner, marketing-site-skill, webapp-ui-skill, or senior-ui-ux-orchestrator.
  • council-input: prepare a concise position for senior council when UX, SEO, migration, or business constraints conflict.

Required Workflow

  1. Read references/rebuild-decision-contract.md.
  2. Start from an existing-site-analyzer report or clearly label missing evidence.
  3. Compare options:
    • improve in place;
    • visual redesign on current stack;
    • partial rebuild;
    • full rebuild and migration.
  4. Use assets/rebuild-decision-record.template.md.
  5. If URLs, redirects, canonical pages, sitemap, robots, schema, or GSC/webmaster verification may change, require migration-planner.
  6. If the recommendation affects SEO/LLM, public facts, or conversion structure, route conflicts to senior-ui-ux-orchestrator council.

Safety Rules

  • Do not recommend full rebuild only because visual design is weak; include migration and maintainability tradeoffs.
  • Do not recommend in-place improvements when severe technical, content, or SEO issues make that unsafe.
  • Do not claim search traffic, rankings, or conversion data unless source evidence exists.
  • Do not change production files, redirects, analytics, DNS, CMS, or deployment settings.

Handoff Shape

Decision:
Evidence used:
Options compared:
Recommended path:
Why not the alternatives:
Migration planner required:
Implementation owner:
Validation gates:
Open risks:

Validation

When editing this skill, run:

python3 $CODEX_HOME/skills/.system/skill-creator/scripts/quick_validate.py $CODEX_HOME/skills/rebuild-or-improve-advisor
python3 $CODEX_HOME/skills/senior-skill-architect/scripts/lint_production_skill.py $CODEX_HOME/skills/rebuild-or-improve-advisor
python3 -m json.tool $CODEX_HOME/skills/rebuild-or-improve-advisor/evals/evals.json >/dev/null

Comments

Markdown supported