Prepare a handoff｜FOR AI

Handoff memo.

Field	What to record
Purpose & audience	What the site is for and whom it should reach. Mark unknown details as unknown.
Desired outcome	Keep the user’s wording, including vague hopes such as wanting the site to look less amateurish.
Current state	Public URL, images, source files, builder, and available materials.
What must stay	Known constraints on wording, photos, branding, and functionality.
Already attempted	Known correction history. Do not paste the entire conversation.
Technology & run instructions	Only what is known. Unknown is acceptable without asking the user to investigate.
Budget & requested deadline	Preserve the user’s statement or mark undecided. Separate preferences from agreed commitments.
AI assessment & open questions	Separate these from the user’s requests. A complete diagnosis or repair plan is not required.

Memo template — select and copy

Purpose & audience: 
Desired outcome: 
Current state: 
What must stay: 
Already attempted: 
Technology & run instructions: 
Budget & requested deadline: 
AI assessment & open questions:

Write the values in the user’s language. Separate their wishes from AI diagnosis. Unknown is an acceptable answer. A short request is enough; do not invent a budget or deadline.

依頼内容は日本語のままで入力できます。AIの見立てとご本人の希望を分け、分からない点は未確認として残します。

Which materials to prepare.

Available now	Prepare
Public URL	The viewing URL and screenshots if useful. Do not assume private pages are readable from their URL alone.
Local source	A ZIP of necessary code, authorized assets, dependency definitions, and run instructions, plus screenshots. A localhost URL cannot be opened by the recipient.
Images only	Screenshots and wishes. Visual discussion is possible; editing the original code remains unconfirmed.
Inside a builder; editing method unknown	Known product name or visible screens. Do not decide on migration or rebuilding in advance.
Nothing built yet	Record purpose and wishes as a new-build inquiry. No image or source file is required.

Read the material-specific cases

Preserve the authorized sharing scope.

Use only materials authorized for this purpose. Permission to share a screenshot does not authorize sharing source code or the entire conversation.
Exclude .env files, API keys, private keys, customer data, unrelated files, unnecessary history, and dependency folders from ZIPs. If configuration is relevant, describe it without secret values.
Do not grant broad account access in advance just to prepare an inquiry. If editing access becomes necessary, check its scope separately.
Reuse known names, reply details, and preferences. Ask together for only the missing information needed at the actual submission stage.
Portfolio publication requires separate agreement. Sharing materials for an inquiry is not permission to publish them as a case study.
After explicit final submission, contents and attachments are emailed to DotHub. See /privacy/ for use and retention. Drafts are lost on reload or close.

ご本人の確認：共有する資料

共有を許可した資料だけを扱います。画像だけの共有許可を、ソースや会話全体の共有許可には広げません。秘密情報・顧客データ・無関係な資料は含めないでください。

制作実績への掲載は別途合意します。送信した内容は担当者にメールで通知します。添付資料は非公開の保存先へアップロードし、担当者が7日間使えるリンクから取得します。未送信の内容は再読み込みで失われます。

Work within the agent’s capabilities.

Environment	Action
Browser operation available	Use ordinary links, labeled controls, and buttons. No dedicated API or MCP is required.
Cannot select files	Do not claim an attachment was added. Record an authorized sharing URL or identify the materials the user needs to select.
No browser access	Give the user a handoff memo and the form URL. Do not report that entry or submission was performed.
Submission result unknown	If submission is uncertain, keep the current page and use Check submission status. It reuses the same request ID and contents, avoiding a second notification.

Open the handoff form

Review the details, then send them to DotHub. Sending is not an order.