I also love just asking Claude to look at the repo and decide how it should use it. Have had a few times where it said “project not a good fit” which in and of itself is a good sign
530 karma · joined August 30, 2010
I also love just asking Claude to look at the repo and decide how it should use it. Have had a few times where it said “project not a good fit” which in and of itself is a good sign
So I wrote a file that defined a composite metric (four weighted components → one score), an improvement loop, and constraints. Pointed Claude at it. Went to bed. Woke up to 12 commits, 47 → 83.
The file became GOAL.md. The insight that surprised me: most software doesn’t have a natural scalar metric like val_bpb. You have to construct it. Documentation quality, API trustworthiness, test infrastructure confidence — these things have no pytest –cov equivalent. But once you build the ruler, the autoresearch loop works on them too.
The part I’m most uncertain about: the “dual score” pattern. When the agent is building its own measuring tools, it can game the metric by weakening the instrument. So the docs-quality example has two scores — one for the docs, one for the linter itself. The agent has to improve the telescope before it can use it. I think this is load-bearing but I’d love to hear if others have found different solutions to the same problem.
Easiest way to try it: paste this into Claude Code, Cursor, or any coding agent and point it at one of your repos:
Read github.com/jmilinovich/goal-md — read the template and examples. Then write me a GOAL.md for this repo and start working on it.
Happy to hear what breaks. The scoring script is bash + jq so it’s not exactly production-grade, and the examples are biased toward the kinds of projects I work on. More examples from different domains would make the pattern sharper.
When a user enters a link to our platform, we're crawling the page for all of its meta data, and then using any Schema.org, Open Graph or Title tag markup as props that we interpolate into a series of React components. While this version of the app is limited to just working with web-based content via our app, we're going to be launch our API and enable users to plug in any dynamic content source as well as import their own templates for use.
We're excited to get this into the hands of the HN community for feedback and in hopes this can be helpful in automating people's marketing workflows today.
Thanks! John Milinovich john(at)aesthetic.com
It's surprising that Google hasn't cracked down on this yet or dealt with the obvious dupes problem (showing image result from Pinterest that came from website a vs showing result from website a).
Currently we list out the availability of apps in our index by company and not by operating system; we’ll look into providing more detailed information.
Regarding IMDb: while the site index may be accessible and their app does have deep links, IMDb has not publicly exposed their deep link structure via meta tags. Currently, we're only indexing sites with these tags, but that will change shortly.
For more background: - http://en.wikipedia.org/wiki/Mobile_deep_linking - http://blog.urx.com/urx-blog/deeplinking-in-3-steps
Look forward to discussing further and seeing how we can work together here to connect the webs.
In addition to their meta tags, Facebook also released an API that lets developers send Facebook a request with a URL to receive a response for the equivalent deeplink. This solution works best for deeper native integrations and those who want to go through Facebook to get this mapping. Fortunately, URX omnilinks already support Applink tags and don't require any code-level integration for developers to start linking to other apps.
Basically, the tags are open source (good), much like URX's working proposal [1], and the implementation of using the tags goes through Facebook. Facebook requires a native integration and does get around browser flashes, but is much more difficult to integrate than omnilinks, where you simply put urx.io/ in front of any weblink.
see also: https://developers.google.com/+/mobile/ios/share/deep-link
Would love to hear from HN any other strategies/suggestions that work in this vain.
http://schemes.zwapp.com/ also has a ton of schemas, but is a bit unorganized and not completely reliable.
2- We've built our own link creator (see footer link on site) to make it easy to learn about other apps' url schemes and create links into their apps. these links can be used from anywhere, including the web. We're adding apps consistently, so let us know if there are any that aren't already there.