Welcome to the ARTPARK Hub GitHub organization.
New here? Start with our team norms — a short guide to how we coordinate across projects.
Our work is organized by project. Each project has one or more repos. See the Repositories tab for the full list.
If you've just joined:
- Read the team norms
- Ask your project lead which repos and Slack channels to join
- Set up your dev environment (instructions live in each project's README)
- Pick up a
good-first-issuefrom your project's board
Org-wide operational rules for Claude live at CLAUDE.md in the .github repo. GitHub doesn't auto-inherit CLAUDE.md — Claude Code only reads it from the current repo, so each project repo should point at the org file.
Minimal pattern — a short CLAUDE.md at the project repo's root:
# CLAUDE.md (<repo-name>)
**Org-wide rules apply first.** Before substantive work, read:
https://github.com/artpark-hub/.github/blob/main/CLAUDE.md
## Project-specific additions
<build / test commands, owners, gotchas>Or put the same pointer as a short section inside the project's README.md if you'd rather not add a separate CLAUDE.md.
Test Claude's output creatively — don't just rely on the tests Claude writes. Tests Claude writes for code Claude wrote share the same blind spots: both come from the same model of what the code is supposed to do. Push from outside — adversarial inputs, boundary cases, real (not synthetic) data, the "obviously wrong" inputs the author didn't think to handle. In review, weigh "is this actually right?" at least as much as "do the tests pass?"
Ask in #all-artpark-hub on Slack, or open an issue in the relevant project repo.
Last updated: 2026-05-19.
