Name: engram-project-structure
Author: devopstales

Imported from devopstales/skillgrid (.agents/skills/engram-project-structure/SKILL.md). Install upstream with npx skills add devopstales/skillgrid --skill engram-project-structure. Copyright stays with the author (Apache-2.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/*.templ and generated files checked in.
Keep dashboard styling in internal/cloud/dashboard/static/styles.css unless 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.

{ "ocm": "1", "id": "devopstales-skillgrid-engram-project-structure", "kind": "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.", "publisher": "devopstales", "version": "1.0.0", "capabilities": { "domains": [ "coding" ], "tags": [ "skill-md", "github" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "Repository structure and placement rules for Engram. Trigger: Creating files, packages, handlers, templates, styles, or tests in this repo." ], "primary": false, "metadata": { "source": { "provider": "github", "repository": "https://github.com/devopstales/skillgrid", "path": ".agents/skills/engram-project-structure/SKILL.md", "ref": "8b9fbdc6a0c764ef2d1db23c06bef5b1ba9fa6f3", "url": "https://github.com/devopstales/skillgrid/blob/8b9fbdc6a0c764ef2d1db23c06bef5b1ba9fa6f3/.agents/skills/engram-project-structure/SKILL.md", "key": "devopstales/skillgrid/.agents/skills/engram-project-structure/SKILL.md" }, "license": "Apache-2.0" }, "instructions": "## When to Use\n\nUse this skill when:\n- Creating a new package, file, or directory\n- Deciding where code belongs\n- Adding tests, templates, assets, or docs\n\n---\n\n## Placement Rules\n\n1. Put behavior near its domain, not near the caller that happens to use it.\n2. Keep templates in `internal/cloud/dashboard/*.templ` and generated files checked in.\n3. Keep dashboard styling in `internal/cloud/dashboard/static/styles.css` unless a new static asset is clearly needed.\n4. Put HTTP handlers in server packages, not in store packages.\n5. Put persistence queries in store/cloudstore, not in handlers.\n\n---\n\n", "cost": { "context_tokens": 267 } }

engram-project-structure

About

When to Use

Placement Rules

File Creation Rules

Anti-Patterns

Use it

Manifest

Reviews