Reducing Entropy

What it does

This skill, Reducing Entropy, aims to minimize the overall codebase size by strategically deleting or simplifying UI elements and code functions. It prioritizes achieving a smaller final codebase, even if that requires writing more code initially to achieve the reduction. The core principle is to measure the total lines of code before and after changes, favoring solutions that result in less code overall, not just reduced churn.

When to use it

• When aiming for a leaner frontend codebase.
• During refactoring or feature development where reducing complexity is desired.
• To identify opportunities to remove unnecessary features or functions.

Key capabilities

• Codebase Minimization: Focuses on reducing the total lines of code in the final product.
• Deletion-Focused Approach: Encourages identifying and removing obsolete or redundant code.
• Measurement-Driven Decisions: Requires quantifying code size before and after changes to validate effectiveness.
• Reference Mindsets: Utilizes pre-defined philosophical guidelines (loaded from references/) to inform decision-making.

Example prompts

• "Apply Reducing Entropy principles to this component: [component name]."
• "What can we delete in this function: [function name]?"
• "Analyze the codebase and suggest ways to reduce its overall size."

Tips & gotchas

• Mindset Loading Required: The skill requires loading at least one mindset from the references/ directory before use. You must list the files, read their descriptions, and explicitly load a mindset, stating which one you loaded and its core principle.
• Focus on End State: Prioritize measuring the final codebase size, not just the effort involved in making changes.
• Beware of Status Quo Bias: Avoid simply preserving existing code; actively seek opportunities for deletion.