docs(rfc): rename rfcs/ to rfc/

.claude/plans/README.md

@@ -20,7 +20,7 @@ This directory contains:
 
 ## What Doesn't Belong Here
 
-Design proposals and architectural decisions belong in `/rfcs`. This directory is for **how** to implement, not **what** or **why**.
+Design proposals and architectural decisions belong in `/rfc`. This directory is for **how** to implement, not **what** or **why**.
 
 ## Compaction Rule
 
@@ -60,7 +60,7 @@ Plans may link to their parent RFC:
 ```markdown
 # Implementing Feature X
 
-**RFC:** [/rfcs/feature-x.md](/rfcs/feature-x.md)
+**RFC:** [/rfc/feature-x.md](/rfc/feature-x.md)
 
 ## Tasks
 

.claude/skills/git/references/scope.md

@@ -14,7 +14,7 @@ Infer commit scope from changed file paths.
 | `packages/react-native/` | `react-native` |
 | `packages/icons/`        | `icons`        |
 | `site/`                  | `site`         |
-| `rfcs/`                  | `rfc`          |
+| `rfc/`                   | `rfc`          |
 | `.claude/`               | `claude`       |
 | `.github/workflows/`     | `ci`           |
 | `.github/`               | `cd`           |

CLAUDE.md

@@ -479,7 +479,7 @@ add(cleanup: CleanupFn): void { ... }
 
 | Location         | Purpose                                                           |
 | ---------------- | ----------------------------------------------------------------- |
-| `rfcs/`          | Design proposals, API decisions, architecture — public discussion |
+| `rfc/`           | Design proposals, API decisions, architecture — public discussion |
 | `.claude/plans/` | Implementation notes, AI-agent context, working drafts            |
 
 **RFCs** focus on **what** and **why**. Write an RFC for major API changes, architectural decisions, or patterns used across packages.

CONTRIBUTING.md

@@ -174,7 +174,7 @@ When your changes introduce new patterns:
 
 ## RFCs (Design Documents)
 
-For significant architectural decisions and API designs, we use RFCs (Request for Comments). See [`rfcs/README.md`](./rfcs/README.md) for the full process.
+For significant architectural decisions and API designs, we use RFCs (Request for Comments). See [`rfc/README.md`](./rfc/README.md) for the full process.
 
 **When to write an RFC:**
 

README.md

@@ -58,7 +58,7 @@ Please see our [contributing guide](./CONTRIBUTING.md) for getting setup locally
 Please note that this project is released with a [Contributor Code of Conduct][coc]. By
 participating in this project you agree to abide by its terms.
 
-[rfcs]: ./rfcs
+[rfcs]: ./rfc
 [v10-discussion]: https://github.com/videojs/video.js/discussions/9035
 [heff-presentation]: https://players.brightcove.net/3737230800001/eyILA5XG7K_default/index.html?videoId=6379311036112
 [coc]: https://github.com/videojs/video.js/blob/main/CODE_OF_CONDUCT.md

rfc/README.md

@@ -63,7 +63,7 @@ implementation-plan: .claude/plans/example.md
 ## Directory Structure
 
 ```
-rfcs/
+rfc/
 ├── README.md           # This file
 ├── feature-name.md     # Single-file RFC
 └── feature-name/       # Multi-file RFC