From 4f1bd69c2a57e78b097824c9cad4e35b4dc86845 Mon Sep 17 00:00:00 2001
From: hizahizi-hizumi <163728895+hizahizi-hizumi@users.noreply.github.com>
Date: Sun, 12 Oct 2025 20:36:26 +0900
Subject: [PATCH] typo: fulfil -> fulfill

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
---
 instructions/prompt.instructions.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/instructions/prompt.instructions.md b/instructions/prompt.instructions.md
index dafc5b9..fd678a2 100644
--- a/instructions/prompt.instructions.md
+++ b/instructions/prompt.instructions.md
@@ -13,7 +13,7 @@ Instructions for creating effective and maintainable prompt files that guide Git
 - Primary references: VS Code documentation on prompt files and organization-specific conventions.
 
 ## Frontmatter Requirements
-- Include `description` (single sentence, actionable outcome), `mode` (explicitly choose `ask`, `edit`, or `agent`), and `tools` (minimal set of tool bundles required to fulfil the prompt).
+- Include `description` (single sentence, actionable outcome), `mode` (explicitly choose `ask`, `edit`, or `agent`), and `tools` (minimal set of tool bundles required to fulfill the prompt).
 - Declare `model` when the prompt depends on a specific capability tier; otherwise inherit the active model.
 - Preserve any additional metadata (`language`, `tags`, `visibility`, etc.) required by your organization.
 - Use consistent quoting (single quotes recommended) and keep one field per line for readability and version control clarity.