← All labs

Lab 04 / Interactive inventory

Product Systems Kit

Not software I know. Equipment I use to build things.

AT.KIT / 08 items Case sealed
  1. Design / Equipped

    Figma

    Interface design, system definition, interaction prototyping, and the visual decisions that need to survive implementation.

    See it used in Designing Pave
  2. AI / Equipped

    ChatGPT

    Exploration, synthesis, critique, and turning loose product questions into material that can be tested.

  3. AI / Equipped

    Codex

    Repository exploration, rapid prototyping, implementation support, and design-system automation.

  4. Build / Equipped

    VS Code

    The portable workbench for editing product code, inspecting behavior, and tightening the handoff between design and implementation.

  5. Build / Equipped

    Terminal

    Builds, tests, repository operations, local tooling, and the unglamorous checks that keep prototypes honest.

  6. Build / Equipped

    GitHub

    Versioned product work, reviewable changes, and a shared place for design decisions to meet production code.

    See it used in Designing Pave
  7. Operations / Equipped

    Linear / Jira

    Planning, sequencing, and keeping product decisions connected to delivery without pretending the ticket is the work.

  8. Operations / Equipped

    Notion / Obsidian

    Working notes, research material, decision trails, and the archive needed when memory stops being a dependable interface.

01 / Meaning

Equipment, not endorsements

Compartments describe the kind of work. Object size is composition, not a ranking, mastery score, or claim about expertise.

02 / Material

Rendered, then assembled

The open case is one limited-palette pixel raster with semantic HTML hit areas layered over each compartment. Labels, focus states, and inspection behavior remain native HTML.

03 / Access

Works with fewer effects

Keyboard controls, reduced motion, and a readable no-JavaScript inventory are part of the object—not cleanup after it.