lauren

building @cursor_ai. @reactjs compiler core team. prev @meta @netflix

[lauren @poteto]

https://t.co/XLwSDQA3d8

[lauren @poteto]

drifting into psychosis
https://t.co/HpVGjAjuCw

[Aurora Scharff @aurorascharff]

Small weekend project: Cronotype. Type a GitHub handle and find out what kind of developer you are based on when you commit. Here's mine!

https://t.co/PdTf2nmMbw

[lauren @poteto]

@kentcdodds oh interesting, how is that different from skills?

[Lee Robinson @leerob]

Some tips to help agents understand your codebase:

1. The source code either needs to be the source of truth, or have something legible as a path to the source. For example, if marketing site content is actually stored in a CMS, you need to either delete the CMS and move that content into code, or make the CMS legible through and MCP, CLI, or skill: https://t.co/zhObygzELv

2. Agents need to be able to verify their work. This includes but is not limited to: using a typed language, having high-quality and fast tests, having a well-configured linter: https://t.co/AL3eY6TBXr

3. You need to have a concise and effective AGENTS.md file, which is included in every message to your agent. Models are quite good now, so some things you can omit as the models know them. You don’t need to say the tests live inside /tests for example. It’s worth asking the models to find things in your codebase and making sure they’re named what the models might expect, otherwise consider refactoring: https://t.co/2FlVQr84nO

4. Set up automations which give you suggestions for refactoring code, catching security issues which may have slipped through code review, and optionally continuous documentation of the codebase. You can effectively create a self-driving codebase which gets better while you sleep: https://t.co/UuYL3KNTZc

[xAI @xai]

Composer 2.5 is now available inside Grok Build.

Composer 2.5 is a fast, highly intelligent model that excels on long-running tasks and following complex instructions.

[lauren @poteto]

@zpao sent you a dm

[lauren @poteto]

@SIGKITTEN @OpenAI @ajambrosino congrats!!

[lauren @poteto]

i had a similar idea, a /setup-pstack skill you can run that lets you pick which models you want for specific types of tasks (eg frontend code, backend code, systems code, prose, judgment, etc) that writes to a .cursor file. then skills can read from that. but a skill also works just as well

[lauren @poteto]

wow!

[Niklas Muennighoff @Muennighoff]

Cursor Composer 2.5 at #1 on an independent eval by @nextjs ahead of Opus 4.8 (https://t.co/da8wdcruGd)

[lauren @poteto]

@nathanclement yeah I think I have an idea for this

[John Bai @johnbai]

It's kinda crazy that you can just use multitask design mode to make a bunch of frontend UI changes, then ask for a shared link canvas with a recap of the changes in like 5 min

[lauren @poteto]

@Baconbrix legendary run!! excited to see what's next

[Cursor @cursor_ai]

Auto-review mode is now available in Cursor.

It allows agents to run tool calls with fewer approval prompts and safer execution.

[lauren @poteto]

@henryqdineen yup! i'll share more when its done

[eric zakariasson @ericzakariasson]

introducing thermos in cursor

a deep security/correctness audit and a harsh code quality audit, run in parallel on your branch, synthesized into one prioritized list

[lauren @poteto]

really like this model! try it out as your main agent in cursor along with pstack skills

[Cursor @cursor_ai]

Claude Opus 4.8 is now available in Cursor.

On CursorBench, it's able to work much more efficiently than Opus 4.7. We've also found it to be more persistent on harder tasks.

[lauren @poteto]

@dillon_mulroy nice

[Matt Pocock @mattpocockuk]

Cursor shipped a /thermo-nuclear-code-review for the TOUGHEST AI code review possible.

But is it any good? Let's dive in:

[lauren @poteto]

@JustJerry121 @stylexjs they’re one off, but since it’s such a large PR I’ve been using them to keep my branch rebased and to remigrate the changes

[lauren @poteto]

new pstack principle: https://t.co/LIwgXDSO82

this was actually a cool emergent behavior i noticed while tackling a really large refactor to @stylexjs. my agent using /poteto-mode started writing codemods and custom skills for its subagents as it tried parallelizing moving components over.

turned it into a principle, so now whenever you invoke /poteto-mode on a large enough task, your agent will build tools for itself.

[lauren @poteto]

@tomcoustols @stylexjs it should be auto updated!