engram-cultural-norms

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.