{
  "schema_version": "1.1",
  "id": "atlas-design-engineering",
  "slug": "design-engineering",
  "title": "Design Engineering",
  "url": "https://feed7.dev/atlas/design-engineering",
  "current_answer": null,
  "implementation_consequence": null,
  "agent_context": null,
  "confidence": "auto_collected",
  "last_verified": null,
  "last_updated": null,
  "evidence": [
    {
      "schema_version": "1.1",
      "id": "p6",
      "slug": "linear-motion-reference",
      "url": "https://feed7.dev/p/linear-motion-reference",
      "title": "Linear’s command menu motion — a taste reference",
      "why_included": "Points to concrete motion timing that maps to a product decision.",
      "summary": "Thread breaks down Linear’s command menu: 150ms state changes, 200ms popover, no bounce, follows-finger dismissal.",
      "practical_implication": "A 150ms / 200ms rhythm worth adopting for any command surface. Maps directly to motion tokens.",
      "agent_context": "Reference for command-menu motion: 150ms state changes, 200ms popover, no bounce. Maps to motion tokens.",
      "source": {
        "name": "X",
        "url": "https://x.com/designdetail/status/1938471",
        "published_at": "2026-06-25T00:00:00.000Z"
      },
      "source_class": "social_media",
      "content_type": "Social Thread",
      "layer": "craft",
      "domains": [],
      "topics": [
        "interface-quality",
        "design-engineering"
      ],
      "verification": {
        "status": "source_linked",
        "label": "Source Linked",
        "method": "source_feed",
        "verified_at": null
      },
      "uncertainty": [
        "Timing inferred from video; not documented by source."
      ],
      "connected_context": null,
      "lifecycle": "New",
      "published_at": "2026-06-25T00:00:00.000Z",
      "modified_at": "2026-06-25T00:00:00.000Z",
      "supersedes": [],
      "expires_at": null,
      "formats": {
        "html": "https://feed7.dev/p/linear-motion-reference",
        "json": "https://feed7.dev/p/linear-motion-reference.json",
        "markdown": "https://feed7.dev/p/linear-motion-reference.md"
      }
    },
    {
      "schema_version": "1.1",
      "id": "p13",
      "slug": "vercel-dashboard-density",
      "url": "https://feed7.dev/p/vercel-dashboard-density",
      "title": "Vercel dashboard density — a layout taste reference",
      "why_included": "A concrete answer to \"how dense should a developer dashboard be\" — with measurable spacing decisions.",
      "summary": "Breakdown of Vercel’s dashboard rhythm: 24px card padding, hairline borders instead of shadow, one accent color per view.",
      "practical_implication": "Decision: adopt hairline-border density for the Brain library instead of spaced-out cards. Maps to spacing tokens 16/24.",
      "agent_context": "Density reference: 24px card padding, hairline borders, no shadow, one accent per view. Use for library/table surfaces where scanning matters more than air.",
      "source": {
        "name": "Design",
        "url": "https://vercel.com/design/dashboard-density",
        "published_at": "2026-06-18T00:00:00.000Z"
      },
      "source_class": "taste_reference",
      "content_type": "Design Reference",
      "layer": "craft",
      "domains": [],
      "topics": [
        "interface-quality",
        "design-engineering"
      ],
      "verification": {
        "status": "source_linked",
        "label": "Source Linked",
        "method": "source_feed",
        "verified_at": null
      },
      "uncertainty": [],
      "connected_context": null,
      "lifecycle": "Evergreen",
      "published_at": "2026-06-18T00:00:00.000Z",
      "modified_at": "2026-06-18T00:00:00.000Z",
      "supersedes": [],
      "expires_at": null,
      "formats": {
        "html": "https://feed7.dev/p/vercel-dashboard-density",
        "json": "https://feed7.dev/p/vercel-dashboard-density.json",
        "markdown": "https://feed7.dev/p/vercel-dashboard-density.md"
      }
    }
  ],
  "conflicting_sources": [],
  "superseded_claims": [],
  "corpus_evidence": [
    {
      "title": "The End of the Static Screen: Architecting Intent-Driven UX — Gus Iwanaga, commercetools",
      "url": "https://www.youtube.com/watch?v=QrMcNe2jjt8",
      "source_name": "AI Engineer",
      "published_at": "2026-09-01T20:00:01+00:00",
      "summary": "Generative UI needs more than a component catalog: agents require explicit layout rules, schemas, and design-system constraints to produce stable interfaces across repeated requests."
    },
    {
      "title": "How our agents build on-brand pages with design.md",
      "url": "https://vercel.com/blog/how-our-agents-build-on-brand-pages-with-design-md",
      "source_name": "Vercel",
      "published_at": "2026-08-31T04:00:00+00:00",
      "summary": "Vercel found that prose alone produced inconsistent agent-made pages, then paired design.md with fixed CSS primitives and repeatable evals to encode brand judgment."
    },
    {
      "title": "The Signal Layer: What to Build When Anything Can Be Built — Lena Hall, Akamai",
      "url": "https://www.youtube.com/watch?v=1KOdiGgMtpY",
      "source_name": "AI Engineer",
      "published_at": "2026-08-29T18:00:34+00:00",
      "summary": "As coding agents make implementation easier to copy, builders should spend more judgment on problem choice and preserve claims, evidence, and limits as AI remixes work across product and GTM."
    },
    {
      "title": "The Missing Layer: Design Taste in AI Agents — Hassan El Mghari, Together AI",
      "url": "https://www.youtube.com/watch?v=7GMKdpLsxwU",
      "source_name": "AI Engineer",
      "published_at": "2026-08-21T15:00:06+00:00",
      "summary": "Treat an agent’s first UI as a draft: encode recurring design dislikes, supply visual references, split work into focused prompts, and reserve time for iteration."
    },
    {
      "title": "Ending AI Slop — Thais Castello Branco, Taste Labs",
      "url": "https://www.youtube.com/watch?v=lCBf9slCanI",
      "source_name": "AI Engineer",
      "published_at": "2026-07-31T19:26:20+00:00",
      "summary": "For subjective agent output, replace vague requests for quality with decomposed brand constraints, then reserve human preference data for style and creativity that resist deterministic checks."
    },
    {
      "title": "Leonxlnx/taste-skill",
      "url": "https://github.com/Leonxlnx/taste-skill",
      "source_name": null,
      "published_at": null,
      "summary": "A set of portable SKILL.md files that push coding agents past generic frontend output: it infers a design language from the brief and tunes variance, motion, and density dials. 850 stars in a day."
    },
    {
      "title": "cathrynlavery/diagram-design",
      "url": "https://github.com/cathrynlavery/diagram-design",
      "source_name": "GitHub",
      "published_at": null,
      "summary": "Diagram Design gives coding agents a reusable system for branded, accessible HTML and SVG diagrams, including draw.io and Mermaid redraw workflows."
    },
    {
      "title": "VoltAgent/awesome-design-md",
      "url": "https://github.com/VoltAgent/awesome-design-md",
      "source_name": "GitHub",
      "published_at": null,
      "summary": "This repository treats visual direction as agent-readable project context: drop in a DESIGN.md containing tokens, component rules, and guardrails to reduce inconsistent generated UI."
    },
    {
      "title": "Nutlope/hallmark",
      "url": "https://github.com/Nutlope/hallmark",
      "source_name": null,
      "published_at": null,
      "summary": "Hallmark turns interface taste into an installable coding-agent skill: it selects page structures and themes, critiques output, and checks common generated-UI patterns before emitting code."
    }
  ]
}