luisdavidtf/clean-arch
skills/clean-arch/SKILL.md
Guidelines for Domain-Driven Design and Clean Architecture dependency rules. Trigger: When creating new UseCases, Repositories, or planning module structure.
documentation
Updated Jun 8, 2026
$ install --global
skillsauthnpx skillsauth add luisdavidtf/vindex clean-archInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jun 8, 2026, 6:09 AM7.4s1 file scanned
SKILL.md
- name:
- clean-arch
- description:
- >
- Trigger:
- When creating new UseCases, Repositories, or planning module structure.
- license:
- Apache-2.0
- author:
- fontstock-arch
- version:
- 1.0
- scope:
- [root, data, domain]
- auto_invoke:
- Connecting UI to Business Logic
- allowed-tools:
- Read, Edit, Write, Glob, Grep, Bash, WebFetch, WebSearch, Task
Core Principles
- Dependency Rule: Source code dependencies always point inwards.
- Data/Presentation -> Domain
- Domain -> NEVER DEPENDS ON ANYTHING
- Separation of Concerns: Business logic is isolated from UI and DB details.
Layers
1. Domain (The Core)
- Entities: Pure TypeScript classes or interfaces representing business objects.
- Use Cases: Application-specific business rules.
- Repository Interfaces: Abstract definitions of how to access data.
2. Data (The Gateway)
- Implementations: Concrete implementations of Repository Interfaces.
- Data Sources: APIs, Databases, Local Storage.
- Mappers: Transform data models (DB schema) into Domain Entities.
3. Presentation (The UI)
- ViewModels/Hooks: Connect UI to Use Cases.
- Views: React Components that render state.
CRITICAL RULES
1. No Frameworks in Domain
- NEVER import from
react,react-native, ordrizzle-ormin thesrc/domainfolder. - ALWAYS keep the Domain pure.
2. Dependency Injection
- ALWAYS inject dependencies (like repositories) into Use Cases via constructor or factory function.
3. Repository Pattern
- ALWAYS define the interface in Domain (
domain/repositories/IUserRepository.ts). - ALWAYS implement it in Data (
data/repositories/UserRepositoryImpl.ts).
Related Skills
luisdavidtf/zustand-store
documentation
VerifiedTrustedCommunity
Guidelines for global state management with Zustand. Trigger: When creating global stores, shared UI state, or managing session data.
SKILL.mdUpdated Jun 8, 2026
luisdavidtf/typescript
development
VerifiedTrustedCommunity
TypeScript strict patterns and best practices. Trigger: When implementing or refactoring TypeScript in .ts/.tsx (types, interfaces, generics, const maps, type guards, removing any, tightening unknown).
SKILL.mdUpdated Jun 8, 2026
luisdavidtf/react-native-style
development
VerifiedTrustedCommunity
Guidelines for styling in React Native (Flexbox, StyleSheet). Trigger: When styling components, fixing layout issues, or adding visual effects.
SKILL.mdUpdated Jun 8, 2026
luisdavidtf/learning-loop
testing
VerifiedTrustedCommunity
Protocol for QA, error verification, and skill evolution to prevent recurring bugs.
SKILL.mdUpdated Jun 8, 2026