gentleman-programming/engram-project-structure
skills/project-structure/SKILL.md
Repository structure and placement rules for Engram. Trigger: Creating files, packages, handlers, templates, styles, or tests in this repo.
$ install --global
skillsauthnpx skillsauth add gentleman-programming/engram engram-project-structureInstall 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 25, 2026, 11:49 AM10.2s1 file scanned
SKILL.md
- name:
- engram-project-structure
- description:
- >
- Repository structure and placement rules for Engram. Trigger:
- Creating files,
- license:
- Apache-2.0
- author:
- gentleman-programming
- version:
- 1.0
When to Use
Use this skill when:
- Creating a new package, file, or directory
- Deciding where code belongs
- Adding tests, templates, assets, or docs
Placement Rules
- Put behavior near its domain, not near the caller that happens to use it.
- Keep templates in
internal/cloud/dashboard/*.templand generated files checked in. - Keep dashboard styling in
internal/cloud/dashboard/static/styles.cssunless a new static asset is clearly needed. - Put HTTP handlers in server packages, not in store packages.
- Put persistence queries in store/cloudstore, not in handlers.
File Creation Rules
- New route -> handler + tests in dashboard/server package
- New DB behavior -> store/cloudstore code + focused tests
- New UI partial/page -> templ component + generated
_templ.go - New contributor guidance -> update docs/catalog in same change
Anti-Patterns
- Do not mix SQL, HTML, and transport logic in one file.
- Do not create utility packages for one-off helpers.
- Do not add package layers unless they remove real coupling.
Related Skills
gentleman-programming/engram-memory
testing
VerifiedTrustedCommunity
ALWAYS ACTIVE — Persistent memory protocol. You MUST save decisions, conventions, bugs, and discoveries to engram proactively. Do NOT wait for the user to ask.
3,507SKILL.mdUpdated Apr 25, 2026
gentleman-programming/engram-visual-language
testing
VerifiedTrustedCommunity
Visual language rules for Engram surfaces. Trigger: Any dashboard styling, typography, spacing, or visual identity change.
2,810SKILL.mdUpdated Apr 25, 2026
gentleman-programming/engram-ui-elements
data-ai
VerifiedTrustedCommunity
Creation rules for Engram UI elements, pages, cards, metrics, and detail flows. Trigger: Adding or changing dashboard UI components or connected browsing flows.
2,810SKILL.mdUpdated Apr 25, 2026
gentleman-programming/engram-tui-quality
testing
VerifiedTrustedCommunity
Bubbletea/Lipgloss quality rules for Engram TUI. Trigger: Changes in model, update, view, navigation, or rendering.
2,810SKILL.mdUpdated Apr 25, 2026