> For the complete documentation index, see [llms.txt](https://morphic.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://morphic.com/docs/kr/how-tos/storyboarding/storyboarding-using-a-script.md).
# 스크립트를 사용한 스토리보딩
Morphic에서 스크립트를 사용해 스토리보드를 만드는 방법에 대한 간단한 튜토리얼입니다:
1. 이동하세요 [코파일럿](https://studio.morphic.com/chat) Morphic에서
2. “이 장면들의 흑백 스토리보드를 생성해 주세요….”와 같은 프롬프트를 입력하세요.
3. 선택 사항으로, 캐릭터의 동작, 카메라 각도, 분위기 또는 환경을 포함할 수 있습니다.
4. 생성을 클릭해 스토리보드를 만드세요
Copilot은 생성된 이야기나 스크립트를 명확한 시각적 장면으로 나누어 스토리보드 프레임을 생성합니다. 이렇게 Morphic에서 스크립트를 사용해 스토리보드를 만들 수 있습니다. 이는 작성된 스크립트를 명확한 시각적 장면으로 바꾸는 데 도움이 됩니다.
***
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://morphic.com/docs/kr/how-tos/storyboarding/storyboarding-using-a-script.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.