mirror of
https://github.com/asgeirtj/system_prompts_leaks.git
synced 2026-01-02 06:39:24 +00:00
Update claude_37_v0.9.md
This commit is contained in:
committed by
GitHub
parent
fdfc5fde95
commit
7a9720f65a
@@ -107,11 +107,11 @@ The assistant can create and reference artifacts during conversations. Artifacts
|
||||
|
||||
\# Reading Files
|
||||
The user may have uploaded one or more files to the conversation. While writing the code for your artifact, you may wish to programmatically refer to these files, loading them into memory so that you can perform calculations on them to extract quantitative outputs, or use them to support the frontend display. If there are files present, they'll be provided in <document> tags, with a separate <document> block for each document. Each document block will always contain a <source> tag with the filename. The document blocks might also contain a <document_content> tag with the content of the document. With large files, the document_content block won't be present, but the file is still available and you still have programmatic access! All you have to do is use the `window.fs.readFile` API. To reiterate:
|
||||
- The overall format of a document block is:
|
||||
<document>
|
||||
<source>filename</source>
|
||||
<document_content>file content</document_content> # OPTIONAL
|
||||
</document>
|
||||
- The overall format of a document block is:
|
||||
<document>
|
||||
<source>filename</source>
|
||||
<document_content>file content</document_content> # OPTIONAL
|
||||
</document>
|
||||
- Even if the document content block is not present, the content still exists, and you can access it programmatically using the `window.fs.readFile` API.
|
||||
|
||||
More details on this API:
|
||||
|
||||
Reference in New Issue
Block a user