implementation-standards

Name: implementation-standards
Availability: InStock
Author: patrickrmoore

Enforce defensive coding and structured error handling during the /sddp-implement phase.

Updated Mar 22, 2026

Search Tags:#architecture #standards #coding #best-practices #defensive-coding #testing-mocks

Ready to run

npx skills add https://github.com/patrickrmoore/sdd-test --skill implementation-standards-patrickrmoore

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: implementation-standards
Source: https://github.com/patrickrmoore/sdd-test/tree/main/.github/skills/implementation-standards
Command: npx skills add https://github.com/patrickrmoore/sdd-test --skill implementation-standards-patrickrmoore

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Standard patterns and practices for code implementation, ensuring consistency, safety, and maintainability across the codebase.

Core Features & Use Cases

Defensive Coding: Enforce input validation, fail-fast strategies, and explicit null-safety.
Structured Error Handling: Standardized error formats, logging, and clear failure modes.
Architectural Patterns: Clear separation of concerns via Repository and Service layers.

Quick Start

Follow these standards during the /sddp-implement phase to ensure code quality from the outset.

Frequently Asked Questions about implementation-standards

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

FAQPage Schema

What are coding standards for robust and maintainable software architecture?▼

Defensive coding prevents runtime failures by enforcing input validation, fail-fast strategies, and explicit null-safety. This approach stops invalid data early, ensuring safer code execution and reducing unexpected runtime errors.

How do I implement structured error handling across projects?▼

Structured error handling standardizes error formats, logging, and clear failure modes across teams. It provides consistent error reporting during feature development and refactoring to ensure maintainable codebases.

When do I need architectural patterns like Repository and Service layers?▼

You need Repository and Service layers when enforcing clear separation of concerns in software architecture. These patterns standardize data access and business logic, ensuring maintainable code during feature development and code reviews.

Does this coding standards skill work for team code reviews?▼

Yes, these coding standards apply directly during code reviews and refactoring across teams. They enforce defensive coding, structured error handling, and architectural patterns to maintain software quality throughout implementation.

What is the best way to standardize coding practices across multiple projects?▼

Standardizing coding practices requires enforcing defensive coding, structured error handling, and architectural patterns like Repository and Service layers. This approach ensures consistency, safety, and maintainability across all team projects.