Iteration Packaging Workflow

Each relevant prompt now advances the canonical documentation package. The assistant must curate the prompt into the docs, emit the next package version, and preserve previous iterations rather than replacing them.

• Daily root folder format: 2026-03-12/ for this work day.
• Canonical docs folder format: canonical-docs-2026-03-12-v03/ and then v04, v05, and so on for later relevant prompts.
• The matching beta file should be versioned alongside the docs, for example index_beta_2026-03-12-v03.html.
• Zip packages must extract into a new versioned folder and overwrite nothing automatically.
• Inside each versioned canonical docs folder, all files keep their normal canonical filenames so deployment copies are still straightforward once a specific version is selected.

Documentation Integration Discipline

Do not treat chat as the long-term memory of the project. The docs are the memory. New rules about shared navigation, freshness timestamps, clickable monospaced URL examples, bug definitions, packaging structure, export behavior, and build workflow must be curated into the correct documents as they are defined.

Developer Guide

developer_en.html

This document describes how developers should understand, extend, and maintain the MyAnythingList system.

1. Development Philosophy

• Preserve simplicity.
• Preserve human-readable text.
• Prefer transparent behavior over hidden logic.
• Document decisions clearly.

2. Core System Components

Playlist text
   ↓
URL discovery
   ↓
Command parsing
   ↓
Tile model creation
   ↓
Thumbnail / QR resolution
   ↓
Grid rendering

3. Playlist Parser

The parser extracts valid URLs from any UTF-8 text.

• URLs may appear anywhere in text.
• Lines beginning with # are comments.
• Commands use the syntax #_Command().

My research notes:

https://example.com/article

#_ReplaceThumbnailWithImage("cover.jpg")

4. Command System

Commands extend playlist behavior.

#_ReplaceThumbnailWithImage("image.jpg")
#_LoadImage("panel.png")
#_LoadImageHideLinks("poster.png")

5. UI State Architecture

Runtime state is controlled by configuration variables.

• ShowControls
• ShowGear
• AutoHideGear
• ShowQR
• ShowTypes
• ShowURLs

• startup configuration
• URL parameters
• UI interaction

6. Thumbnail System

Command thumbnail
→ Uploaded thumbnail
→ Platform thumbnail
→ Fallback image

• QR images must never replace thumbnails.
• Uploaded images must affect only the intended tile.

Developers must treat URL art as a first-class thumbnail mode with real layout requirements, not as throwaway fallback text.

• Best-fit scaling should be attempted before clipping.
• The full URL should remain visible whenever the URL length is within practical bounds.
• Export logic should preserve the same compositional intent seen in the live tile.
• When the footer URL is visible, do not redraw or position the large URL-art block beneath that footer strip.

7. Contribution Guidelines

• Preserve existing behavior unless explicitly redesigned.
• Update documentation when behavior changes.
• Favor readability over cleverness.

Documentation discipline

• Every materially new user request in an active design session should trigger updates to the affected docs.
• Insert new information where future readers will naturally look for it; do not dump all new rules at the bottom of a file.
• For this project, technical documentation often needs expansion rather than summarization. Engineers, future AI instances, and maintainers should get a richer spec after each pass.
• Overwrite-ready bundles may use original in-place filenames even if working copies use dated names during authoring.

8. Long-Term Goal