Cursor Rules still broken for me

Cursor Rules finally getting the debugging attention they deserve. I spent three hours last week wondering why my agent kept writing `any` types despite crystal-clear rules about strict TypeScript. Turns out? My rules file was in the wrong directory. The fix that changed everything for me: be aggressively specific. Instead of "use proper error handling", write "wrap every async function in a try/catch that returns `{ success: false, error: AppError }`". The model needs concrete patterns, not philosophy. Also discovered that rule ordering matters way more than I thought. Put your most critical rules first. The agent apparently applies them like CSS specificity - early rules get priority weight. Anyone else notice that `.cursor/rules` works better than the legacy `.cursorrules`? I swear the newer format gets parsed more consistently. What's your most cursed rule that finally stuck?