dry

Detect and refactor duplicated code, UI patterns, database structures, and workflow logic.

232|43|Updated Jan 13, 2026
One-click install
npx skills add https://github.com/whawkinsiv/solo-founder-skills --skill dry-whawkinsiv
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dry
Source: https://github.com/whawkinsiv/solo-founder-skills/tree/main/skills/dry
Command: npx skills add https://github.com/whawkinsiv/solo-founder-skills --skill dry-whawkinsiv

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps eliminate duplicated code, repeated UI patterns, denormalized database structures, and copied workflow logic that increase maintenance costs and create inconsistent behavior.

Core Features & Use Cases

  • UI Deduplication: Identify near-duplicate components, repeated styles, and reimplemented library patterns.
  • Database Normalization: Detect duplicated data, missing foreign keys, inconsistent naming, and string-based lookup values.
  • Workflow Refactoring: Consolidate duplicate utilities, API handling, validation, business logic, and data transformations.
  • Use Case: Apply a quick scan after adding a feature or run a deep audit when an AI-assisted codebase has accumulated redundant components and logic.

Quick Start

Ask the dry skill to audit the codebase for duplication, propose specific refactorings, apply the appropriate fixes, and run the relevant tests.

Frequently Asked Questions about dry

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

FAQPage Schema
How do I eliminate duplicated code and simplify my codebase?

To eliminate duplicated code, you can perform a repository-wide pattern analysis to identify redundant UI components, database schemas, and workflow logic, then apply domain-specific refactorings and verify changes with build and test runs.

What is the rule of three in code refactoring and when should I apply it?

The rule of three in code refactoring is a judgment guideline used to decide when duplicated code should be consolidated. You should apply it during repository-wide pattern analysis to determine if repeated UI components or business logic require deduplication.

How do I normalize database schemas and fix denormalized structures?

Normalizing database schemas involves detecting duplicated data, adding missing foreign keys, fixing inconsistent naming, and replacing string-based lookup values. A deep audit identifies these denormalized structures to reduce maintenance costs and inconsistent behavior.

Can I run a quick code audit for duplication after adding a new feature?

Yes, you can run a quick post-feature scan to identify near-duplicate components, repeated styles, and copied workflow logic. This code audit targets newly added utilities, API calls, and data transformations to prevent redundancy early.

What is the best way to consolidate duplicate workflow logic and API calls?

The best way to consolidate duplicate workflow logic is to run a deep audit that identifies repeated utilities, API handling, validation, and business logic, then apply domain-specific refactoring to merge these patterns and run build and test verification.

Why does duplicated UI logic increase maintenance costs and cause inconsistent behavior?

Duplicated UI logic increases maintenance costs because changes must be applied across multiple near-duplicate components and repeated styles. This repetition causes inconsistent behavior when updates are missed, making UI deduplication essential for stable workflows.