正在加载视频...

视频加载失败

I ran one of my own React dashboards through Replay before treating it as ready to ship. It looked fine to me. Replay QA found a notifications button that looked completely functional but did nothing when clicked, accessibility issues across the UI, and a workflow where completing a task...

57,558 次观看 • 5 天前 •via X (Twitter)

0 条评论

暂无评论

原始帖子的评论将显示在这里

相关视频

this video is the CLEAREST explanation of how claude skills + AI agents work and how to use them most people set up an AI agent and wonder why it keeps disappointing them. the context window is everything context is what the model assembles before it takes any action. think of it like everything the agent needs to read before it does anything. the quality of what goes in determines the quality of what comes out. the models are genuinely really good right now. claude and gpt are exceptional. the variable is almost always the context you give them. 1. agent.md files are mostly unnecessary every single line you put in an agent.md file gets added to every single conversation you have with your agent. a 1000 line file is around 7000 tokens burning on every run. the model already knows to use react. it can read your codebase. save the agent.md for proprietary information specific to your company that the model genuinely cannot know on its own. 2. skills are the actual unlock a skill.md file works differently. what loads into context is only the name and description, around 50 tokens. the full instructions only appear when the agent recognizes it needs that skill. so instead of 7000 tokens on every run you have 50. and the agent stays sharp because the context window stays lean. the closer you get to filling the context window the worse the agent performs, same way you perform worse when someone dumps 10 things on you at once. 3. here is how to actually build a skill the right way most people identify a workflow and immediately try to write the skill. what you want to do instead is run the workflow by hand with the agent first. walk it through every single step. tell it what to check, what good looks like, what bad looks like. correct it in real time. once you have had a full successful run from start to finish, tell the agent to review everything it just did and write the skill itself. it writes a better skill than you will because it has the full context of what actually worked in practice not in theory. 4. recursively building skills is how you go from frustrated to reliable when the skill breaks, and it will break, ask the agent exactly why it failed. it will tell you specifically what went wrong. fix it together in that same conversation. then tell it to update the skill file so that failure mode never happens again. ross mike did this five times with his youtube report generator. it now pulls from eight different data sources and runs flawlessly every single time without him touching it. 5. sub agents are something you earn not something you set up on day one start with one agent. build one workflow. turn it into one skill. once that works add another. ross mike has five sub agents now covering marketing, business, personal and more. it took months to get there and every single one exists because a workflow proved it deserved to exist. the people who set up 15 sub agents on day one and wonder why nothing works skipped all the steps that make the thing actually run. 6. your workflow is the thing the model cannot get anywhere else the model has been trained on everything. it knows more than you about most things. what it does not have is your specific process, your taste, your way of doing things. that is what skills capture. that is what makes your agent actually useful versus a generic one. downloading someone else's skill means downloading their context onto your setup and it will not work the way you want it to because it was never built around how you work. this is the clearest explanation of how agents actually work i have heard. Micky runs this stuff every single day and the results show it. full episode is now live on The Startup Ideas Podcast (SIP) 🧃 where you get your pods people charge for this sorta stuff i give away the sauce for free i just want you to win watch

GREG ISENBERG

193,721 次观看 • 4 个月前

TradingView can't replay the order book. It can't even rewind. Today, we are releasing Market Replay. In the clip, we replayed yesterday's CPI print release tick by tick. They replay the chart. We replay the market. It allows you to jump back in time and replay every candle, every order book tick, every liquidation, exactly as it happened. Pick any moment from years back. Scrub it like a video. What you will see is exactly what a live trader saw at that second. Here's what's inside: • The full order book, replayed. Rebuilt second by second at tick resolution: walls stacking, getting pulled, getting swept. • A real scrubber. Drag anywhere, both directions, instantly. Pause, step, or play at ten speeds from 0.25x to 30x. • Honest playback. Speed changes how fast you watch, never what happened. • Live data is gated out during replay. Replay is the only thing painting the chart. • 71 indicators replay in sync: CVD, open interest, funding, liquidations, footprint, volume delta, TPO, session profiles, VWAP, long/short ratios, ETF flows, dominance. • Your own scripts replay too, including ones built on orderbook and orderflow data. • Watch candles form: a 4h candle builds update by update, and at tick resolution second by second, with the book moving behind it. • Depth and liquidity readouts show the book as it stood at that moment, not now. • Years of candle and indicator history. Jump with the calendar or click any candle. Add an indicator mid-replay and it joins the timeline.

OpenMarket

12,730 次观看 • 1 个月前

AG-UI makes building agentic applications dramatically easier. Here's how it works. This is a model for a simple chatbot: User → LLM → Response But interactive agents that render UI, pause for approvals, and ask users for input need a much more complex model. When building these agents, a response from the LLM will include a series of state changes as the agent runs: • Agent started a task • Agent called a tool • Agent updated its state • Agent streams these tokens • Agent is waiting on a human • Agent is resuming the task The Agent-User Interaction Protocol (AG-UI) treats the LLM response as a stream of events rather than a text endpoint. In practice, here is what you get as an agent runs: 1. Lifecycle events so your UI knows where the agent is. 2. Text messages that stream tokens. 3. Tool calls so your UI can prefill a form with any required arguments. 4. State updates that keep your UI in sync with the agent. 5. Special events for human approvals, rich media, and custom needs. All of these events travel over standard transports (SSE, WebSockets, or plain HTTP) as JSON. As a result, you can build a frontend that stays in sync with the agent's progress without having to invent a custom process to make this happen. For example, building a human-in-the-loop workflow becomes an off-the-shelf component you can integrate rather than build from scratch. CopilotKit🪁 is the creator of AG-UI, and you can use it when building frontend applications pretty much anywhere: • React • Angular • Vue • React Native • Slack • Teams • Discord • WhatsApp • Telegram Here is the link for you to check it out: Thanks to the CopilotKit team for partnering with me on this post.

Santiago

17,438 次观看 • 1 个月前

In education, are we more focused on what school will look like 10 years from now, or asking the question, what are we doing with students today, and how will that affect them in 10 years? I also wonder how many students truly care about our “10 Year” plans in education. What matters most to them is what we are doing today. I was having a conversation with my daughter Kallea this past week and sharing about an opportunity that I wanted and how it didn’t work out. That was a teachable moment and I asked her, “What do you think your dad is going to do now?” Without hesitating she said, “Work harder.” This is something that I have talked about with her a lot, but hopefully, it is also something that I model. Sometimes things don’t work out because life isn’t fair. And sometimes, things don’t work out because we are not ready and haven’t done the work to get the accomplishment. It is easy to make the fault of others, and sometimes, that is even true. But I know that I always can control my own actions and if you complain about a problem, once you are finished complaining, it is still a problem. Only action creates future opportunities. My actions are the only things I can control. I hope this sticks with her and my kids because I know it is something my parents instilled in me. Of course, we need to focus on what school and learning can look like in the future, but we also have to understand that the future is also very dependent on what we install in our children today.

George Couros

16,599 次观看 • 2 年前