{
  "schema_version": "1.1",
  "id": "atlas-interface-quality",
  "slug": "interface-quality",
  "title": "Interface Quality",
  "url": "https://feed7.dev/atlas/interface-quality",
  "current_answer": "Taste references that map to concrete product decisions — motion timing, density, editorial rhythm.",
  "implementation_consequence": "Taste references only belong in feed7 when they produce a design decision an agent can apply. Otherwise they are moodboard material.",
  "agent_context": "Motion: 150ms state changes, 200ms popovers, no bounce. Density: 24px card padding, hairline borders over shadow, one accent per view.",
  "confidence": "editorial",
  "last_verified": null,
  "last_updated": "2026-06-25T00:00:00.000Z",
  "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": "MCP Apps: Extending the Frontier — Ido Salomon & Liad Yosef",
      "url": "https://www.youtube.com/watch?v=-jY2T2PiJBE",
      "source_name": "AI Engineer",
      "published_at": "2026-08-02T23:30:06+00:00",
      "summary": "MCP Apps let servers return sandboxed, interactive UI instead of text alone while the host retains control of prompts and tool calls—a useful pattern for agent workflows needing charts or controls."
    },
    {
      "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": "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."
    }
  ]
}