anti-duplication

Search endpoints, components, services, and models for existing implementations before writing code.

Updated Jan 5, 2026
One-click install
npx skills add https://github.com/Sjdjdiejdrirhdkjej/Claude-code-conductor --skill anti-duplication-sjdjdiejdrirhdkjej
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: anti-duplication
Source: https://github.com/Sjdjdiejdrirhdkjej/Claude-code-conductor/tree/main/.claude/skills/anti-duplication
Command: npx skills add https://github.com/Sjdjdiejdrirhdkjej/Claude-code-conductor --skill anti-duplication-sjdjdiejdrirhdkjej

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The anti-duplication skill ensures that new code is not written in isolation and instead leverages existing patterns discovered across the codebase, preserving DRY principles and reducing maintenance burden.

Core Features & Use Cases

  • Automated search before implementation: automatically scans for similar endpoints, components, services, and models.
  • Reuse-first guidance: presents options A-D (reuse, extend, extract pattern, follow established pattern) before initiating new code.
  • Proven-pattern enforcement: ensures new code adheres to established patterns and reduces duplication across the project.

Quick Start

  • Start by describing a feature you want to add, and the tool will search for existing patterns and recommend a reuse approach before coding.

Frequently Asked Questions about anti-duplication

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

FAQPage Schema
How do I prevent code duplication when adding new features?

To prevent code duplication, search for existing similar implementations across endpoints, components, services, and models before writing new code. This ensures you reuse proven patterns and maintain DRY principles.

What is the best way to find reusable code patterns before refactoring?

Finding reusable code patterns involves analyzing existing endpoints, components, services, and models to identify exact matches, close matches, and established patterns. This guides your reuse decisions without requiring extensive refactoring.

How do I enforce DRY principles in my software engineering workflow?

Enforce DRY principles by evaluating reuse options before initiating new code. Categorize matches to guide decisions—reuse existing code, extend it, extract a pattern, or follow an established pattern—to ensure consistent codebase maintainability.

Can I check for existing similar implementations before writing new code?

Yes, you can check for existing similar implementations before writing new code. Automated pattern searches scan your project to identify matching endpoints and components, presenting reuse options to prevent isolated code creation.

Why should I search for established patterns before coding a new endpoint?

Searching for established patterns before coding a new endpoint reduces maintenance burden and ensures new code adheres to proven conventions. This prevents writing code in isolation and leverages existing models.

When do I need pattern search to maintain codebase maintainability?

You need pattern search to maintain codebase maintainability whenever adding new features or endpoints. It identifies exact and close matches across services, ensuring consistent DRY code with minimal refactor.