superical

[cryptoshant🇮🇳 @cryptoshan484]

To find subdomains you can use this new technique:

https://t.co/OAAowvtwaT

[Meng To @MengTo]

I open-sourced ThreeUI, my library of three.js components and landing pages.

160+ are free, and the tool is free too. It includes procedural 3D hero sections, icons, and motion designs. Copy the prompt or source, give it to your agent, then change the theme, lighting, motion or layout.

Live site: https://t.co/rtCfqeZnOP

Repo: https://t.co/B66ahgxHVl

I'm adding a lot more soon. Pro comes with 50+ extra components, MCP, and skills. Early adopters get 50% off right now.

[Travis Street @travisstreet_]

wtf this is crazy: https://t.co/C3ot23hAUs

[Guillaume Meyer @guillaumemeyer]

🧹watermarks-remover now supports watermarks from OpenAI and Gemini in addition to Claude.
https://t.co/OxSdnAjEGe

[Chris Tate @ctatedev]

Introducing drag and drop in Native SDK

Make any UI element draggable

TypeScript + markup. No JS runtime.

[Abraham John 🦄🦓 @Abmankendrick]

UI/UX Designers, this might be one of the best tools for color palette inspiration.

Happy Hues gives you curated color palette ideas displayed on real website examples, so you can instantly see how colors work together before designing.

Bookmark it for later 💜

[gianmarco simone ✨ @ggsimm]

Don't let your node UIs become spaghetti, embrace cable management

[Aniket Pawar @alaymanguy]

I just came across something really useful for design engineers.

So many great tools in there...

https://t.co/EeV1rrWUAt

[Arek @arknow91]

block-to-block connection

[Jakub Antalik @Jakubantalik]

More types added to the Thinking Orbs library.
Large and small sizes, light & dark mode, playground, zero dep

https://t.co/PdGxwi6cGU
npm install thinking-orbs

Huge shoutout to @a_brinza who also worked on this

[CJ Zafir @cjzafir]

Introducing https://t.co/DPZQATF63w

A self-improving loop that fixes your existing and all new skills (SKILL.md) with custom evals.

Results: Tuned-skills improve model performance by 15-20% on average.

> works with all harnesses
> works with all models
> no credits required
> runs locally

Try it today.

[ani @anaisbetts]

I can't remember who said this trick, but it is now trivially easy to make APIs and MCP servers for websites:

1. Go to the site
2. Turn on DevTools => Network tab => "Keep Log"
3. Log out and log back in
4. Visit all the pages you want data from

(cont.)

[Nav Toor @heynavtoor]

Apple's product pages have that scroll effect. The camera flies through a 3D world. Products float. Scenes transition. No cuts. One continuous flight driven by your scroll wheel.

Here is what one costs to build in 2026.

Big storytelling agencies (Noomo, WithLore, Utsubo): $15,000 to $100,000. Three to six months. A team of designers, 3D artists, and WebGL developers.

Awwwards-tier flagship from a senior freelancer: $8,000 minimum.

Three.js multi-scene site with GSAP scroll: $3,500 to $8,000.

That is if you can find a Three.js specialist. They charge $75 to $150 an hour. There are fewer of them than there are brands that want the site.

Now meet scroll-world.

A free, open-source agent skill for Claude Code and Codex that generates the entire thing from a prompt.

Describe your brand. Describe the scenes. "A coffee brand. Start outside the farm. Fly into the roasting facility. Pass through the packaging. Land in the cafe."

It generates the isometric stills. It generates the camera flights. It generates the connector clips between scenes from the actual boundary frames of both neighbors, so every seam is pixel-identical. No flicker. No cut. One continuous flight.

Then it wires the chain into a portable vanilla JS scroll engine that drops into plain HTML, Next.js, or Vue.

One prompt. Hours. Not months.

6,096 stars on GitHub in 25 days. 724 forks. MIT license. Built by cyw, founder and CTO of Hermai AI, out of San Francisco.

Here is what scroll-world does:

- Interviews you on brand, scenes, art direction, and budget before spending a cent
- Generates the isometric stills through GPT Image 2
- Generates the camera flights through Seedance on Monid
- Renders a native 9:16 portrait chain for mobile, not a crop
- Ships a vanilla JS scrub engine with blob-seek, lazy load, and seam crossfade
- Installs into Claude Code as a plugin or Codex through the Vercel skills CLI
- Framework-agnostic

Here is what scroll-world costs to install:

Zero. Forever.

Generation burns credits. A 6-scene 1080p chain on Monid pay-per-clip lands around $27, printed before the run starts.

Big storytelling agency: $15,000 to $100,000. scroll-world: $27.
Awwwards WebGL flagship: $8,000. scroll-world: $27.
Three.js contractor for a month: $12,000. scroll-world: this afternoon.

Your brand. Your world. Your scroll.

100% Open Source. (Link in the comments)

[Puneet Patwari @system_monarch]

1) Load Balancing: https://t.co/IytjJseO11

2) CDN: https://t.co/xxzUuwV5GD

3) Caching: https://t.co/QvyGIyKNHM

4) Cache Invalidation: https://t.co/FyDLJWZVOE

5) Rate Limiting: https://t.co/auDKgPpLeA

6) API Gateway: https://t.co/H1y0htWDub

7) CAP Theorem: https://t.co/AglSd993oa

8) Sharding: https://t.co/HT316hgoEr

9) Replication: https://t.co/NXessCjYp4

10) Partitioning: https://t.co/01bpFCZBhZ

11) Queues: https://t.co/Lenx1Pfw95

12) Microservices: https://t.co/Hx9Yn2yRBw

13) Microservices Vs Monoliths: https://t.co/g9lGFHydVj

14) Fault Tolerance: https://t.co/jCJk6d52z2

15) Database Scaling: https://t.co/h7pYha8x6x

16) Service Discovery: https://t.co/vEDMvhWYj5

17) Consistency models: https://t.co/cb3zNtdZNA

18) Eventual Consistency: https://t.co/aFjL3flHNY

19) Distributed Transactions: https://t.co/s0ZWdtTqiW

20) Leader Election: https://t.co/IxrWO9AvB3

21) Horizontal vs Vertical Scaling: https://t.co/I8CH64dL5l

22) Back of the Envelope Estimation: https://t.co/gyatcqpaqO

23) Idempotency, Data Latency & Finale: https://t.co/fNArLx4MrW

[Jamon @jamonholmgren]

I'm just going to dump my whole agentic setup out here, because I see too many people missing giant chunks of this and it's hurting them.

Here's what I have and recommend:

0. an AGENTS.md that is a router -- it sends the agent to the right skills, docs, tools

1. a standard workflow doc/skill customized to my needs ... (grab Matt Pocock skills if you don't already have something) ... I tag this in most sessions with `@/AGENT_WORKFLOW.md` and it pulls it in.

2. self-healing docs for every system, and agents are instructed to keep them updated ... I tag the ones I know I need, or let the agent find them through AGENTS.md ... I also provide a more detailed summary in the first 7 lines of every doc, so they're easily greppable to find the right thing, and this is documented in AGENTS.md

3. agents always run the app ... the agent should always actually run the app itself, and test its work and fix issues as it goes, especially if running autonomously / asynchronously

4. end-to-end tests and instructions to write more and keep up to date, and docs on how to write tests, what to avoid, and a list of all the tests and what they test in yet another markdown doc ... write and run targeted tests during implementation, improve and commit with work

5. custom linters at precommit hooks looking for any problems you run across, with `--fix` fixing the problems automatically, OR if that's not feasible, it shells out to a cheaper LLM like Composer 2.5 or Sonnet to fix the problems -- NOT just flagging them, but actually resulting in cleaned code

6. cross-agent review at each major point: research, plan, implementation, and wrap-up. I mean codex, claude, cursor, whatever -- but it shouldn't be the same model reviewing the same code. And specific docs for agent review, what to look for, how to approach it. Also, personas -- looking at the code from different perspectives, such as maintainability, code quality, security, performance, AI smells, domains (e.g. "financial services expert" or whatever) ... and each persona also "owns" a set of system docs too and keeps them up to date

7. agent traces / worksheets that track what the agent is doing each session. if the agent fails partway through, you should be able to hand this worksheet to another agent and it could finish the job. commit this worksheet with the work so it's all connected and easy to reference later (you will reference these later!!), also have the agent apply git tags that correspond to specific worksheet names so they're easy to find

8. automatic agent feedback to you at the end of the session, added to a doc that is also committed with the work, that you periodically ingest into an interactive session and improve your workflows

9. a tools or bin folder that contains python or bash scripts that the agent has skills to make to make its job easier (for example, I have an `agent_review` bash script that lets the agent kick off agent reviews via CLI without knowing each agent's particular incantations) ... docs on how to make scripts effectively, and instructions to constantly build these out more

10. periodic agent sweeps through recent commits, looking for problems / gotchas from a higher level across commits

11. a coding conventions doc that is just for specific coding conventions you want to see in the code base, your review agents use these a lot (but a lot of this should be in linters)

12. an agent loop / night shift skill for autonomous work, that lays out how the agent is to approach this, from an orchestration standpoint

13. a task queue that is accessible to the agent (mine is just a TODOS.md, but yours might be in Linear etc, with a CLI to fetch via API)

14. a periodic false-confidence test audit skill that looks for tests that aren't actually testing what you think they're testing, and that fix those

15. visual regression tests -- take screenshots, compare via tool and with agent visual review, commit with work (git lfs useful here) or at least push into the PR

16. automatic performance benchmark tests that notice when performance degrades

17. performance profiling tools that can be used by agents for targeted benchmarking, trying new techniques, comparing outputs, and comparing profiles

18. end-of-shift full validations, including running all tests, performance, agent reviews, sweeps, everything -- when you return, it's all as pristine as it can be

If you have all this, your agentic coding experience is going to be very different than dry prompting and manually guiding it toward the right thing every time.

[Balázs Pozsgay @pozsgaybalazs]

We used this one: https://t.co/6szUgtJeFZ

[Muratcan Koylan @muratcan]

We're now building loops that improve the harness itself.

With strong instruction-following models (e.g. GPT-5.6 Sol), more exploratory models (e.g. Fable 5), and efficient competitive ones (e.g. GLM-5.2), the next bottleneck is meta-harnesses that can safely rewrite their own scaffolding.

I just released the Self-Improvement Loops skill (with its loop-design-evidence reference) in the Agent-Skills-for-Context-Engineering repo.

https://t.co/OiXy0MooLl

It distills patterns for systems where the harness becomes the optimization target.

“just let the agent improve itself” is the wrong mental model. The loop will optimize whatever signal you give it.

[Oikon | Claude Code深掘りガイド @oikon48]

もしかしてClaude Codeの /advisor コマンドで、指定のモデルをアドバイザーにできる機能が標準搭載されているの知られていない？？

[Avid @Av1dlive]

Fable 5 is here to stay in Claude Code till July 12th

so this guy just mapped the entire fable 5 agentic workflows into 9 diagrams

> the daily loop, trust ledger, standing goals + the 4 optional loops
> every one flow-mapped, numbered, editable in excalidraw
> each paired with the exact script that runs it and the check that proves it worked

plus it's free... all you do is send these screenshots to Claude:

save and bookmark this no matter what

[James E. Thorne @DrJStrategy]

Ignore the noise.

The next move in rates by the Fed will be a cut.

Have a nice day.