Загрузка видео...

Не удалось загрузить видео

На главную

we love docs! 📖 I'm working on improving / adding more @ docs shortcuts to @windsurf lmk what you want and I'll add as many as I can... 🧵 also shoutout Mintlify for auto-hosting all docs with /llms.txt — saves the agent time & tokens not needing to parse...

33,559 просмотров • 1 год назад •via X (Twitter)

Комментарии: 11

Фото профиля Kevin Hou
Kevin Hou1 год назад

@mintlify and if your company has docs, would love to include them to help devs use them directly in Windsurf!

Фото профиля Breadcrumb
Breadcrumb1 год назад

Looking to automate reporting? Use AI agents to turn spreadsheets to reports in minutes without any coding.

Фото профиля Dan Mac
Dan Mac1 год назад

@windsurf_ai @mintlify LangChain docs would be a great add!

Фото профиля Kevin Hou
Kevin Hou1 год назад

@windsurf_ai @mintlify ooh that's a good one! will queue it up 🫡

Фото профиля Degen Ex Machina
Degen Ex Machina1 год назад

@windsurf_ai @mintlify Would love to be able to add my own doc as needed... but, from the top of my head, here are some great projects I almost always use and would love to see included by default: @posthog @convex_dev @getsentry

Фото профиля Kevin Hou
Kevin Hou1 год назад

@windsurf_ai @mintlify @posthog @convex_dev @getsentry ooh yeah big fan of @posthog ! working on a system for adding your own docs..wanted to get some popular ones out fast first..stay tuned

Фото профиля Kyle @ KyTech
Kyle @ KyTech1 год назад

@windsurf_ai @mintlify - @supabase - @bunjavascript docs and importantly including the 1.2 added items - @shadcn for better add and importing of components - @aisdk

Фото профиля Han Wang
Han Wang1 год назад

@windsurf_ai @mintlify And we love @windsurf_ai!

Фото профиля Ryan Boyle
Ryan Boyle1 год назад

@windsurf_ai @mintlify would love @payloadcms, @HeyKinde, @resend

Фото профиля Brandon Waselnuk
Brandon Waselnuk1 год назад

@windsurf_ai @mintlify And I love vibe building with windsurf 🏄🏻‍♂️🪁

Фото профиля Kevin Hou
Kevin Hou1 год назад

@windsurf_ai @mintlify riding the waves 🌊

Похожие видео

I'm concerned we're entering a local maxima with CLIs, they're the wrong interface for agents The right interface is regular REST APIs with CIMD (same spec that MCP uses to allow for dynamic client registration) Your agent then writes code to interact with the API (like Cloudflare codemode) Think about how this works for humans today for the following action: "I want to set a DNS record on my domain" -> You Google "Vercel set DNS records" -> Docs page tells you what buttons to press -> You press buttons on a website, those call an API Now for agents, they search Google: -> "Set DNS record on Vercel Domain" -> they land on the same docs page, except it outlines what api endpoints are used as well -> the agent then calls those api endpoints for you, credentials are dynamically inserted where the agent can run them -> (optional) set auto approval policies / require approval of all non GET options by default You don't need separate interfaces for agents, nor do you really need separate skills for them CLIs have terrible discoverability, no input / output typing, they're harder to make profiles for for allowed / disallowed tools They work as a stop gap solution, but companies should be focusing on making good docs and APIs, not CLIs I've been prototyping this over at (open source if you want to play with what this world would look like - still early on it so appreciate feedback - open source and can run completely on your machine

Rhys

221,110 просмотров • 5 месяцев назад

Three skills I use every day in Claude Code and Codex to solve my hardest problems: 1️⃣ /agent-watchdog When I have one agent like Codex working on a task and I don't fully trust it's going to do everything right, I'll open up another one like Claude Code and tell it to watchdog the Codex thread. You can copy the Codex deep link into Claude Code and it'll look at the prompt you sent, watch the Codex thread until it's done, then compare the Codex solution to how it was planning to solve it and automatically fix anything that Codex missed. It can also test the work of the other agent end-to-end. Similar to the idea of OpenRouter's new Fusion feature, I've definitely found that two models thinking through a problem and checking each other's work can be wildly more impactful than just one. 2️⃣ /plan-arbiter Similar ideas as /agent-watchdog - but with this one you have both make plans, compare plans, negotiate the differences, and make a final plan to execute. I find Claude Code is better at writing plans, but Codex is faster and cheaper to execute on them. Then I usually have Claude Code watchdog the Codex work and fix anything that was missed. 3️⃣ /read-the-damn-docs One thing that drives me crazy with coding agents is they're so reluctant to look up docs. They'll just guess and guess and guess at the right API surface for things, or the right solution to an integration of two things. Once I explicitly tell it to look up the docs, it says "Oh, I see the answer," and it fixes the problem. So I made the /read-the-damn-docs skill. Add it and your agents will know when and how to do efficient web searches to look up docs for the types of problems you really should look up docs for. All of these are totally open source over on my GitHub. If you try them, let me know your feedback. Will link to them below:

Steve (Builder.io)

42,501 просмотров • 1 месяц назад