Human Quest · Patterns

AI Patterns

Every one of these started as something breaking in a real product, more than once. The fix became a pattern only when it was worth carrying into the next project instead of solving again from scratch.

Each has a repository you can read and a live site you can use. Nothing is listed here until both are true.

01Feedback02Openstage03Walkthroughs

How something earns a place here

1

It broke more than once

A one-off fix is a fix. The second time the same thing breaks in a different product, it is a pattern.

2

The fix got extracted

Pulled out of the product it was born in, into a repository that stands on its own and can be read without that context.

3

It runs in public

A live subdomain anyone can open. A pattern that only works on my machine has not been proven — it has been described.

01

Feedback

A button in the corner that files a real issue.

What broke

Bug reports arrived as screenshots in chat with no URL, no browser, no version — and the ones that did get filed were closed with an email telling the reporter to wait for a release that was never going to carry the fix.

What it does

Puts a reporting affordance on every page. One click captures the screenshot, the annotation, the route and the full browser fingerprint, and opens a GitHub issue on the project's own repository. Closing the issue is scripted, not manual, because the close is what sends the email.

See it liveSource

feedback.humanquest.net · alibad/feedback-widget

any pageshot · route · UA#1walkthrough-feedbackstatus:newa real issue, on its own repo
02

Openstage

Presentations that are a web app, not a slide file.

What broke

A deck is usually a dead artifact — it cannot show live data, cannot be linked to a line of code, and goes stale the moment the thing it describes changes.

What it does

Scroll-driven and slide-mode decks built as React. Narration, a chapter rail, theming, print-to-PDF, and panels that read live state from the app they are describing — so the deck is wrong only when the system is.

See it liveSource

openstage.humanquest.net · alibad/openstage

LIVEa URL, not a file — there is no deck to go stale
03

Walkthroughs

Documentation captured from the running product.

What broke

Written docs describe the product someone remembered, not the one that shipped. They drift silently, and nobody notices until a reader follows a step that no longer exists.

What it does

Drives a real browser over the real product, captures every screen at desktop and mobile, and publishes a searchable catalog with a staleness verdict per feature. When a capture cannot be trusted it refuses to publish rather than documenting something false.

See it liveSource

walkthrough.humanquest.net · alibad/walkthrough-studio

the real productmobilecatalog + verdictamber = refused to publish

The first pattern is running on this page

The feedback button in the corner is the Feedback pattern. Use it and it will file a real issue against this site, with the screenshot, the route and the browser you are reading on attached. That is the whole test of whether a pattern is real: it has to be switched on in the thing describing it.

It is down there

bottom corner, on every page

Named, not built

These are next. They have no links because there is nothing yet to link to, and a roadmap item dressed up as a shipped one is the exact failure these patterns exist to catch.

MCP

No repo · no subdomain

Redact

No repo · no subdomain

Console

No repo · no subdomain