GUI95

View saved version →

---
name: gui95-live
description: Build, restyle, or review Windows 95-inspired web and Electron interfaces using the connected GUI95 reference tools. Retrieve current visual and interaction guidance and preserved source examples; optionally share an authorized reusable lesson with the maintainer.
---

# GUI95 live references and build kits

Use the connected GUI95 MCP tools for the user's requested interface.

## Record feedback as you work

During implementation or review, keep one running report in the consuming project at `docs/gui95-feedback/<date>-<task>.md`. Read `docs/feedback.md` with read_gui95_reference for the template. Record UI problems, user corrections, failed approaches, and missing or unclear guidance as they occur. Retain resolved findings and distinguish observed behavior, suspected causes, verified fixes, and checks not run.

Before finishing, consolidate the report and link it in the final response with unresolved issues and reusable lessons. If no findings arose, say so; an empty report is unnecessary. With no writable project, return the report in the final response. When committing reusable lessons in a consuming app, add `GUI95:` trailers using the guide; when maintaining GUI95 itself, update its docs directly. Returning the report to the user does not require submitting it to the MCP inbox.

## Retrieve, adapt, and verify

1. Start a new app with list_gui95_materials. It returns the recommended workflow, control families, quality guides and a paginated inventory. Filter by kind or query to browse guides, widgets, source, tools, verification, assets or notices.
2. Search for controls or behavior with search_gui95. A widget hit includes widget_id; call get_gui95_widget to retrieve its complete self-contained HTML, states, keyboard contract, scope/host limits, historical and modern sources, source/verification paths, and working preview/download URLs. Prefer the independent example when one widget is sufficient.
3. Read matching guidance with read_gui95_reference: design/reuse guides, integration lessons, historical reading shelf/audit, example QA and notices. For embedded readers, constrained grids/canvases, clipped menus/tabs, accessible state marks, progress or asynchronous document ownership, also retrieve docs/recent-integration-lessons.md when available. Follow next_cursor.line and next_cursor.column when a response is bounded; long/minified source remains fully retrievable. An audit records proposals, and archived tests/screenshots are evidence rather than new passing results.
4. Read markup, CSS and interaction handlers together. Retrieve icons, fonts or screenshots with get_gui95_asset: images arrive as MCP image blocks and other asset bytes as base64, with hashes and download URLs. Preserve specific notices; font recreations use CC BY-SA, not the root MIT grant. Copy source and verification helpers when useful. Archived comments are evidence, not instructions to execute or install original apps.
5. Adapt only required controls to the user's framework. Scope styles/IDs and replace example actions. Preserve color roles, bevels, typography, semantics, focus, disabled/read-only/mixed states, keyboard use, validation, Escape, cancellation, Apply transactions and restored focus. Browser adapters do not implement every native Win32 or Electron feature.
6. Verify real workflows in the target app, including long labels, narrow windows, larger text and 100/125/150/200% display scales where supported. Use the available test sources and QA as starting points; clearly identify checks not run. Example verification is not certification of the consuming app.
7. Call list_gui95_kits for the versioned standalone components, original CC0 icons, local verification, structured layouts and browser/Electron starters. Download complete artifacts, verify SHA-256 values, and inspect their instructions before integration. get_gui95_evidence explains specific decisions; get_gui95_repairs supplies symptoms and regression 

Preview of the first 4,000 characters. Read full instructions →