coding-principles

Name: coding-principles
Availability: InStock
Author: Lore

Surface hidden assumptions and enforce minimal, verified code changes.

Updated Aug 23, 2026

Search Tags:#planning #refactoring #quality #review #coding #principles

Ready to run

npx skills add https://github.com/lorehq/lore --skill coding-principles-lorehq

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: coding-principles
Source: https://github.com/lorehq/lore/tree/main/.lore/skills/coding-principles
Command: npx skills add https://github.com/lorehq/lore --skill coding-principles-lorehq

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The coding-principles skill helps teams avoid ambiguous requirements and overengineered solutions by surfacing assumptions early and limiting changes to what is strictly necessary.

Core Features & Use Cases

Surface Confusion Early: reveal hidden assumptions before implementing code to prevent misaligned outcomes.
Write Less Code: encourage minimal, purpose-driven implementations and avoid unnecessary abstractions.
Change Only What You Must: restrict changes to the exact scope of the request and preserve existing behavior.
Prove It Works: require tests or verifiable demonstrations before declaring work complete.
Plan, Execute, Verify: translate tasks into measurable outcomes with a clear plan and checkpoints.

Quick Start

Review a code change request and apply these principles to reduce complexity and improve clarity.

Frequently Asked Questions about coding-principles

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

FAQPage Schema

How do I surface hidden assumptions before starting feature development?▼

To surface hidden assumptions during feature development, you must reveal implicit expectations early. Enforcing explicit assumptions and creating a plan with checkpoints prevents ambiguous requirements and misaligned outcomes before implementation begins.

What is the best way to minimize unnecessary code changes during refactoring?▼

The best way to minimize unnecessary code changes during refactoring is to restrict modifications to the exact scope of the request. Preserving existing behavior and avoiding unnecessary abstractions ensures minimal, purpose-driven implementations.

How do I verify code quality and prevent overengineered solutions in code reviews?▼

To verify code quality and prevent overengineered solutions in code reviews, require tests or verifiable demonstrations before declaring work complete. This enforces explicit assumptions and limits changes to what is strictly necessary.

Does this approach to coding principles work for any software project?▼

Yes, this approach to coding principles works across software projects and teams. It applies to feature development, code reviews, and refactoring by enforcing a plan-to-verify workflow regardless of the specific platform.

Why should I require tests before marking a coding task as complete?▼

You should require tests before marking a coding task as complete to prove the implementation works. This plan-to-verify workflow ensures measurable outcomes are met and prevents implicit assumptions from creeping into code.