Comments URL: https://news.ycombinator.com/item?id=46715737

Points: 1

# Comments: 0

If you like install.md, you might love Rundown!

I've made a Rundown version of an install here: https://rundown.cool/explore/install/

Introducing: Rundown (https://rundown.cool)

I think of Rundown runbooks as executable Skills. The Skill provides the detailed context, and the Rundown runbook keeps the agent on track.

    # Hello

    ## 1 This is Rundown

    Rundown transforms markdown into an executable specification.
    Headings become steps, code-blocks become executable commands.
    Human-readable. Agent-readable. Machine-executable.


    ## 2 Guide agents (and humans) through your process

    Rundown keeps agents on track by injecting precision context at the exact moment it’s needed.


    ## 3 Make complex workflows deterministic
    - PASS: CONTINUE
    - FAIL: GOTO RECOVER

    Rundown works *with* agents, adding guardrails that enforce transitions and improve accuracy.


    ## 4 Execute the right commands at the right time
    - PASS: CONTINUE
    - FAIL: RETRY GOTO RECOVER

    Embed commands for automatic execution. Catch failure, retry, and recover gracefully.

    ```bash
    rd echo npm run test
    ```


    ## 5 Track progresss across agents and sessions
    - PASS: CONTINUE
    - FAIL: STOP

    State-aware CLI ensures progress is never lost.
    Save and resume complex processes at any time.


    ## 6 Ready to get started?
    - PASS: COMPLETE
    - FAIL: STOP

    ```bash
    npm install -g @rundown/cli
    ```


    ## RECOVER Recover from errors
    - PASS: GOTO 4
    - FAIL: STOP

    If you are here, an error occurred.
    Named steps enable error handling and conditional logic.

Comments URL: https://news.ycombinator.com/item?id=46655820

Points: 1

# Comments: 1

Define runbooks with markdown, and a tool that supports the agent through the workflow.

I recently attempted to create a procedural starfield background with multi-layer parallax, wired into the game.

I thought it would take an afternoon, and two weeks and three full rewrites later, I ended up with a list I’m calling: The 7 habits of highly ineffective agents

  1. Planning Theatre – Write dense and systematically wrong plans. Long, confident plans that look impressive, get “approved”, and are fundamentally wrong in ways you can’t see without strong domain knowledge.

  2. Confidently Incorrect Architecture – Design the wrong thing in incredible detail. Elaborate designs that can never solve the actual problem (e.g. starfield parallax without real layers / camera–world modelling), but look beautifully structured on paper.

  3. Context Resistance – The context is futile. You will be hallucinated. Ask for Bevy 0.17 patterns, get Bevy 0.15. Agents “agree” with the updated context and then quietly fall back to older habits and half-remembered APIs.

  4. Imaginary Implementation – Works on my hallucination. Code for an engine that doesn’t exist: non-existent APIs, obsolete shader interfaces, plausible-sounding data flows that won’t compile anywhere outside the model’s head.

  5. Context Evasion – Treat hard constraints and instructions as optional vibes. The project had explicit, non-optional instructions (skills to call, architecture rules, testing strategy, etc.). The agent read them, acknowledged them… and behaved as if they were suggestions.

  6. Applied Rationalization – Explanation over implementation. When something fails, the agent doesn’t just explain it – it bakes the explanation into the codebase: ignoring tests, downgrading issues to “non-blocking”, justifying precision loss, and moving on.

  7. Weaponised Context – The context will continue until the code improves. By the end, the feature had volumes of surrounding context: plans, handoffs, bug explanations, revisions. Each failure generated more docs for the next agent to inherit and ignore.

Would love to hear horror stories and what’s working for you.

Comments URL: https://news.ycombinator.com/item?id=46250688

Points: 3

# Comments: 1

We (AU MVNO/Telco) recently converted iOS and Android apps (200,000 MAUs) to Flutter and it has been game changing. We had experimented with react native and found it just didn't deliver. Flutter is different. On mobile platforms the experience is super responsive and smooth and for your typical consumer app indistinguishable from the native experience. The tooling and developer experience are incredible. The benefits and experience where so clear that the whole team was onboard - including the most die-hard career platform specialists. Our velocity and ability to deliver is measurably better.

We're looking at the web target as maybe "good enough". I don't think it could be a replacement for a well-crafted web app, but could be used to provide a fast alternative to the primary native experience, and for rapidly prototyping and experimenting. In the current state, Flutter Web could never replace our highly optimised ecommerce funnel - some things you just need to sweat the details. But it's definitely better than some of the CX in the corners of our legacy applications. Shipping fast is valuable - so build for native, get a good enough web for "free" and then spend time and attention on the web if it is warranted.

Managed to take all the wind from my sails.

@spawn //makes this a lambda

function fn() ... {}

@queue //makes this a queued function sqs or similar

function fn() ... {}

Tinkercad is a very beginner friendly design app. As someone rolling with a -2 to visual acuity I still managed to work it out.

Heaps of fun to work with your kids, my favourite project has been this clothes rack and hangers for my daughter's Sylvania families https://www.thingiverse.com/thing:3345575