But how is DESIGN.md to play nicely with eg Figma Design Tokens, or tailwind.config.js? Is it to become the source-of-truth, or simply point to those--in which case how, besides deterministic validation, does it differ from AGENTS.md? Scope? If the future of agentic coding is the orchestration of discrete, focused sub-agents, I expect something like DESIGN.md to show up as .agents/designer/SOUL.md.
This doesn't seem to be a critique of the principles so much as a critique of their phrasing.
Even his "critique" of Demeter is, essentially, that it focuses on an inconsequential aspect of dysfunction—method chaining—which I consider to be just one sme that leads to the larger principle which—and we, apparently, both agree on this—is interface design.
Yes, and there are many different kinds of truth, so when two arise together—we can call this connascence—we can categorize how these instances overlap: Connascence of Name, Connascence of Algorithm, etc.
Sure, when these things were novel the friction was delightful. Now that the magic is gone, I want to finish configuring my device ASAP and get back to the games.
reply