From b49e37f906536373e98ee8cd527e4902e828206f Mon Sep 17 00:00:00 2001 From: Eric Fennis Date: Fri, 9 Oct 2026 14:25:16 +0200 Subject: [PATCH] chore(copilot-instruction): Adjust instruction text to allow more then 4 use-cases (#4989) * Adjust instruction text * Revise use-case writing instructions for icons Updated guidelines for writing use-cases for icons. Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com> --------- Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com> --- .github/instructions/metadata.instructions.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/instructions/metadata.instructions.md b/.github/instructions/metadata.instructions.md index ea5753d61..a1e99a8e6 100644 --- a/.github/instructions/metadata.instructions.md +++ b/.github/instructions/metadata.instructions.md @@ -32,7 +32,7 @@ A use-case tells a reader **where and why an icon would be used in a real interf - Write each use-case as a short phrase, not a sentence. Start with a present participle verb: *Representing…*, *Indicating…*, *Marking…*, *Showing…*, *Confirming…*, *Toggling…*, *Categorizing…*, *Searching…*. - Keep it to roughly 4–12 words. One clear idea per entry. - No trailing period. No leading bullet, number, or dash (the surrounding format supplies that). -- Give each icon 1–4 use-cases, ordered most-common first. Prefer fewer strong entries over many weak or repetitive ones. +- Give each icon 1 or more use-cases, ordered most-common first. More than 4 use-cases are allowed when they are distinct and useful. Prefer fewer strong entries over many weak or repetitive ones. ### Voice