Proposal: Optional project-level context files for team-specific skill customization

Love this repo, thanks for sharing!

One thing I've noticed using skills like these across projects: the same skill often needs different conventions per team: PR size limits, legacy directory handling, test framework choices, etc. Right now that means forking the skill, which drifts from upstream.

**A pattern that's worked for me:** an optional context file in the *project* that the skill reads at runtime.

```
my-project/.claude/skills/code-review/PROJECT_CONTEXT.md
```

If it exists, the skill picks up project-specific rules. If not, it runs with defaults (same as today). Example for `code-review-and-quality`:

```markdown
## Review Standards
- Max PR size: 400 lines
- Legacy directories (safety only, not style): src/legacy/, lib/compat/
- PRs touching src/api/ require integration tests

## Team Conventions
- Conventional commits — verify PR title format
- No default exports in TypeScript
```

Skills stay generic and updatable. Context file makes them project-aware. No new tooling, just a convention in the skill anatomy spec and one skill updated as proof of concept.

Happy to draft a PR if there's interest.