cutaway16.1 KB
View saved version →
---
name: cutaway
description: Explain how machines and hardware work by creating educational cutaways as interactive HTML, isometric SVG, or editable React figures. Use for requests such as "explain how this machine works" with a photo or model number, and for engines, wings, pumps, appliances, and other physical mechanisms. Identify the machine and research its internals before drawing it. Also supports requested software analogies. Doesn't cover medical anatomy or ordinary flowcharts.
---
# Cutaway
Build a cutaway that explains how the requested machine works. For a jet engine, separate core and bypass flow; for an espresso machine, follow water through the pump, boiler, and group head; for a piston engine, connect crank position to piston and valve motion.
When the user invokes Cutaway with a machine photo and asks how it works, deliver a visual explanation by default: identify it, research the mechanism, then create and attach the interactive cutaway. Identification and a written explanation are intermediate work. Honor requests for identification only, text only, or a different output.
Draw the actual mechanism when the user asks about a physical object, and use an analogy when requested. Every visible number and moving part must agree with the same model.
Name the hardware layout and explain its simplifications, such as illustrative dimensions in an engine or uncalculated airflow over a wing. When arrangement or timing affects the explanation, check an authoritative diagram or technical reference and cite it. Name each part, describe its job, and show what changes when the user operates a control.
Cutaway adapts Ryan's MIT-licensed Anatomy toolkit for ChatGPT. Its optional 2D glow layer adapts April Zhu's iso-glow, based on Tolga Cohce's iso-figure, with their MIT notices preserved.
User instructions take precedence over these defaults. Resolve the paths below relative to this skill directory.
## From a photo or model number
Use this workflow when the user asks how their particular machine works. A photo can establish its appearance and help identify it; hidden parts need other evidence. Use the host's image, search, and file tools. Keep the photo in the conversation and deliver the drawing there; this workflow doesn't upload it to Cutaway's hosted service.
1. Identify the brand and model from visible markings, controls, and the user's information. Separate a likely match from a confirmed identification. Ask for a model label only when the missing detail changes the operating principle being explained, or the user requires an exact internal layout. An unknown SKU or revision doesn't block a drawing of a documented shared mechanism. A supplied model number or manual can be enough; don't require a photo. Search by model, without serial numbers or unrelated personal details from the image.
2. Open references for that model and relevant revision. Prefer manufacturer manuals, service documents, and exploded parts diagrams; use a documented teardown when needed. Check that each source actually supports the claim. A search snippet, marketing specification, or similar-looking model doesn't establish internal placement or connections.
3. Establish the parts and connections needed to explain the requested operation. For an espresso machine, check the pump, heating system, brew path, valves, and any steam circuit being shown. Resolve conflicting references or state the uncertainty. Gather only specifications that affect the explanation; an unknown dimension can stay illustrative.
4. Choose the drawing's scope from the evidence. When references document the operating principle but not the exact internal layout, build a simplified mechanism cutaway in the same turn. Match recognizable exterior features from the photo, label internal placement and routing as illustrative, and keep unverified specifications out. A source describing the principle can support this teaching model without proving the product's construction. If t
Preview of the first 4,000 characters. Read full instructions →
Referenced files: 51 — file references are metadata, not package contents.
