design-principles

Enforce architectural best-practice principles during software design workflows.

7|4|Updated Mar 2, 2026

Search Tags:#architecture #principles #ports-and-adapters #single-source-of-truth #design-guidance #generated-contracts

Ready to run

npx skills add https://github.com/nklisch/skills --skill design-principles-nklisch

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: design-principles
Source: https://github.com/nklisch/skills/tree/main/plugins/workflow/skills/design-principles
Command: npx skills add https://github.com/nklisch/skills --skill design-principles-nklisch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Design work often lacks consistent architectural guidance, leading to tightly coupled code, duplicated logic, and fragile interfaces.

Core Features & Use Cases

Ports & Adapters: Keep domain logic independent from infrastructure.
Single Source of Truth: Centralize variant definitions to avoid duplication.
Generated Contracts: Derive cross‑boundary contracts from a single source of truth. Apply these principles when drafting new modules, defining interfaces, or reviewing system architecture.

Quick Start

Ask the design principles skill to guide the architecture while creating a new component.

Frequently Asked Questions about design-principles

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

FAQPage Schema

What are ports and adapters in software architecture design?▼

Ports and adapters is an architectural pattern that keeps domain logic independent from infrastructure. Applying this design principle ensures your core business rules remain isolated from external systems like databases or UI frameworks.

How do I maintain a single source of truth when defining software interfaces?▼

To maintain a single source of truth, centralize your variant definitions to avoid duplication. This architectural principle prevents conflicting logic by ensuring all components derive their data from one authoritative location.

What is the best way to generate cross-boundary contracts for system modules?▼

The best way to generate cross-boundary contracts is to derive them directly from your single source of truth. This architectural approach guarantees that all system boundaries receive consistent, synchronized interface definitions.

Can I apply architectural principles to review existing system boundaries?▼

Yes, you can apply architectural principles to review existing system boundaries. Evaluating your modules against ports and adapters guidelines helps identify tightly coupled code and fragile interfaces during design and implementation workflows.

Why does tightly coupled code occur during module design?▼

Tightly coupled code occurs during module design when consistent architectural guidance is lacking. Without applying single source of truth principles, duplicated logic and fragile interfaces easily infiltrate your system boundaries.