dry

Identify and eliminate duplicated business logic and knowledge representations in codebases.

Updated Dec 29, 2025
One-click install
npx skills add https://github.com/AmidVoshakul/chatorai --skill dry-amidvoshakul
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dry
Source: https://github.com/AmidVoshakul/chatorai/tree/main/assets/skills/dry
Command: npx skills add https://github.com/AmidVoshakul/chatorai --skill dry-amidvoshakul

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the technical debt caused by duplicated business logic and inconsistent code patterns, which often lead to bugs and maintenance nightmares.

Core Features & Use Cases

  • Knowledge Unification: Identifies and merges redundant business rules to ensure a single source of truth.
  • Refactoring Guidance: Provides a structured approach to extracting shared logic without creating premature or overly complex abstractions.
  • Use Case: When you notice that a tax calculation logic is implemented in both the frontend and the backend, use this skill to centralize the logic into a shared module to prevent future divergence.

Quick Start

Ask the AI to review the current codebase for duplicated business logic and suggest a plan to unify it using the dry principle.

Frequently Asked Questions about dry

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

FAQPage Schema
What is the difference between superficial code duplication and semantic knowledge redundancy?

Semantic knowledge redundancy involves duplicated business rules causing logic divergence, whereas superficial syntax duplication is merely repeated code structure. This skill analyzes existing code to distinguish between them and eliminate true semantic duplication.

How do I eliminate duplicated business logic across frontend and backend codebases?

To eliminate duplicated business logic across codebases, analyze existing structures to identify shared rules and centralize them into a shared module. This skill provides refactoring guidance to unify logic and prevent future divergence.

How do I refactor duplicated code without creating overly complex abstractions?

Refactoring duplicated code without complex abstractions requires a structured approach to extract shared logic safely. This skill guides you through the extraction process to ensure a single source of truth without introducing premature architectural complexity.

When should I address technical debt from duplicated code patterns during a code review?

You should address technical debt from duplicated code patterns during code reviews when you identify inconsistent business rules that lead to maintenance issues. Use this skill to review the codebase and suggest a structured plan to unify the logic.

Can I use this approach to centralize tax calculation logic implemented in multiple places?

Yes, you can use this approach to centralize tax calculation logic implemented in multiple places. It identifies redundant business rules and merges them into a shared module to ensure a single source of truth and prevent future divergence.