# Bicycle mechanics explained visually

> An illustrated mechanics explainer pairs readable prose with controllable bicycle, wheel, crate, and beam diagrams. Colored arrows, component highlights, sliders, and a frame mass readout expose forces, velocity, spoke construction, and structural loading.

- Kind: Interactive reference
- Live interactive reference: https://ciechanow.ski/bicycle/
- Page: https://meetreference.com/v/exp-bicycle-forces/
- Ready-to-use agent handoff: https://meetreference.com/v/exp-bicycle-forces/agent.txt
- Authorship: Not stated
- Made with: Not stated
- Model: not stated
- Built with: not stated
- Style: Interactive explainers; scientific illustration, interactive diagrams, minimal editorial, color coding, technical 3d, white space
- Preview: a flip-through of inspected screenshots; open the live work to experience its motion and interactions.
- Shared by Bartosz Ciechanowski in Website, Mar 28, 2023: https://ciechanow.ski/bicycle/
- Prompt fidelity: Unavailable in this entry. The recreation brief is written by Reference.

## Before you start

Guidance from Reference, separate from the creator's instructions.

1. Read the reference and inspect the project, installed libraries, and available agent skills before writing code. Reuse suitable tools already present.
2. Prefer the creator-reported libraries and skills when they fit the task. Explain what useful additions help with, and install missing project dependencies or relevant skills from official sources when the environment and the user's existing permissions allow it. Respect the project's package manager and setup rules; do not ask again for routine setup already authorized.
3. Distinguish tools used by the creator from your own recommendations. A listed tool is not automatically required, and an empty tools or requirements list means the setup is unknown, not that nothing is needed.
4. Ask concise questions when missing inputs or choices materially affect the result: paid services, credentials, the user's assets, or a different production approach. Use existing answers and permissions; continue independent work while waiting.
5. If a useful library, skill, or service cannot be installed or used, explain an available alternative and its expected effect on quality, features, or effort. Get the user's choice before a material compromise; otherwise state the fallback and continue. Never silently simplify the result or claim to have used a tool you did not use.

## Recreating this interactive reference

This is a visual reference. No original creator prompt is available. The following brief was written by Reference after inspecting the work.

Connect each explanatory variable across prose, diagram overlays, and controls using the same accent color. Isolate detailed models against pale backgrounds, fade ground planes at the edges, and use paired views to compare a complex representation with its simplified equivalent. For a new mechanical subject, replace the bicycle components and force scenarios while retaining the alternating prose–diagram rhythm and controls placed directly beneath each illustration.

1. Open the live work or source and inspect the frame images below.
2. Adapt its layout, hierarchy, palette, and interaction patterns to the user's own content and brand.
3. Compare the result against the reference. Use your own assets and credit the original creator.

## What it looks like

Written by Reference from the captured walkthrough frames, not by the creator.

Educational physics explainer with simple bicycle and wheel illustrations, explanatory text, and slider-like controls.

- Color: Mostly white and light gray, with blue outlines and accents plus small yellow, red, and green details.
- Type: Small sans-serif body text with occasional colored or underlined emphasis; no prominent display typography.
- Framing: Centered mechanical diagrams alternate with short explanatory paragraphs. Color-linked sliders sit beneath wheels, riders, force diagrams and simplified structural models.
- Structure: Multiple instructional blocks, each combining paragraphs with a diagram or bicycle schematic and, in several sections, a horizontal control.

Storyboard, nine frames spread across the captured walkthrough: https://meetreference.com/media/exp-bicycle-forces/storyboard.webp

- Frame 1 at 1.4s: https://meetreference.com/media/exp-bicycle-forces/f1.webp
- Frame 2 at 4.2s: https://meetreference.com/media/exp-bicycle-forces/f2.webp
- Frame 3 at 7.0s: https://meetreference.com/media/exp-bicycle-forces/f3.webp
- Frame 4 at 9.7s: https://meetreference.com/media/exp-bicycle-forces/f4.webp
- Frame 5 at 12.5s: https://meetreference.com/media/exp-bicycle-forces/f5.webp
- Frame 6 at 15.3s: https://meetreference.com/media/exp-bicycle-forces/f6.webp
- Frame 7 at 18.1s: https://meetreference.com/media/exp-bicycle-forces/f7.webp
- Frame 8 at 20.9s: https://meetreference.com/media/exp-bicycle-forces/f8.webp
- Frame 9 at 23.7s: https://meetreference.com/media/exp-bicycle-forces/f9.webp

## Links

- Open reference: https://ciechanow.ski/bicycle/
- Original post: https://ciechanow.ski/bicycle/