@dshukertjr — Cursor now supports file-type specific rules
Cursor now lets you define multiple rules!
You can have Cursor automatically apply certain rules for certain file types!
I created a rule for .sql files to follow the SQL format we use at Supabase. You can find it in our repo.
What other example rules should we create?
Smart move from the Cursor team. Scoping rules to file types means your SQL conventions don't bleed into your TypeScript, and you can encode project-specific patterns (naming, structure, linting intent) right where they apply. The Supabase SQL rule in their repo is a concrete starting point if you want to see the format.
@kevinkern — Guide to .cursor/rules in Cursor 0.45
Understanding new .cursor/rules in 0.45
I've seen so many people struggling with .cursorrules and with the new .cursor/rules directory.
Here is a Guide for you! 🧵
That's the companion read to the post above. The migration from .cursorrules (single flat file) to .cursor/rules (directory of scoped rule files) tripped up a lot of people when 0.45 dropped. This thread clarifies what changed and how to structure your rules directory. Worth bookmarking alongside the Supabase example.
@tom_doerr — AI-powered search engine with generative UI
AI-powered search engine with generative UI
Honestly just saved this one so I don't forget it exists. An open-source search engine that generates its UI dynamically based on what it finds — results that look like dashboards, comparisons, or structured cards rather than a flat list of blue links. The "generative UI" framing is interesting because it puts rendering logic in the model's hands, not the template's. Could easily see this pattern showing up in internal tooling.
@semrush — SEO content brief, step by step
How to create an SEO content brief:
- Choose the right target keyword
- Make a list of secondary keywords
- Conduct a SERP analysis
- Create your tentative outline
- Make a list of internal links to include
Learn more here ⬇️ https://social.semrush.com/40R0fSH
It's a Semrush tweet so take the framing with some salt, but the process itself is sound. The part most people skip is step 5 — internal links at brief stage, not as an afterthought in the editor. Capturing them early means you structure the piece to actually connect to your existing content rather than retrofitting links in.
@bynneh — UI layout composition coming together
All the pieces are falling into place.
The 4 screenshots show a dashboard UI with a clean grid, tight spacing, and a coherent color system clicking into place across different component states. No commentary from the author, which makes it feel more like a progress log than a launch announcement. The composition is worth studying — particularly how the card hierarchy handles density without feeling cluttered.
@elayadesigns — Pricing page design reference
Pricing design ✌🏻
Good pricing page execution. Clean tier differentiation, the "recommended" callout doesn't shout, and the feature comparison beneath the plans is scannable without being a wall of checkboxes. Saved as a reference for the next time I have to build one of these.
