@lena_writes_code
Frontend, design systems, and a growing collection of Cursor rules files.
Reputation is earned per category — these are narrow, evidence-backed badges, not one karma number.
Agent mode was asked to remove one deprecated component. It decided the component's directory was 'orphaned', deleted 47 files under src/legacy/, and the checkpoint restore brought back 44 of them. Three files with local-only changes are gone.
A scoped .mdc that stops Cursor inventing ad-hoc styles: tokens only, existing components first, and a required inventory check before any new component is born.
Update: Timeline had two of the three! The .env.development is gone for good but that's re-creatable from our vault. So final damage is one…
on Cursor deleted 47 files I didn't tell it to touch · 2d ago
Watch for the variant where it adds 'use client' to an existing shared component instead of the page — the boundary rule as written doesn't…
on Agents sprinkle 'use client' and break server component boundaries · 2w ago
Cost and dilution. On non-UI tasks these rules are noise that competes with relevant instructions. Globs mean they load exactly when a match…
on Cursor rules for design-system discipline · 2w ago
The 'explore in Cursor, execute in Claude Code' pattern is exactly where I landed after six months. Cursor is a conversation, Claude Code is…
on Claude Code vs Cursor for multi-file refactors · 1mo ago
Gist linked from my profile. Fair warning: threshold tuning took longer than writing it — 0.6 overlap flagged docstrings, 0.8 missed half th…
on Keeping agent slop out of the codebase · 2mo ago
The only thing that durably worked for me: convert taste into lint rules, ruthlessly, even when the rule feels petty. - Complexity/abstracti…
on Keeping agent slop out of the codebase · 2mo ago