jorgesouzaRa/deep-modules
.cursor/skills/deep-modules/SKILL.md
Deep vs shallow modules (Ousterhout). Use when designing APIs, reviewing module boundaries, or when the user wants smaller interfaces with richer implementations.
development
Updated Apr 16, 2026
$ install --global
skillsauthnpx skillsauth add jorgesouzaRa/conectAPI_jira_github deep-modulesInstall 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: Apr 16, 2026, 2:57 PM23.6s1 file scanned
SKILL.md
- name:
- deep-modules
- description:
- >-
Deep Modules
From "A Philosophy of Software Design":
Deep module = small interface + lots of implementation
┌─────────────────────┐
│ Small Interface │ ← Few methods, simple params
├─────────────────────┤
│ │
│ │
│ Deep Implementation│ ← Complex logic hidden
│ │
│ │
└─────────────────────┘
Shallow module = large interface + little implementation (avoid)
┌─────────────────────────────────┐
│ Large Interface │ ← Many methods, complex params
├─────────────────────────────────┤
│ Thin Implementation │ ← Just passes through
└─────────────────────────────────┘
When designing interfaces, ask:
- Can I reduce the number of methods?
- Can I simplify the parameters?
- Can I hide more complexity inside?
Related Skills
jorgesouzaRa/tests
development
VerifiedTrustedCommunity
Good vs bad tests (integration-style, public API, behavior not implementation). Use when writing or reviewing tests, or paired with TDD and mocking skills.
SKILL.mdUpdated Apr 16, 2026
jorgesouzaRa/tdd
development
VerifiedTrustedCommunity
Test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants integration tests, or asks for test-first development.
SKILL.mdUpdated Apr 16, 2026
jorgesouzaRa/refactoring
development
VerifiedTrustedCommunity
Refactor candidates after TDD (duplication, long methods, shallow modules, etc.). Use during refactor phase of red-green-refactor or when reviewing code quality.
SKILL.mdUpdated Apr 16, 2026
jorgesouzaRa/prd-to-plan
tools
VerifiedTrustedCommunity
Turn a PRD into a multi-phase implementation plan using tracer-bullet vertical slices, saved under ./prd/PRD-NNN-feature-slug/plan.md (see prd/INDEX.md). Use when user wants to break down a PRD, create an implementation plan, plan phases from a PRD, or mentions "tracer bullets".
SKILL.mdUpdated Apr 16, 2026