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