Code of Conduct

June 26, 2026 · View on GitHub

HeyClaude is a public contribution space for useful Claude and AI workflow resources. The standard is simple: be direct, useful, and respectful.

Expected behavior

  • Keep issues and PRs focused on improving the directory.
  • Give actionable feedback and assume maintainers are balancing quality, safety, and review bandwidth.
  • Credit original sources and avoid passing off someone else's work as your own.
  • Disclose affiliation, sponsorship, affiliate links, or commercial interest when relevant.
  • Respect maintainer decisions about scope, safety, policy, and category fit.

Unacceptable behavior

  • Harassment, threats, hate speech, personal attacks, or targeted abuse.
  • Spam submissions, low-effort reward farming, or attempts to manipulate contribution scoring.
  • Plagiarism — copying another contributor's submission, PR, or work and passing it off as your own, including duplicated or lightly reworded copies filed under a different account.
  • Repeatedly reopening closed submissions without new evidence.
  • Submitting malware, deceptive packages, credential-harvesting instructions, or intentionally unsafe content.
  • Manipulating the review bot or automated gate — embedding hidden or misleading instructions in submissions, PR titles/bodies, file contents, or commit messages to influence the automated review (prompt injection).
  • Circumventing validation or the review gate — faking checks, or editing automation/CI to skip required validation.
  • Abusing system resources — spam floods, deliberately triggering expensive re-reviews, or attempts to exhaust the review bot's compute or credits.
  • Publishing private information, secrets, tokens, or non-public data.

Enforcement

Maintainers may edit, hide, close, lock, or delete issues, comments, PRs, and discussions that violate this code of conduct. Maintainers may also block users from participating in the project.

Enforcement is proportional and escalates with intent and repetition. Opening your own issue and then submitting a PR that resolves it is welcome, and a PR with no linked issue is fine — neither is farming. Off-scope or low-effort submissions are closed or relabeled, with no further penalty. Reward-farming is against policy: using more than one account under the same person's control (alt / sock-puppet accounts) — for example, one account opening issues for another account to "resolve" — or manufacturing low-value issues and bulk point-chasing submissions to inflate contribution credit; linked issues from farming are closed so the work earns no bonus credit and a warning is issued, with continued or any confirmed multi-account farming closed on sight and blocked. Plagiarism and ban-evasion — copying another contributor's work, or returning under a new account after a block — result in an immediate permanent block from contributing across all of our repositories (JSONbored/gittensory, JSONbored/metagraphed, JSONbored/awesome-claude).

By submitting, you affirm the work is your own original work and that you have the right to contribute it under this repository's license. Contributing is not an entitlement, and all decisions — merge, close, scope, policy, timing, labels, and blocks — are at maintainer discretion and final.

Security-sensitive reports should follow SECURITY.md, not public exploitation — report issues privately rather than weaponizing them in a submission; good-faith research is welcome through that channel. Other conduct concerns can be raised through a GitHub issue or discussion if it is safe to do so.

Maintainer decisions should be proportional to the issue and focused on keeping the project useful, safe, and reviewable.