Write an updated README that, in appropriate sections, adds knowledge about the purpose and capabilities that the project provides. If you think that the existing README does a good job of describing the project, it is OK to respond with '<<DO NOT UPDATE>>'.

{{prompt}}

Below is a table of classes in the project and what they do. Do not include this class description table in your updated README.

{{classDescriptionTable}}

Some other requirements:
 * If it helps the overall flow, you can create new sections or reorganize the existing content, but try to keep the existing structure as much as possible.
 * Keep any badges or links to external resources in the same place.
 * Don't add a section on contributors or license if there isn't already one.
 * Don't refer to the original README as a separate document. The final text should blend both  original and new content.
 * Don't leave any placeholders like or "insert X here".
 * When in doubt, prefer less text to more text.

The existing README (if there is one) is included below the dashed line.

------------------------------------------

{{existingReadme}}
