coding-effectively

Enforce context-aware coding discipline separating pure logic from side effects.

13|Updated Jan 18, 2026

Search Tags:#testing #refactoring #coding #context-awareness #design-principles #software-engineering #defensive-programming

Ready to run

npx skills add https://github.com/pbdeuchler/llm-plugins --skill coding-effectively-pbdeuchler

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: coding-effectively
Source: https://github.com/pbdeuchler/llm-plugins/tree/main/plugins/house-style/skills/coding-effectively
Command: npx skills add https://github.com/pbdeuchler/llm-plugins --skill coding-effectively-pbdeuchler

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enforces context-aware coding discipline to improve consistency, readability, and maintainability across projects.

Core Features & Use Cases

ALWAYS REQUIRED: Separate pure logic from side effects and promote defensive data handling; leverage contextual sub-skills to support different languages and runtimes.
CONDITIONAL: Apply sub-skills for PostgreSQL integration, testing, and property-based thinking when appropriate.
Design Guidance: Emphasize property-driven design, pragmatic incrementalism, and robust error handling to guide engineering decisions.

Quick Start

Apply this skill when starting a feature or refactoring to ensure clean separation of concerns and defensible coding choices.

Frequently Asked Questions about coding-effectively

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

FAQPage Schema

How do I separate pure logic from side effects when refactoring code?▼

To separate pure logic from side effects during refactoring, enforce context-aware coding discipline that isolates functional operations from external state modifications. This approach improves consistency, readability, and maintainability across projects by applying defensive data handling.

What are the best design principles for maintaining consistency across software projects?▼

Design principles for maintaining consistency include property-driven design, pragmatic incrementalism, and robust error handling. These guidelines enforce context-aware coding discipline, ensuring defensible engineering decisions and clean separation of concerns across different languages and runtimes.

How do I apply defensive programming and property-based thinking to my testing workflow?▼

Apply defensive programming and property-based thinking to testing workflows by utilizing conditional sub-skills that support robust error handling. This integration ensures defensible coding choices and validates pure logic separation during feature development and refactoring.

Does this coding discipline approach work with PostgreSQL integration and different runtimes?▼

Yes, this coding discipline works with PostgreSQL integration and different runtimes by leveraging contextual sub-skills. It applies conditionally to database work, ensuring defensive data handling and clean separation of concerns across diverse language environments.

When should I use context-aware coding skills for feature development?▼

Use context-aware coding skills when starting a feature or refactoring to ensure clean separation of concerns and defensible coding choices. This approach enforces discipline for consistency, readability, and maintainability across projects.

Why does separating pure logic from side effects improve code maintainability?▼

Separating pure logic from side effects improves code maintainability by enforcing context-aware coding discipline that isolates functional operations. This separation, combined with defensive data handling, ensures consistency and readability across diverse software projects.