4 comments

  • moonshotideas19 days ago
    I think you did an amazing job of converting this into something that people can easily understand and use within their codebase - so props on that. It however would be the the right thing to give the proper credit to the source of idea - at least to thank them for their work and effort given this more of less is a direct copy of what they published <a href="https:&#x2F;&#x2F;www.intent-systems.com&#x2F;" rel="nofollow">https:&#x2F;&#x2F;www.intent-systems.com&#x2F;</a> (not me and it’s something I use as well, but proper thing to do is give credit where credit is due)
    • contextty6 days ago
      hey moonshot, I wrote that intent layer article, thank you for this! I&#x27;m glad you find it useful :)
    • Hunter1718 days ago
      hey, thank you, yup I fully agree with you. before publishing, I made sure to add a Credits section at the end of the blogpost. I will add it to GitHub too ;)
  • cadamsdotcom18 days ago
    Truly curious here.<p>How is this different to asking the agent to add documentation?
    • Hunter1718 days ago
      This follows, more or less, the principle of progressive disclosure, similar to skills. I think of it as precomputing constraints, not just context. The agent always reads the subfolder’s AGENTS.md, which re-asserts scope and authority. I plan to add another skill to periodically re-assert intent, preventing intent drift and keeping the intent layer up to date. You can already rerun &#x2F;intent-layer to refresh it.
  • Agent_Builder19 days ago
    [dead]