engram-cultural-norms

star 4.4k

Cultural and collaboration norms for Engram contributors and agents. Trigger: Starting substantial work, reviewing changes, or defining team conventions.

Gentleman-Programming By Gentleman-Programming schedule Updated 3/7/2026

name: engram-cultural-norms description: > Cultural and collaboration norms for Engram contributors and agents. Trigger: Starting substantial work, reviewing changes, or defining team conventions. license: Apache-2.0 metadata: author: gentleman-programming version: "1.0"

When to Use

Use this skill when:

  • Starting a new feature or refactor
  • Reviewing implementation direction
  • Writing or refining project conventions

Cultural Rules

  1. Product coherence beats local cleverness.
  2. Every visible feature should feel connected to the full Engram experience.
  3. Avoid generic enterprise UI/architecture drift.
  4. Prefer explicit decisions and documented rules over tribal knowledge.
  5. Quality means behavior, naming, tests, docs, and UX all line up.

Collaboration Rules

  • Push back on fake UX and fake controls.
  • If a rule is organizational, enforce it on the server.
  • If a pattern repeats, capture it as a skill or project convention.
  • Treat design, architecture, and business rules as one system.
Install via CLI
npx skills add https://github.com/Gentleman-Programming/engram --skill engram-cultural-norms
Repository Details
star Stars 4,398
call_split Forks 518
navigation Branch main
article Path SKILL.md
More from Creator
Gentleman-Programming
Gentleman-Programming Explore all skills →