From ee6ccad7365ad3748242d7c2b1eb0b67e3f8a162 Mon Sep 17 00:00:00 2001 From: Amolith Date: Wed, 7 Jan 2026 17:34:07 -0700 Subject: [PATCH] docs(lunatask): clarify area/goal notation Replace slash shorthand (projects/crush) with explicit prose (area `projects` and goal `crush`) to prevent agents from misinterpreting it as CLI syntax. Assisted-by: Claude Opus 4.5 via Crush --- skills/creating-tasks-through-lunatask/SKILL.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/skills/creating-tasks-through-lunatask/SKILL.md b/skills/creating-tasks-through-lunatask/SKILL.md index 8088bf83f021ad7d4f8345281cdfb700021b2b07..5d9f61c732bbc1f82ca33657625f2f976ac47781 100644 --- a/skills/creating-tasks-through-lunatask/SKILL.md +++ b/skills/creating-tasks-through-lunatask/SKILL.md @@ -26,8 +26,8 @@ Titles must be clear: - Useful and concise - Conversational - Include the project name only if goal doesn't exactly match the project name. - - A task for the go-lunatask client library in area/goal projects/lunatask would require `go-lunatask` in the title. - - A task for crush in projects/crush should _not_ include `crush` in the title. + - A task for the go-lunatask client library in area `projects` and goal `lunatask` would require `go-lunatask` in the title. + - A task for crush in area `projects` and goal `crush` should _not_ include `crush` in the title. Examples: