Design × AI structure
Cursor plan · design_ai_structure
Problem
One surface does two jobs today: nav says Design × AI, but /design is mostly a bookmark shelf of primary-source link cards. Design × AI should feel like authored practice — workflows and tools you run — while resources stay a citeable corpus.
Two content types
| Kind | Name | Job | URL |
|---|---|---|---|
| Authored | Design × AI | Workflows, tools, topics you define | /design |
| Resources | Design resources | Primary-source link platform (existing articles) | /design/sources |
Separate kinds, one graph — with taxonomy and technologies, not two siloed shelves.
Target graph
Every major page should walk to the other three without hunting. Edges are declared (and reverse-indexed), not only prose backticks.
- A workflow shows related resources, technologies, and taxonomy terms.
- A resource shows Used-in practice entries, plus tech + taxonomy when declared.
- A technology profile can list related Design × AI practice and design resources.
- A taxonomy term can list both practice and resources tagged with it.
Layers
Layer A — Design resources
- Keep articles under design/articles/; public home /design/sources.
- Framing: “What we read and cite.”
- Add Technologies · Taxonomy · Practice (reverse index) link bands.
Layer B — Design × AI practice
- New design/practice/ with TOPIC.md (Sources · Technologies · Taxonomy required).
- Hard rule: incomplete without at least one source or technology (vocab topics still need taxonomy).
- Seed 2–3 real entries so /design is not hollow.
UI surfaces for the graph
- Practice page — Connections: Sources · Technologies · Taxonomy
- Resource article — Technologies · Taxonomy · Used in (practice)
- Technology article — Design × AI + Design resources when reverse links exist
- Taxonomy term — members include practice + resource hits
What not to do
- Do not relabel the link cards as “our workflows.”
- Do not delete the resource corpus.
- Do not leave practice and resources as parallel trees with only a footer link.
- Do not merge vibe + design.
Implementation todos
- schema-practiceAdd design/practice/ + TOPIC.md schema with required sources/technologies/taxonomy fields; seed 2–3 entries
- routes-navSplit /design (practice) vs /design/sources (resources); update nav/footer/home
- graph-linksFirst-class interlinks practice↔sources↔taxonomy↔technology (declared fields + Used-in + wiki/taxonomy trails)