|
|
@@ -12,8 +12,11 @@ Your output must be:
|
|
|
</task>
|
|
|
|
|
|
<rules>
|
|
|
+- Title must be grammatically correct and read naturally - no word salad
|
|
|
+- Never include tool names in the title (e.g. "read tool", "bash tool", "edit tool")
|
|
|
- Focus on the main topic or question the user needs to retrieve
|
|
|
-- Use -ing verbs for actions (Debugging, Implementing, Analyzing)
|
|
|
+- Vary your phrasing - avoid repetitive patterns like always starting with "Analyzing"
|
|
|
+- When a file is mentioned, focus on WHAT the user wants to do WITH the file, not just that they shared it
|
|
|
- Keep exact: technical terms, numbers, filenames, HTTP codes
|
|
|
- Remove: the, this, my, a, an
|
|
|
- Never assume tech stack
|
|
|
@@ -29,8 +32,12 @@ Your output must be:
|
|
|
<examples>
|
|
|
"debug 500 errors in production" → Debugging production 500 errors
|
|
|
"refactor user service" → Refactoring user service
|
|
|
-"why is app.js failing" → Analyzing app.js failure
|
|
|
-"implement rate limiting" → Implementing rate limiting
|
|
|
-"how do I connect postgres to my API" → Connecting Postgres to API
|
|
|
+"why is app.js failing" → app.js failure investigation
|
|
|
+"implement rate limiting" → Rate limiting implementation
|
|
|
+"how do I connect postgres to my API" → Postgres API connection
|
|
|
"best practices for React hooks" → React hooks best practices
|
|
|
+"@src/auth.ts can you add refresh token support" → Auth refresh token support
|
|
|
+"@utils/parser.ts this is broken" → Parser bug fix
|
|
|
+"look at @config.json" → Config review
|
|
|
+"@App.tsx add dark mode toggle" → Dark mode toggle in App
|
|
|
</examples>
|
Aiden Cline