domain-layer

Validate Go domain layer entities, repositories, QueryOptions, Enums, and errors.

Updated Feb 22, 2026

Search Tags:#code quality #validation #clean architecture #go #repository #entity #domain layer

Ready to run

npx skills add https://github.com/YangTaeyoung/go-clean-arch-toolkit --skill domain-layer-yangtaeyoung

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: domain-layer
Source: https://github.com/YangTaeyoung/go-clean-arch-toolkit/tree/main/skills/domain-layer
Command: npx skills add https://github.com/YangTaeyoung/go-clean-arch-toolkit --skill domain-layer-yangtaeyoung

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill enforces strict validation and best practices for your Go project's domain layer, preventing common architectural flaws and ensuring clean, maintainable code.

Core Features & Use Cases

Entity Validation: Verifies structure, naming, and foreign key constraints for domain entities.
Interface Enforcement: Ensures Repository interfaces and QueryOption patterns are correctly implemented.
Enum & Error Standards: Checks for consistent Enum definitions and domain error structures.
Use Case: Before committing new domain models, run this Skill to automatically catch violations of your clean architecture principles, such as incorrect FK types or missing gorm.Model embeddings.

Quick Start

Run the domain-layer skill to audit all files within the internal/domain directory.

Frequently Asked Questions about domain-layer

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

FAQPage Schema

How do I validate entity structure and foreign key constraints in a Go domain layer?▼

To validate Go domain layer entities, run an audit on the internal/domain directory to automatically verify entity structures, naming conventions, and foreign key types, preventing architectural flaws before committing new models.

What is the best way to enforce repository interfaces and QueryOption patterns in Go clean architecture?▼

The best way to enforce repository interfaces and QueryOption patterns is to audit the domain layer to ensure correct implementations, catching missing structures and maintaining architectural purity before code commits.

How do I check for consistent Enum definitions and domain error standards in Go projects?▼

Check for consistent Enum definitions and domain error standards by auditing the domain layer, which automatically scans files to verify error structures and enforce architectural best practices.

Why does my Go clean architecture domain layer require disallowing external dependencies?▼

Disallowing external dependencies in the Go domain layer enforces architectural purity by ensuring the domain remains isolated, preventing framework coupling and keeping the business logic clean and maintainable.

Can I use this domain layer validation for Go projects with missing gorm.Model embeddings?▼

Yes, you can use domain layer validation for Go projects with missing gorm.Model embeddings, as the audit automatically catches these violations and guides you to correct structural implementations.

When do I need to run a domain layer audit in my Go clean architecture workflow?▼

Run a domain layer audit before committing new domain models to automatically catch violations of your clean architecture principles, such as incorrect foreign key types or missing model embeddings.