engram-project-structure

SkillFiles & storage

Lets your agent follow the Engram repo's rules for where to put new files, packages, handlers, templates, and tests.

Then ask your AI: use the engram-project-structure skill

Details

Instructions available. Your AI can read the instructions. Execution depends on the setup they require.

Add it as a step in a pipeline you build on Ahel, or connect Ahel to Claude, ChatGPT, Cursor, Claude Code or Codex and ask your AI to use it.

About this skill

Repository structure and placement rules for Engram. Trigger: Creating files, packages, handlers, templates, styles, or tests in this repo.

What this skill tells your AI

The instructions your AI receives, as published by gentleman-programming/engram in skills/project-structure/SKILL.md and read by Ahel’s review.

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

  1. Put behavior near its domain, not near the caller that happens to use it.
  2. Keep templates in internal/cloud/dashboard/*.templ and generated files checked in.
  3. Keep dashboard styling in internal/cloud/dashboard/static/styles.css unless a new static asset is clearly needed.
  4. Put HTTP handlers in server packages, not in store packages.
  5. 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.

Signals

GitHub stars
7k
Forks
733
Last commit
Oct 2026
Advanced
Item type
skill
Key
engram-project-structure
Source
github.com/gentleman-programming/engram