engram-cultural-norms
Cultural and collaboration norms for Engram contributors and agents. Trigger: Starting substantial work, reviewing changes, or defining team conventions.
64
Quality
76%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Securityby
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./skills/cultural-norms/SKILL.mdWhen 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.
- Repository
- Gentleman-Programming/engram
- Commit
763a6ba
- Last updated
- First committed
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.