← ClaudeAtlas

community-ruleslisted

Community + governance discipline — code-of-conduct (Contributor Covenant v2.1 adoption; documented enforcement team + reporting paths + retaliation protection; quarterly transparency reports). Auto-fires on community/governance artifacts.
Nmor/the-claude-council · ★ 9 · Code & Development · score 69
Install: claude install-skill Nmor/the-claude-council
> Migrated 2026-06-02 from `~/.claude/rules/common/` as part of the lazy-rules-loading plan. Phase H will delete the source files to close the eager-load loop. # community-rules ## Source files migrated - `rules-library/common/code-of-conduct.md` --- <!-- ============================================================ Section: code-of-conduct.md (from rules/common/) ============================================================ --> # Code of Conduct Rule (Always-On, Global) > Auto-fires on every file. Sister to `documentation-requirements.md`, > `security.md`, `audit-logging.md`. Standards: **Contributor > Covenant v2.1** (most-adopted), **Django CoC**, **Mozilla > Community Participation Guidelines**, **Geek Feminism Anti- > Harassment Policy** (foundational). Legal: **EU EAA enforcement > context**, **US Title VII / EEOC**, **GDPR Article 6** (reporter > data lawful basis). ## Core Principle **Every collaborative codebase, community, organisation, and event has a published Code of Conduct that defines expected behaviour, named unacceptable behaviour, an enforcement mechanism, and a reporting path. The CoC is signed by every contributor (PR template includes acknowledgement); enforcement is consistent, transparent (in aggregate), and protective of reporters.** A repo without a CoC signals one of: "we don't host contributors," "we don't know what we'd do if behaviour was a problem," or "we tolerate behaviour we shouldn't." None of these is acceptable. ## Why e