NT Site Editor / Mirror included

Edit/with intent.

A patch-first skill for Claude Code and Codex that turns requested website changes into traced, reversible, validated edits. NT Site Mirror is included to establish the local baseline first.

Get Editor + Mirror How it works

Evidence-led

Mirror included

Scoped validation

Claude + Codex

The complete edit workflow

One purchase.
Full workflow.

NT Site Editor is the main product. NT Site Mirror comes included, giving the edit workflow a disciplined way to create the local baseline it needs.

NT Site Editor / v1.0 Primary

Website before and after an NT Site Editor transformation

Change
with intent.

A patch-first workflow for editing authorized, completed local mirrors or recreations while protecting the baseline, tracing the real source of truth, and validating each change.

Classify content, style, asset, structural, and behavioral edits before touching the project.
Create a restore point, trace runtime-effective sources, and keep a practical patch ledger.
Validate the edited target and surrounding behavior, with clear limits when the runtime is opaque.

Get Editor + Mirror

NT Site Mirror / v1.3 Included

Baseline
included.

NT Site Mirror comes with Editor for projects that begin at a live website and need an authorized, locally runnable starting point before changes begin.

Choose static mirroring or editable recreation based on the site and permissions.
Preserve observed routes, runtime assets, interactions, and dependencies with evidence.
Hand Editor a declared, validated baseline instead of an undocumented copy.

Included with Editor

What comes with Editor

Baseline first. Then change.

Editor is the working method. The included Mirror stage establishes a defensible local baseline when the project starts from a live site, then Editor keeps every later change traceable.

Observe

Declare the authorized scope, routes, viewports, interactions, and risk signals that matter.

Mirror

Build + validate

Capture or recreate the baseline, serve it locally, then record fidelity, gaps, and dependencies.

Mirror

Hand off cleanly

Keep baseline manifests and evidence intact. Let the working local project become the input for later edits.

Bridge

Trace, patch, prove

Editor creates a restore point, traces the real source, applies a narrow change, and compares before with after.

Editor

Time + token economy

Spend prompts on decisions.

NT Site Editor packages repeatable checks, handoff artifacts, and stop conditions so your agent can follow a defined edit path instead of rebuilding the workflow from scratch in every conversation.

Actual time and token use varies by site complexity, access, runtime behavior, model, requested scope, and validation depth. These tools improve workflow structure; they do not guarantee a fixed saving or a perfect mirror.

01 /

Less repeated setup

Reusable instructions, templates, and deterministic helpers reduce the need to restate every production rule.

02 /

Risk-led depth

Run deeper discovery and validation when named risk signals justify it, while keeping routine scope focused.

03 /

Narrow re-validation

After a local change, recheck the affected surface first; expand only when shared or global behavior demands it.

04 /

Clear stop conditions

Known acceptance tiers, blockers, and patch limits help prevent endless “one more try” loops.

Inside NT Site Editor

Editor ships with
the baseline.

Your Editor purchase includes the two agent-ready skill folders, their workflow guidance, reusable report structures, and Mirror’s deterministic helpers.

Workflow guidance

Installation, boundaries, workflow, and practical usage guidance in a portable reference.

Editor + Mirror skills

Complete skill folders for Claude Code and Codex, with conditional modules and reusable report templates.

Mirror helpers included

Scripts for browser-backed observation, authorized asset mirroring, local serving, and viewport checks come with the included Mirror skill.

FAQ

Before
you start.

The short version: install the complete skill folder, work only on sites you are authorized to use, and let validation determine what can honestly be claimed.

What is included with NT Site Editor?

NT Site Editor includes NT Site Mirror. Use Mirror when the job starts from a live website and needs an authorized local baseline; then use Editor to trace, patch, and validate the requested changes. If you already have a completed, runnable local project, you can begin with Editor.

Does Mirror produce clean source code?

Not always. A static mirror preserves the observed deployed runtime; it is not source recovery. When capture is unsuitable, the workflow may use an editable recreation, but the acceptance status must reflect what was validated and what remains approximate.

Will this work on every website?

No universal guarantee is possible. Authentication, protected media, paid fonts, third-party services, WebGL, service workers, and opaque builder runtimes can limit capture or editability. The workflow is designed to classify those limits clearly instead of hiding them.

What do I need to run the skills?

Claude Code or Codex plus Python 3 for NT Site Mirror’s bundled scripts. Browser capture and viewport validation require Playwright and Chromium. NT Site Editor uses the existing project’s working serve, dev, or build path.

Can I use these on any public site?

No. Public availability is not authorization. Use the skills only for websites and assets you own, control, have client approval for, or are otherwise permitted to work with, and respect licenses, trademarks, privacy, and provider restrictions.

The website is the evidence

Edit the site.
Keep the proof.

Start with NT Site Editor. Use the included Mirror workflow when the job needs a defensible local baseline first.