[yzhangcs]

Summary

Organize repository skills into concise task guides and make CONTRIBUTING the shared source for documentation and test conventions. Documentation should state its scope, group related guidance, and use consistent terminology. Test changes should follow nearby FLA conventions and extend existing parameterized cases before adding functions or files.

Follows merged #1223. The diff contains only 17 Markdown files; runtime code, tests, CI, and profiling scripts are unchanged. Numerical, synchronization, dispatch, and public compatibility constraints remain in the guides.

Test plan

Validated candidate 3e92e0dc against main b3d7bc99:

• Reviewed all nine skill entry points, their workflow references, the skill index, contribution guidance, and affected README text for organization, consistency, and current implementation paths.
• All nine skills passed skill-creator/scripts/quick_validate.py. Across 20 documentation files, checked 161 local links/anchors, 27 code paths, 15 Python/shell snippets, and nine skill tables; all four reference symlink targets exist.
• Checked the documented profiler options, benchmark gate behavior, KDA gate contracts, and backend registration against repository code; checked Gluon barrier arguments against installed Triton source.
• Pre-commit and git diff --check passed. Linked operator references are unchanged; their excerpts and accelerator examples were not executed. No GPU/NPU runtime validation is needed for this documentation-only diff.

Benchmark / NCU

N/A: no runtime, kernel, or performance-relevant code changes.

Breaking changes

None. Public APIs, numerical tolerances, checkpoint compatibility, and backend behavior are unchanged.

Checklist

• I have read CONTRIBUTING.md and follow its conventions (code style, docstrings, commit prefixes).
• I have read AGENTS.md and, where my change matches its scope, the relevant skill under .agents/skills.
• Dependent tests pass locally or in CI, and new behavior is covered by tests where applicable (tick as N/A for changes with no testable code, e.g. docs-only).
• Kernel changes include same-hardware before/after benchmark numbers, dense + varlen where applicable (tick as N/A when no kernel code changed).
• This PR is minor/cosmetic-only (typo, formatting, style-only tweaks) — tick only if it is, and justify below.
• I understand this PR exceeds 500 changed lines and have explained its single purpose and why it should stay together below.

Large PR justification

The skills form one workflow: design the contract, establish coverage, optimize with a fixed gate, and prepare evidence. Removing overlap across the guides together keeps each responsibility clear. Most changes delete repeated material. Review the index and contribution rules, then the individual guides and their focused references.