web-dedup

Detect and de-duplicate duplicated web frontend code with zero-diff verification.

15|8|Updated Oct 8, 2024
One-click install
npx skills add https://github.com/yanet-platform/yanet2 --skill web-dedup
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: web-dedup
Source: https://github.com/yanet-platform/yanet2/tree/main/.claude/skills/web-dedup
Command: npx skills add https://github.com/yanet-platform/yanet2 --skill web-dedup

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

De-duplicate the YANET2 web frontend by detecting copy-paste and extracting shared components, hooks, SCSS, and utilities into reusable assets, enabling a maintainable, single source of truth across pages.

Core Features & Use Cases

  • Detect copied markup, logic, and styles across web/src.
  • Triage and delegate extractions to coder-ui with zero-diff proofs for safe refactors.
  • Ship one PR per extraction and maintain visual parity with the original pages.

Quick Start

Run the web-dedup pipeline over web/ to identify and extract shared components, hooks, and styles with zero-diff verification.

Frequently Asked Questions about web-dedup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find and remove duplicated web frontend code?

To remove duplicated web frontend code, use a multi-phase pipeline that detects copied markup, logic, and styles, then extracts shared components, hooks, and SCSS into reusable assets with zero-visual-diff proofs.

What is zero-diff verification for frontend refactoring?

Zero-diff verification for frontend refactoring is a structured proof process ensuring extracted shared components and styles maintain exact visual parity with the original pages after duplication removal.

How do I extract shared SCSS and hooks from web src safely?

To extract shared SCSS and hooks safely, coordinate a pipeline that triages duplicated code and delegates extractions to coder-ui, shipping one PR per extraction with zero-diff proofs for safe refactors.

When should I run a deduplication pipeline on my web frontend?

Run a deduplication pipeline on your web frontend after large feature pushes to reduce code duplication and maintainability overhead, ensuring a single source of truth across pages.

Does the deduplication process require guardrails for extraction targets?

Yes, the deduplication process requires references to guardrails for extraction targets to safely coordinate the identification, triage, and extraction of shared frontend components and styles.

Can I ship one PR per extraction without breaking visual parity?

Yes, you can ship one PR per extraction while maintaining visual parity by applying a structured verification workflow that provides zero-diff proofs for all refactored components and styles.