Scan package tests, update @.claude/rules/testing.mdc with new patterns. Follow writing-skills: DRY, ultra-concise, token-efficient.

Process:

1. Glob packages/[PACKAGE]/**/*.spec.{ts,tsx}
2. Read 6-8 diverse tests: plugins, transforms, components, hooks, utils
3. Identify patterns NOT in testing.mdc:
   • Imports (ONLY mock/spyOn from bun:test - describe/it/expect are global)
   • Test organization, mocking, assertions, RTL, edge cases
4. Update testing.mdc: Add to existing sections (DRY), one example per pattern, Quick Reference if frequent
5. Report: Found X patterns → Updated Y sections

Critical:

• Only actual codebase patterns. No theoretical examples. No duplication.
• Test globals (describe, it, expect, etc.) are global via tooling/config/global.d.ts - NO imports needed
• ONLY import mock and spyOn when used

Package: Specify path (e.g., packages/media)

Claude Skill Registry (Data)

This repo contains the archived skill contents (the heavy, browsable skill files).

Canonical layout

• Category folders at repo root (e.g. development/, documents/, data/, ...)
• Each skill lives under a category: <category>/<skill>/SKILL.md + <category>/<skill>/metadata.json
• Case conflicts are resolved with {name}-{owner}-{repo} suffixes (fallback: -{short-hash}).

Archive status

• Live badges above are sourced from claude-skill-registry-core stats.json.
• Counts in this README are intentionally dynamic, not hardcoded.
• If the badges look stale, refresh the core build/index pipeline rather than editing numbers here.

Where the index + site live

• Core repo: https://github.com/majiayu000/claude-skill-registry-core
• Main repo (merged publish artifact): https://github.com/majiayu000/claude-skill-registry