bookmarks
13 bookmarks

i love prompting for a full walkthrough of a flow i.e here i had it show me all of the steps involved in oauth and found redundant steps, layout shift, and some weird ui state agents don't have to produce slop, they can also help you make great software↗

·@RhysSullivan·Sep 22, 2026·workflow·agent-software·oauth·prompting·ui-state

A prompt to stop Claude from speaking in parseltongue. “Please remove all mannered prose.”↗

·@iannuttall·Sep 2, 2026·workflow·claude·prompting

One solution is to train the AI to write like you. Specifically: 1. Ask your agent to assemble everything you've ever written. Docs + Slack + X + Other. 2. Then have it write a markdown profile on you, your style and beliefs. 3. Then when it writes, ask it to pull specific word…↗

OpenAI just dropped A TON of alpha on GPT 5.6-maxxing. it's a long document, but i pulled out the top tricks you can steal right now: 1. delete instructions from your old prompts. OpenAI's rule is to state each instruction exactly once. they found that removing repeated instruc…↗

·@itsolelehmann·Jul 11, 2026·workflow·effort-levels·gpt-5-6·pro-mode·prompting

Fable 5 has been re-released with 50% weekly usage. Copy my output-optimized Fable stack that doesn't burn tokens like crazy: > [I explain the task] > explore - scout agent (Opus, low) > plan - Fable high > [I review the plan] > implement - Fable medium > diff review - Opus hig…↗

·@robj3d3·Jul 4, 2026·workflow·agent-orchestration·claude·fable-5·prompting

TL;DR ELI5 of @trq212's new article: Claude isn't the bottleneck anymore. The stuff you forgot to tell it is. Your prompt is a map. The codebase is the actual road. Every pothole you didn't mention, Claude fills with its best guess, and the more work you hand it, the more it has…↗

New skill: /animation-vocabulary Helps you get better animations from an AI by telling it exactly what you want by using the right words. "morph", "rubber-banding", "layout animation", and more.↗

a prompt I've been using a lot recently: implement <SPEC> and while you do, keep a running implementation-notes.html file (or markdown) with decisions you had to make weren't in the spec, things you had to change, tradeoffs you had to make or anything else I should know↗