engram-project-structure

Repository structure and placement rules for Engram.

IndexedApache-2.0★ 7,588

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/gentleman-programming-engram-project-structure

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

About

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

Reviews

Write a review

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools: No tools found
Secrets: None asked for
Install scripts: None found

Network hosts it talks to 1

codeload.github.com · found in install command

Files it touches

~/.claude/skills/engram-project-structure

What's inside

Skill name: engram-project-structure
Description: Repository structure and placement rules for Engram. Trigger: Creating files, packages, handlers, templates, styles, or tests in this repo.
License: Apache-2.0
Metadata: author: gentleman-programming · version: 1.0
Instructions: 35 lines in SKILL.md · view on GitHub

Agent Skills spec issues

name: "engram-project-structure" does not match folder "project-structure"

Files (1)

SKILL.md

SKILL.md (first lines)

## 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.

From Gentleman-Programming/engram, Apache-2.0.

Signals

Stars: 7,588
Forks: 791
Open issues: 73
Last commit (this folder): Mar 7, 2026 (7 months ago)
Last release: Oct 23, 2026 (4 days ago)

From GitHub (fetched Oct 24, 2026).

Details

Version: 1.0
License: Apache-2.0
Repository: github.com/Gentleman-Programming/engram
Website: engram.gentlemanprogramming.com/
First seen: Oct 24, 2026
Last checked: Oct 24, 2026
Source: GitHub github-graphql

More from gentleman-programming

Cite this page

engram-project-structure skill. Agent Mart. https://agentmart.dev/skills/gentleman-programming-engram-project-structure (last updated 2026-10-24)