engram-cultural-norms
SkillAI & modelsLets your agent follow Engram project conventions when starting work, reviewing changes, or writing team rules.
Then ask your AI: use the engram-cultural-norms skill
Details
Instructions available. Your AI can read the instructions. Execution depends on the setup they require.
Account requirements not reviewed. Check the skill instructions before use; Ahel provides instructions and does not run this skill.
No other account needed.
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
Cultural and collaboration norms for Engram contributors and agents. Trigger: Starting substantial work, reviewing changes, or defining team conventions.
What this skill tells your AI
The instructions your AI receives, as published by gentleman-programming/engram in skills/cultural-norms/SKILL.md and read by Ahel’s review.
When to Use
Use this skill when:
- Starting a new feature or refactor
- Reviewing implementation direction
- Writing or refining project conventions
Cultural Rules
- Product coherence beats local cleverness.
- Every visible feature should feel connected to the full Engram experience.
- Avoid generic enterprise UI/architecture drift.
- Prefer explicit decisions and documented rules over tribal knowledge.
- 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.
Signals
- GitHub stars
- 7k
- Forks
- 733
- Last commit
- Oct 2026
Advanced
- Item type
- skill
- Key
engram-cultural-norms- Source
- github.com/gentleman-programming/engram
github.com/gentleman-programming/engram