Intuition Check
一款用來測試和訓練直覺的簡單、私密的 App,適用於 iPhone、iPad 和配備 Apple 晶片的 Mac。用撲克牌、數字或影像練習你的直覺,可以一個人玩,也可以和附近的搭檔一起玩。
在 App Store 下載 → 用 AI 製作你自己的猜測集 →直覺
什麼是直覺
直覺是知道某件事,卻說不出自己是怎麼知道的:一種預感、一種說不上來的感覺、一種突如其來的確信。
心理學家對其中一種直覺有清楚的描述:比思考更快發揮作用的經驗。一件事做過很多次的人,在能用言語說明之前,就會察覺到其中的規律:感覺先出現,言語之後才跟上。1
許多人也描述過第二種直覺:知道任何經驗都不可能告訴他們的事,例如在電話顯示名字之前就知道是誰打來的,或是知道蓋著的那張牌是哪一張。這種直覺是否存在,在科學界是有爭議的。23這個 App 讓你測試的正是這第二種直覺,用的是隨機選出的值。
直覺可能如何出現
許多人都熟悉這樣的時刻:
- 你想到某個人,片刻之後對方就打電話來了。
- 你拿起電話想打給朋友,電話卻在你手中響起,打來的正是那位朋友。
- 你在鬧鐘響起前兩三分鐘就醒了。
- 你在看螢幕之前,就知道是誰打來的。
- 你想起一個很久沒見的人,對方當天就打電話來了。
- 你對一個人的第一印象,後來證明是對的。
- 問題的答案自己浮現出來:在早上、在淋浴時、在散步時。
- 你感覺有人在看你,轉過頭去,真的有人在看你。
在英格蘭和加州以隨機選出的民眾為對象的電話調查中,有 65% 到 78% 的人說,他們曾打電話給某人,而對方說自己剛才正要打給他們;也有 47–49% 的人說,他們曾在沒有任何線索的情況下,就知道是誰打來的。45大多數成年人相信,自己感覺得到看不見的人正在注視自己。6
其中有些情況有已知的解釋。身體能掌握你預期醒來的時間:在一項實驗中,一種讓身體準備醒來的荷爾蒙,在人們事先被告知會被叫醒的時間之前大約一小時就開始上升。7暫停一下可能有助於解決問題:在許多實驗中,人們把問題擱置一段時間後,解題表現更好;8在一項研究中,有一項作業藏著一條能讓解題更快的規則,而睡一晚讓發現這條規則的人數比例增加到兩倍以上。9而第一印象可能是準確的:陌生人在關掉聲音的情況下看一位老師總共 30 秒,給出的評價就和這位老師的學生在學期末的評價大致相同。10
一次、兩次,還是一次又一次
一兩次的話,這樣的巧合很容易被當成只是隨機發生的。當它一次又一次發生,人們自然會想知道,這背後是否還有什麼。
在這件事上,記憶是個很差的計數器。它記住電話響起的那些時候,卻忘了有許多次你想到某個人,結果什麼也沒發生。而且,只要日子、人和念頭夠多,驚人的巧合必然會不時發生。11
所以,實際數一數會很有幫助。在這個 App 中,隨機猜中的機率是確切已知的:它只取決於可能抽出的值有多少個。統計會顯示你的結果是落在隨機可得的範圍內,還是偏離了它。請參閱解讀你的結果。
日常生活中的直覺
感覺和來自身體的訊號,會參與許多決定。單純挑選自己喜歡的海報的人,三週後對那張海報的滿意度,比先被要求列出喜歡或不喜歡每張海報的理由的人更高。12在另一項實驗中,人們玩一種有四副牌的紙牌遊戲:其中兩副長期下來會贏,另外兩副會輸,但沒有人告訴玩家是哪兩副。每次抽牌之前,身體都會先有反應,而這些訊號在不同的人身上偏向不同的方向:整體而言,有些人的訊號偏向會贏的那兩副,另一些人的訊號則偏向會輸的那兩副。研究人員以每個人感覺自己心跳的準確程度,來衡量他感覺身體訊號的能力。這種感覺越準確,這個人的選擇就越緊密地跟隨身體的訊號,不論結果是好是壞。13
在有真正的規律可以依靠、又有快速而清楚的回饋時,直覺最可靠。強烈的確信感本身,並不表示你是對的。1
所以,和自己的直覺保持良好的連結,意味著兩件事:察覺它,以及學會分辨什麼時候可以信任它。要學會分辨什麼時候可以信任它,就在玩的時候記錄你的狀態:統計會依狀態和依時段比較你的回合,讓你看出自己什麼時候表現得比較好。請參閱你的狀態。
這背後還有什麼嗎?
人能不能知道任何經驗都無法告訴他們的事,科學界對此沒有定論。2018年,美國心理學會主要期刊上的一篇回顧論文得出結論:支持這類現象的證據,大約和支持心理學中公認研究發現的證據一樣有力。2同一份期刊上的一篇回應則主張,這類現象不可能存在,這些結果一定另有原因。3這個問題懸而未決,而這個 App 讓你可以用自己的回合來觀察它。
App 的運作方式
一個回合
選一個猜測集(撲克牌、數字或一組影像),然後在值出現之前,試著感應它是什麼。接著揭曉它,看看你是否猜對了。App 會計算你命中的次數,並和純粹隨機可得的結果相比較。
被動與主動模式
App 有兩種模式:
- 「被動直覺」:值已經選好並隱藏起來。你要試著讀出它是什麼。
- 「主動直覺」:在你揭曉之前,不會選出任何值。你要試著用意念讓你想要的值出現。
統計會把兩種模式分開記錄,讓你看出哪一種比較適合你。
三種玩法
主介面頂部的切換器用來選擇玩法和模式。「設定」→「玩法與模式」中也有同樣的選項。
逐一
一次一個值。點一下揭曉它,再點一下隱藏它,然後揭曉下一個。在「設定」→「逐一」中開啟「不隱藏,直接揭曉」後,每點一下都會直接揭曉下一個值。「顯示提示」會在值的下方加上一行指引文字。
當「猜測記錄」的「方式」設為「輸入你的猜測」時(一開始就是這樣設定的),每次揭曉前都會先請你輸入猜測,App 也會自己判定這個回合是否命中。請參閱會記錄哪些內容。
快速點選
猜測集的所有值都排列在同一個網格中。每點一下就是一個獨立的回合。在主動模式下,值會在你點選的那一刻隨機抽出;在被動模式下,值則是事先抽出,就在你上一次點選之後。命中時可以用綠色閃光和震動來標示。
超過 1,000 個值的數字猜測集沒有網格:請在該猜測集的設定中縮小範圍,或改用「逐一」玩法。
連續系列
在主動模式下,選一個你想要的值,集中意念想著它,然後點一下:App 會抽出一連串隨機值,並計算其中有多少個與你點的值相符。一個連續系列可以抽 2 到 12 次,或是 100、1,000、10,000、100,000、100 萬或 1,000 萬次。系列長度在主介面上設定。在「設定」→「連續系列」中,「系列時間」滑桿可以把這些抽選分散在最長 10 秒內進行;設為 0 時則沒有停頓。每個連續系列在統計中都記為一條記錄。
選擇「連續系列」時,模式會切換為主動直覺。
撲克牌與數字
撲克牌猜測集使用一副 36 張或 52 張的撲克牌,可以含或不含鬼牌。數字猜測集使用最多 9 位數的數字:最大位數由你選擇。這兩項都在猜測集的設定介面中修改:在主介面上,點一下猜測集切換器旁的齒輪按鈕。
簡潔檢視
在主介面的任何地方按住,即可隱藏切換器、工具列、狀態選擇列和提示。再按住一次,它們就會重新出現。回合數和結果會繼續顯示。
在「設定」→「外觀與回饋」的「簡潔檢視」下方,「顯示按鈕」會在工具列加入眼睛按鈕,點一下它就能開啟簡潔檢視;「記住簡潔檢視」則會讓簡潔檢視在 App 重新啟動後維持開啟。
回合數
主介面可以顯示你玩了幾個回合,以及你的表現如何:每種模式與玩法的組合各有一個回合數和一個結果,還有一個按鈕,可以重置回合數並清除結果。切換到其他猜測集時,也會重置所有的回合數和結果。
若要在 App 重新啟動後保留回合數和結果,請在「設定」→「統計」中開啟「儲存回合數與結果」。這個選項在「在裝置上儲存統計資料」開啟時才能使用。
猜測集
猜測集就是你從中猜測的內容:撲克牌、數字或一組影像。一開始,主介面只顯示「數字」和「撲克牌」。點一下主介面上猜測集切換器旁的 ,就可以加入 App 附帶的其他猜測集。
猜測集切換器
主介面頂部的切換器會顯示你的猜測集。使用預設的「切換器樣式」時,如果要顯示的猜測集有一個或兩個,切換器會顯示按鈕;從三個起則顯示目前猜測集的名稱,由它開啟猜測集列表。在「切換器樣式」中選擇「獨立介面」時,切換器一律開啟這個列表。
每個猜測集都有自己的「使用」開關。關閉這個開關的猜測集不會出現在任何地方:不會出現在主介面的猜測集切換器中,不會出現在搭檔遊戲中,也不會出現在統計中。但它會留在「設定」→「猜測集」→「管理猜測集」的猜測集列表中;再次開啟這個開關,它的統計也會回來。
猜測集切換器旁的 按鈕會打開「加入猜測集」介面。這裡列出 App 附帶的其他猜測集,可以直接加入主介面;下方有一個按鈕,可以建立空白的猜測集,之後再把你自己的影像加進去,還有「你的 AI 助理」區塊,用來加入 AI 助理製作的猜測集。猜測集切換器旁的齒輪按鈕會打開目前所選猜測集的設定。這兩個按鈕都可以在「設定」→「猜測集」中,用「顯示加入猜測集按鈕」和「顯示猜測集設定按鈕」隱藏起來。
現成套組
點一下主介面上猜測集切換器旁的 ,或打開「設定」→「猜測集」→「管理猜測集」,點一下 並選擇「現成套組」。打開一個套組,然後點一下「加入到我的猜測集」。
你加入的猜測集是你自己的副本:你可以為它重新命名、重新排列影像、讓其中一些影像不在遊戲中使用、用它和搭檔一起玩,或傳送給別人。
用自己的影像建立猜測集
在主介面上:點一下切換器旁的 ,然後點一下現成套組下方的「空白影像集」。保留名稱「我的影像」或輸入其他名稱,然後點一下「建立」。App 會切換到這個新的猜測集並打開它。
或者打開「設定」→「猜測集」→「管理猜測集」,點一下 並選擇「空白影像集」,接著為猜測集命名,然後點一下「建立」。新的猜測集隨即打開。
在猜測集裡點一下 ,就能從「照片」或「檔案」加入影像(一次可以加入好幾張),用「相機」一張一張拍攝,或用「從剪貼板貼上」貼上拷貝的影像或 SVG。
影像名稱
在猜測集本身的介面中點一下影像,即可放大檢視。它的「名稱」就是下方的欄位:可以輸入、更改或清除。從「檔案」加入的影像,名稱一開始是檔案名稱(不含副檔名);從「照片」、「相機」或「從剪貼板貼上」加入的影像,一開始沒有名稱。在擁有多種語言名稱的猜測集中,欄位下方的「各語言的名稱」保存這張影像在每種語言中的名稱。影像下方會顯示 App 所保存檔案的格式和大小。
AI 助理可以為你製作影像和整個猜測集:用 AI 製作你自己的猜測集。
順序、版面與參與遊戲的影像
在猜測集的介面中,「排列」可以讓你拖移影像來重新排序,並為網格選擇「每列影像數」、「對齊」和「完整顯示」。
按住一張影像,可以看到更多選項:
- 「不在遊戲中使用」:影像會留在猜測集中,但永遠不會被抽中。「在遊戲中使用」則讓它重新參與遊戲。
- 標示為「?」佔位圖:在「逐一」玩法中,值還隱藏著的時候會顯示這張影像。它本身永遠不會被抽中。每個猜測集最多只能有一張「?」佔位圖。
重新命名與刪除
名稱是猜測集介面中的第一個欄位。在現成套組中,修改它會改變 App 目前語言的名稱;其他語言的名稱位於「各語言的名稱」中。
若要刪除猜測集,請在「設定」→「猜測集」→「管理猜測集」的猜測集列表中滑動它,或按住它,然後選擇「刪除」。App 會先向你確認。猜測集的統計資料也會隨之刪除。
傳送猜測集
傳送一個猜測集
由你自己的影像組成的猜測集,可以裝在一個副檔名為 .guesset 的檔案裡傳送。這個檔案包含影像、影像的順序、版面和猜測集的名稱,以及哪些影像參與遊戲、哪一張是「?」佔位圖。「撲克牌」和「數字」是 App 內建的,無法傳送。
- 打開「設定」→「猜測集」→「管理猜測集」。
- 按住猜測集,然後選擇「匯出⋯」。猜測集裡的分享按鈕也有同樣的作用。
- 選擇傳送方式:「郵件」、「訊息」、AirDrop、「檔案」或其他 App。
要和附近的人一起玩某個猜測集,並不需要檔案:請參閱用你自己的影像來玩。
打開別人傳給你的猜測集
在「郵件」、「訊息」或「檔案」中點一下 .guesset 檔案,或接受透過 AirDrop 傳來的檔案,然後用 Intuition Check 打開。它會成為你自己的一份獨立副本,並出現在你的列表最後面和切換器中。
已經儲存在裝置上的檔案,也可以從 App 內匯入:在「設定」→「猜測集」→「管理猜測集」中點一下 ,然後選擇「從檔案匯入」。
搭檔遊戲
運作方式
兩台裝置一起玩:一個人選一個值,另一個人試著猜出來。兩台裝置只會彼此通訊(在兩者彼此靠近時裝置對裝置,或在兩台裝置共同連上的 Wi‑Fi 網路上)。搭檔遊戲的回合不會計入統計。
連線
在兩台裝置上都開啟 Wi‑Fi。連上同一個 Wi‑Fi 網路時,連線效果最好,而且兩台裝置可以位在這個網路範圍內的任何地方。兩台裝置沒有共同的網路時,會以裝置對裝置的方式連線:請讓它們彼此靠近。
只有在兩台裝置都打開搭檔遊戲時,它們才會尋找彼此。
開始
- 在兩台裝置上都打開搭檔遊戲:點一下主介面工具列中的雙人按鈕,或在「設定」→「搭檔遊戲」中點一下「打開搭檔遊戲」。如果沒有這個按鈕,請在「設定」→「搭檔遊戲」中開啟「顯示搭檔遊戲按鈕」。
- 每台裝置都會先顯示「正在尋找附近的搭檔⋯」,接著在「在附近發現:」下方顯示另一台裝置。兩台裝置會自動連線。
第一次使用時,你的裝置會詢問是否允許 App 尋找你區域網路上的裝置。請允許:沒有這項權限,兩台裝置就無法找到彼此。
一個回合
- 在「使用的猜測集:」下方,選擇要用什麼來玩:任何一個你正在使用的猜測集都可以。
- 選擇角色:「我來選一張牌」(或是數字、影像)或「我來試著猜」。搭檔會擔任另一個角色。
- 負責選的一方選一個值,負責猜的一方做出猜測。接著兩台裝置都會顯示選定的值和猜的值,以及「正確!」或「這次沒中」。
- 「再玩一次」會帶你們兩人回到第一步,為下一個回合選擇要用什麼來玩,以及各自的角色。
用你自己的影像來玩
你用自己的某個影像集來玩時,App 會先請搭檔「下載」這個影像集,除非對方已經有相同的影像集。對方收到的這一份只會用在搭檔遊戲中,絕不會改動對方自己的猜測集。只有對方還沒有的影像才會傳送過去。
如果在「設定」→「搭檔遊戲」中開啟了「保留收到的影像集」,下次和同一位搭檔玩時就不必等待,會直接開始。關閉時,收到的影像集會在你離開搭檔遊戲時刪除。收到的影像集會列在「設定」→「猜測集」→「管理猜測集」的「從搭檔收到的影像集」下方;在那裡,「加入到我的猜測集」會建立一份完全屬於你的副本。
搭檔的名稱
iPhone 和 iPad 上的 App 只能看到一般的裝置名稱,例如「iPhone」,所以兩台裝置可能看起來一樣。連線之後,點一下搭檔名稱旁邊的鉛筆,然後輸入你想用的名稱。這個名稱只會顯示在你的裝置上。
如果兩台裝置找不到彼此
- 在兩台裝置上都打開搭檔遊戲,並開啟 Wi‑Fi。
- 如果可以,讓兩台裝置連上同一個 Wi‑Fi 網路;否則,請讓它們彼此靠近。
- 訪客網路和公共網路(例如飯店、咖啡廳、辦公室裡的網路)常常會阻擋裝置之間的通訊。請試試其他網路,或完全不使用網路,並把兩台裝置並排放在一起。
- 如果你拒絕了區域網路的權限要求,請在「設定」App 中重新開啟這項權限:前往「隱私權與安全性」→「區域網路」,然後開啟 Intuition Check。
- 如果某台裝置出現在「在附近發現:」下方,卻一直沒有連線,請在兩台裝置上都離開搭檔遊戲,再重新打開:搜尋會重新開始。
- 一次只有兩台裝置一起玩。第三台裝置會持續尋找,直到正在玩的兩台中有一台離開為止。
統計
會記錄哪些內容
「快速點選」和「連續系列」一律會記錄你的回合。「逐一」則依照「設定」→「逐一」中「猜測記錄」下的「方式」設定來記錄:
- 「輸入你的猜測」:預設選項。你在揭曉前選好你的猜測,再由 App 為這個回合計分。
- 「自行判定」:每次揭曉後,點一下 ✓ 或 ✗。揭曉後若略過不標記,該次就不會計入。
- 「關閉」:「逐一」不會記錄任何內容。
只有一個可能值的猜測集不會記錄任何內容。搭檔遊戲的回合一律不會記錄。
查看你的統計
點一下主介面工具列中的統計按鈕,或在「設定」→「統計」中點一下「檢視統計」。統計會針對你正在玩的猜測集、玩法和模式打開。頂部的過濾條件可以依「時間範圍」、「猜測集」、「玩法」、「模式」,以及「狀態」(在你記錄狀態時)縮小範圍。
不需要的區塊,可以在統計設定介面中關閉:在統計介面中點一下設定按鈕就能打開它,也可以從主介面透過「設定」→「統計」打開。
這些數字的意思:解讀你的結果。
保留你的統計
一開始,統計資料只會在本次執行期間保留在記憶體中:App 結束時就會清除,包括 iOS 在背景中將它關閉的情況。如要保留統計資料,請開啟「在裝置上儲存統計資料」,它位於統計介面頂部,也位於「設定」→「統計」中。本次執行期間的回合也會一併儲存。先前執行期間從未儲存的回合無法找回。
關閉這個開關會刪除已儲存的統計資料。App 會先詢問「要停止儲存統計資料嗎?」;點一下「刪除已儲存的統計資料」後,只會留下自上次打開 App 以來玩過的回合,而且只保留在記憶體中:App 關閉後它們就會消失。此動作無法還原。
清除
在統計介面底部:
- 清除「…」的全部統計:過濾條件中所選猜測集記錄的全部統計。
- 「刪除過濾後的統計記錄(… 條)」:只有過濾條件所顯示的記錄。
- 「清除全部統計」:全部內容。
App 會請你確認上述每一項刪除,而且任何一項都無法還原。
匯出
點一下統計介面工具列中的分享按鈕,然後點一下「將統計資料匯出為文字檔案」。這個檔案是一份表格(CSV),內容正好就是你的過濾條件所顯示的記錄:每個回合一列,在「連續系列」玩法中則是每個系列一列。Numbers 等試算表 App 可以開啟它。你也可能會發現,把這個檔案拿給你使用的 AI 助理看並問它問題很有用,例如:「我的直覺在什麼情況下似乎發揮得比較好,在什麼情況下比較差?」
解讀你的結果
統計不只是計算命中次數。它會把你的結果和隨機猜測在可能值數量相同時會得到的成績互相比較,並用簡單的話告訴你:你是高於隨機水準、低於隨機水準,還是與隨機水準相當。
你的結果與隨機水準
在「猜對次數」下方,「你的結果」會和「隨機可得」並列顯示。同樣的 30% 可能代表相反的意思:有 3 個可能值時,隨機猜測約可得到 33%,所以 30% 略低於隨機水準;如果是 52 張牌,隨機猜測約可得到 2%,所以 30% 遠高於隨機水準。隨機命中率會依照每個回合各自的可能值數量計算。
判定
App 會給出判定:從「與隨機水準相當」,經過略高於或略低於隨機水準、明顯高於或明顯低於隨機水準,一直到「遠高於隨機水準」或「遠低於隨機水準」。App 也會告訴你,對隨機猜測來說這樣的結果有多罕見,例如「大約每 300 次才會出現一次」。
回合數少時,光是隨機就會造成很大的起伏。所以每多一個回合,判定就會更穩定一些。
被動直覺與主動直覺的比較
當你在兩種模式下都有回合時,「被動直覺與主動直覺的比較」會顯示各自的命中次數和命中率,讓你看出哪一種比較適合你。「連續系列」玩法不會顯示這個區塊。
最長連續命中
「最長連續命中」會列出你連續猜對次數最多的幾次,並附上日期和時間,以及你當時記錄的狀態。間隔若超過「回合之間的最長間隔」(你可以在這個區塊中設定),連續命中就會中斷;你記錄的狀態改變時也一樣。
隨時間的變化
當你在兩個不同的日子都有回合之後,「命中率隨時間的變化」會畫出你每天的命中率。「依時段」會把上午、下午、晚上和凌晨分開顯示。
各個值
當統計只顯示單一猜測集的資料,而且這個猜測集最多有 100 個值時,會列出你最常猜對的值,以及你最常和最少選作猜測的值;一旦你猜測的次數和這個猜測集的值一樣多,連你從未選過的值也會列出。
人們常常會偏好某些值、避開其他值,而某些值也可能比其他值更常被猜對。
結果可能會變動
你的結果可能會隨你的狀態和情況而改變。以下內容都不是定論,而是你在玩的時候值得留意的可能性:
- 你的狀態。剛起床時或深夜時、精神飽滿或疲倦時、平靜或緊張時,你的表現可能會不一樣。玩的時候記錄你的狀態,統計就會依狀態和時段比較你的回合。
- 自信。對自己有把握或充滿懷疑,都可能和你的得分有關聯。
- 低於隨機水準也算數。猜對的次數明顯少於隨機預期,也是一種偏離隨機的情形。其中一種解讀是:在那個時刻,直覺正在跟你作對,而不是什麼事都沒有發生。
- 各個值。你猜對某些值的次數可能遠多於其他值,有些值你可能一次都猜不對,即使你選它們的次數和其他值一樣多。
數字能告訴你什麼
App 能告訴你,你的結果是否偏離純粹的隨機,但永遠無法告訴你原因,即使從資料看來原因似乎很明顯。請把這些數字當作可以探索的東西,而不是衡量你自己的固定標準。另請參閱直覺。
你的狀態
狀態選擇列
主介面上的狀態選擇列可以讓你記錄自己此刻的狀態:「精神飽滿」或「疲倦」、「平靜」或「緊張」、「有把握」或「沒把握」、「專注」或「分心」、你的心情,以及像是「剛起床」、「喝咖啡後」或「運動後」這類情況。你記錄的狀態會和你從那時起玩的每一個回合一起記錄下來,直到你變更它,或 App 忘記它為止。
這樣一來,統計就會依狀態和時段比較你的回合,而每一次連續命中都會顯示你當時記錄的狀態。請參閱結果可能會變動。
何時忘記記錄的狀態
由「設定」→「你的狀態」中的「重置記錄的狀態」決定:
- 「App 啟動時」:預設選項。下次啟動時,不會有任何記錄的狀態。
- 「暫停後」:如果你沒有玩的時間超過你選擇的「暫停時間」(15 分鐘到 1 天),App 就會忘記它。
- 「永不」:會一直保留,直到你變更為止。
你自己的狀態
在「設定」→「你的狀態」→「管理狀態」中,你可以重新命名、重新排序、加入和隱藏狀態,加入你自己的維度,也可以用維度自己的「使用」開關把它關閉:關閉的維度會離開狀態選擇列,新的回合不會記錄它,統計中也不會包含它。
如要完全移除狀態選擇列,請關閉「在回合中記錄你的狀態」;這樣就完全不會記錄任何狀態。
簡潔檢視開啟時,以及在「逐一」玩法中關閉「猜測記錄」時,狀態選擇列會隱藏。
外觀與功能
主題
「設定」→「外觀與回饋」中有四種主題:「沙色」、「海洋」、「森林」和「黃昏」,每一種都有淺色和深色版本。「外觀」可以選擇「淺色」、「深色」或「系統」;選擇「系統」時,App 會跟隨你裝置的設定,並隨之切換。主題也會為撲克牌和現成套組中的大部分影像上色。
回饋
在「命中回饋」下方,「震動」和「動畫」會用一陣震動和一道綠色閃光標示猜對;任一項都可以關閉。它們適用於「快速點選」玩法中的每一次點選、「連續系列」玩法中每次抽選都命中的系列,以及在「逐一」玩法中於揭曉前輸入猜測的情況。沒猜中時既不會震動,也不會閃光。震動還需要開啟「系統觸覺回饋」,這個選項位於「設定」App 的「音效與觸覺回饋」中。
「點一下時的脈動動畫」會讓你在「快速點選」和「連續系列」中點一下的格子,以及你在「逐一」中自行判定回合或不記錄回合時所揭曉的值,短暫地脈動一下。
更清爽的主介面
主介面上幾乎所有東西都可以隱藏。每個開關都位於它所屬的「設定」介面中:
- 「設定」→「玩法與模式」:兩個「顯示切換器」開關,一個用於玩法,一個用於模式。
- 「設定」→「猜測集」:「顯示切換器」、「顯示加入猜測集按鈕」、「顯示猜測集設定按鈕」。
- 「設定」→「快速點選」:「顯示網格選項按鈕」。
- 「設定」→「逐一」:「顯示提示」。
- 「設定」→「連續系列」:「在主介面顯示系列長度」、「在主介面顯示系列時間」、「顯示網格選項按鈕」(與「設定」→「快速點選」中的是同一個開關)。
- 「設定」→「你的狀態」:「在回合中記錄你的狀態」。
- 「設定」→「統計」:「顯示統計按鈕」。
- 「設定」→「搭檔遊戲」:「顯示搭檔遊戲按鈕」。
- 每種玩法的設定(「快速點選」、「逐一」、「連續系列」):「顯示回合數」、顯示「結果」開關、「顯示結果」。
如要讓某個猜測集不出現在切換器中,請在該猜測集的設定中關閉「使用」;這樣它也會從搭檔遊戲和統計中消失。開啟簡潔檢視會一次隱藏主介面上的大部分元素。
功能
「設定」→「功能」中有「連續系列玩法」的開關,以及「主介面上的回合數與結果」的開關。關閉後,該功能就會從主介面和「設定」中消失。
語言
「設定」→「語言」可以設定 App 的語言,不受裝置語言影響,也會決定數字和日期的寫法。在「建議的語言」下方,列表會先顯示系統語言,再依照裝置上設定的順序顯示裝置語言中 App 提供的每一種;其餘所有語言接著列在「其他語言」下方。如果新語言的閱讀方向和原本相反,切換後請關閉 App 再重新打開(書寫方向要在重新啟動後才會正確切換)。
在「設定」的「語言」列下方,有一個開關:在「設定」中顯示提示。它會顯示或隱藏各項設定下方的說明。
免費的 1 小時與訂閱
免費的 1 小時
App 可以免費下載,並附有 1 小時的 App 內使用時間,讓你試用 App 中的所有內容。這 1 小時只會在 App 開啟並顯示在螢幕上時計算,而且會把你每次執行的時間累計起來:App 關閉或在背景中時,不會計時。
這 1 小時用完後,訂閱介面會自動打開。如果這段時間還不夠你決定是否訂閱,你可以再多用一些時間:「重置免費的 1 小時」可以再給你 1 小時,最多 3 次,總共 4 小時的免費時間。
訂閱
之後若要繼續使用 App,可以選擇訂閱,訂閱有兩種方案:「每月」和「每年」。訂閱支援「家人共享」。
如何訂閱
打開「設定」→「訂閱」→「立即訂閱」。
管理或取消訂閱
訂閱的費用由 Apple 收取。「設定」→「訂閱」→「管理訂閱」會帶你前往你的訂閱。你也可以用標準方式管理這個 App 的訂閱:在裝置的設定中,透過你 Apple 帳號的訂閱項目。取消訂閱會停止之後的自動續訂,但在目前的期間結束之前,你仍然可以繼續使用。
每月方案的訂閱者可以透過「設定」→「訂閱」→「改用年度方案」換成年度方案。
退款
退款由 Apple 處理:請前往 reportaproblem.apple.com 申請。我們無法存取你的付款資料,也無法自行退款;但如果出了問題,也請寫信告訴我們,因為這是我們得知問題的唯一方式。
回復購買項目
在新裝置上,打開「設定」→「訂閱」→「立即訂閱」,然後點一下「回復購買項目」。這也會回復家庭成員與你共享的訂閱。請使用當初訂閱的 Apple 帳號,或同一個「家人共享」群組中的帳號。
你的資料
簡而言之
沒有帳號,也沒有伺服器。App 不會把你的資料傳送給我們或其他任何公司。搭檔遊戲只會和另一台裝置交換資料:在兩台裝置共同連上的 Wi‑Fi 網路上,或在兩者彼此靠近時裝置對裝置。
存放在哪裡
你的設定、你的猜測集(包括你加入的影像)以及你的狀態清單,都儲存在你的裝置上,也就是 App 自己的儲存空間中。在你開啟「在裝置上儲存統計資料」之前,統計資料只會在 App 執行期間保留在記憶體中。
就像任何其他 App 的資料一樣,這些內容都會包含在你裝置的備份中。
App 不含數據分析,也不含當機回報。
寫信給我們時
你寄給我們的電子郵件屬於一般的往來信件:我們只會在回覆你所需的時間內保留它。
所有細節都在隱私權政策中。
用 AI 製作你自己的猜測集
你可以請 AI 助理(例如聊天機器人)為猜測集畫影像,或製作整個猜測集。這些影像是 SVG 圖畫。SVG 影像中的文字可以有多種語言,App 會以 App 所設定的語言顯示這些文字。影像也可以採用 App 主題的顏色,淺色和深色版本都可以。猜測集可以有自己的「?」佔位圖,也就是值隱藏時顯示的影像。AI 助理需要格式說明;下方每個請求都附有這份說明的網址。
製作猜測集
- 把下方其中一個請求拷貝到 AI 助理中,再依你的喜好修改主題、影像數量(2 到 200 張)和語言。
- 如果 AI 助理無法打開網頁,也要把格式說明交給它:在給 AI 的格式說明部分點一下「拷貝」,把說明貼到同一個對話中;或點一下「儲存」,再附上儲存的檔案。
- AI 助理回覆時,會把猜測集放在一個程式碼區塊中,前後常常附有幾句說明。只要拷貝程式碼區塊就好:在許多聊天 App 中,程式碼區塊有自己的拷貝按鈕。
- 在 App 中,點一下主介面上的 ,然後在「加入猜測集」介面點一下「從剪貼板貼上」。如果 AI 助理是在另一台裝置上(例如 Mac)使用,請在那台裝置上把程式碼區塊儲存成檔名以 .json 結尾的檔案,然後改為點一下「從檔案匯入」。新的猜測集會被加入並選定;點一下「開始猜測」即可回到主介面。這些步驟的正下方也有同樣的按鈕。
如果出現錯誤,請 AI 助理修正。
不含說明文字的猜測集:
請為 Intuition Check 這個 App 製作一個名為「動物」的猜測集:10 張不同動物的 SVG 影像,不含說明文字。請先閱讀格式說明並照著做:https://intuition-check.com/llm-formats.txt每張影像都有說明文字的猜測集。說明文字不會隨 App 的語言改變:
請為 Intuition Check 這個 App 製作一個名為「水果」的猜測集:8 張不同水果的 SVG 影像,每張圖畫下方都有說明文字,寫出水果的名稱。請先閱讀格式說明並照著做:https://intuition-check.com/llm-formats.txt有多種語言名稱的猜測集。每段說明文字都會用 App 的語言顯示影像的名稱:
請為 Intuition Check 這個 App 製作一個名為「行星」的多語言猜測集:8 張行星的 SVG 影像,每張都有說明文字,用 App 的語言顯示影像的名稱。請提供繁體中文、德文和印地文的名稱。請先閱讀格式說明並照著做:https://intuition-check.com/llm-formats.txt影像會採用 App 主題顏色的猜測集:
請為 Intuition Check 這個 App 製作一個名為「天氣」的猜測集:8 張 SVG 影像,分別是太陽、雲、雨、雪、雷雨、風、霧和彩虹,不含說明文字。它們的顏色必須跟著 App 的主題變化,淺色和深色版本都要。請先閱讀格式說明並照著做:https://intuition-check.com/llm-formats.txt製作一張影像
AI 助理也可以只製作一張影像。拷貝它的程式碼區塊,打開你自己的其中一個影像集,點一下 ,再點一下「從剪貼板貼上」。影像加入時沒有名稱:點一下影像,在「名稱」中輸入名稱。你也可以把程式碼區塊儲存成檔名以 .svg 結尾的檔案,然後在影像集中點一下 ,選擇「檔案」;不含 .svg 的檔案名稱就會成為影像的名稱。
請為 Intuition Check 這個 App 畫一張貓的 SVG 影像。請先閱讀格式說明並照著做:https://intuition-check.com/llm-formats.txt猜測集還可以有什麼
請 AI 助理說明格式允許哪些做法,並為每一種可能各給一個請求範例:
請閱讀 Intuition Check 這個 App 的格式說明,然後用簡短、淺白的話告訴我,猜測集和影像可以做到哪些事:影像如何跟著 App 的主題變化(不同的主題、淺色和深色版本);猜測集和其中影像的名稱如何加上其他語言的翻譯;影像可以有哪些種類的說明文字;猜測集的「?」佔位圖(它的背面)可以顯示什麼。每一種可能,都給我一個我可以傳給你的請求範例。先不要畫任何東西。格式說明在這裡:https://intuition-check.com/llm-formats.txt給 AI 的格式說明
格式說明是用英文寫的,是給 AI 助理看的,不是給人閱讀的。網站上也有同樣的說明,網址就在上方的請求中。
This is a specification for language models; it is not formatted for human reading.
Format version: 1
Stable URL: https://intuition-check.com/llm-formats.txt
# Intuition Check: how to make SVG pictures and guess sets
Intuition Check is an iOS app. The app picks one picture of a guess set, hidden, and the user guesses which one.
A guess set is a named, ordered list of pictures. This text tells you how to produce (A) a whole guess set as
one JSON object, or (B) one picture as one SVG document, so that the app accepts it and draws it well.
The user's wishes always win. Every rule, default and style advice in this text is what you do when the user
has not said otherwise: anything the user asks for — any texts, any number of them, any place, size, shape,
colour or layout, a caption over the drawing, a word along an arc — overrides it. Only facts about the app
cannot be overridden, because the app enforces them (what it accepts and refuses, what it removes, how it
draws: sections 2, 3, 5 and the theme rules of 6 — but a sentence there that tells you what to do is still a
default, not a fact about the app); if a wish runs into one of them, do the closest thing the app allows and
say so.
## When the user asks what the formats allow (to explain, not to make)
Answer in the user's language, in plain words, without code. Keep apart what the app does and what you do by
default. The sizes, positions and orders in this text, and its sentences that tell you what to do ("put",
"give", "write", "keep"), are your defaults for a good result: the app does not check them and the user may
ask otherwise. Do not retell them as rules of the app ("must", "required", "not allowed"); say "by default I …".
What the app itself does:
- Themes: four themes, each light and dark. The app never recolours a picture on its own; a picture follows
the theme only where its own file says so (section 6), which you write when asked.
- Names: a set needs a name; a picture's name is optional. The set and every picture may have translations,
each its own languages; the app shows the one for the app language, else the default name.
- Captions: text in a picture is part of the drawing; the app never writes or translates it. A caption is one
fixed text, or holds versions in any number of languages, two included, and the app language picks one.
- The "?" placeholder: a set without a cover shows the app's own "?". The app draws no cover itself. A cover
is a picture like any other: it may show anything, with or without text, follow the theme and the app
language, and stand anywhere in the set.
- Limits: at least 2 pictures to guess (a cover is not one of them), at most 200 in all, 10 MB per SVG; one
refused picture refuses the whole set.
Do not translate the themes' code words (section 6).
Terms used below:
- name: the picture's name as stored in the app (`name`, `nameTranslations`). It is data, not part of the drawing.
- caption: a text drawn inside the picture (an SVG `<text>`). Optional. See section 4.
- app language: the language the app's interface is set to, in the app itself; it may differ from the device's
language. One of the codes in section 3.
- user's language: the language the user writes to you in, unless the user names another.
## 1. Output contract
A. The user asks for a SET (several pictures, "guess set", "set"):
- Answer with ONE JSON object as defined in section 2, in ONE code block. Nothing else is needed.
- If you add words outside the code block, they must not contain `{` or `}`: the app reads the pasted text
from the first `{` to the last `}`.
- Before or after the code block, tell the user in one short sentence, in the user's language, to copy the
code block (chat apps usually show a copy button on it) and paste it into Intuition Check as a new set — or,
on another device, to save it as a file whose name ends in .json and open that file in the app.
B. The user asks for a single PICTURE:
- Answer with ONE SVG document (section 5) in ONE code block.
- If you add words outside the code block, they must not contain `<svg` or `</svg>`: the app reads the
pasted text from the first `<svg` to the last `</svg>`.
- Before or after the code block, tell the user in one short sentence, in the user's language, to copy the
code block and paste it into one of their picture sets in Intuition Check; the picture is added without a
name. Or to save it as a file whose name ends in .svg and add that file to a set: the file name without
".svg" becomes the picture's name, so suggest a file name that is the name, e.g. `Cat.svg`.
In both: do not name the app's buttons or screens from memory, and do not translate their names yourself. The
app's help exists in every language of the app, with the exact names the app shows in that language; the steps
are in its section "#ai_sets", and the page for each language is listed in https://intuition-check.com/llms.txt. If
you can open web pages and the user wants the steps, take the names from the page in the user's language.
Otherwise the one sentence above is enough: the app's help and its own screens show the user where to paste.
Ask first, or proceed:
- Proceed without questions. Decide what the request leaves open, and say what you decided in a sentence or
two beside the code block:
- which things of a kind ("five animals": choose the animals);
- how many pictures, if no number is given: 4;
- the regional form of the user's language: take the likeliest and name it (e.g. "Canadian French");
- translations: as well as you can; name the languages you are least sure of;
- themes not mentioned: fixed colours, and one sentence that a version following the app's themes can be
made;
- a cover with nothing said about what it shows: the question mark (8c).
- Ask only when you cannot start: you cannot tell which language the names should be in, or the request names
no subject at all. Then at most 2 questions, in ONE message, in the user's language, each with the choice
you will make if the user does not mind; no code block in that message. Never ask what the message already
says. Plain words: no "code block", "JSON", "opaque", "plate", "import", nothing about how the format works.
- If you cannot ask (there is no dialogue), or the user tells you not to: proceed.
- What you say beside the code block is in the user's words: "its own background", not "opaque plate";
language names, not codes; at most four short points. The file endings .json and .svg are allowed: the
user needs them.
- Like all words outside the code block: no `{` or `}` next to a set, no `<svg` next to a picture. Do not
quote code outside the code block.
Defaults when the request does not say otherwise:
- No caption text in the drawing (section 4, option 1).
- No theme colours (section 6). Fixed colours of your own.
- Names: always give every picture a `name`, in the user's language. Give no `nameTranslations` unless the
user asks for other languages or for captions in several languages (section 4, option 4).
- Number of pictures: what the user asked for; never fewer than 2 or more than 200.
- No cover (section 2). A cover the user asks for is extra: it is not one of the pictures asked for.
## 2. The set format (JSON)
```json
{
"intuitionCheckSet": 1,
"name": "Animals",
"nameTranslations": { "ru": "Животные", "de": "Tiere" },
"images": [
{ "name": "Cat", "nameTranslations": { "ru": "Кот", "de": "Katze" }, "svg": "<svg xmlns=\"http://www.w3.org/2000/svg\" viewBox=\"0 0 100 100\"><circle cx=\"50\" cy=\"56\" r=\"30\" fill=\"#f57c00\"/><path d=\"M24 44 L28 14 L48 30 Z M76 44 L72 14 L52 30 Z\" fill=\"#f57c00\"/></svg>" },
{ "name": "Fish", "nameTranslations": { "ru": "Рыба", "de": "Fisch" }, "svg": "<svg xmlns=\"http://www.w3.org/2000/svg\" viewBox=\"0 0 100 100\"><ellipse cx=\"44\" cy=\"50\" rx=\"30\" ry=\"18\" fill=\"#1976d2\"/><path d=\"M70 50 L92 32 L92 68 Z\" fill=\"#1976d2\"/></svg>" }
]
}
```
(The drawings above are kept tiny to show the shape of the file. More examples are in section 8.)
Keys:
- `intuitionCheckSet` (required): the integer 1.
- `name` (required): the set's default name. Not empty.
- `nameTranslations` (optional, on the set and on each image): object, language code → name. Codes: section 3.
- `images` (required): array of at most 200 objects, at least 2 of them pictures to guess (a cover is one
more, not one of the 2).
Array order = display order. Each object:
- `name` (optional in the format; always give it): the picture's default name.
- `nameTranslations` (optional): as above.
- `svg` (required): one complete SVG document as a JSON string (section 5).
- `cover` (optional): the JSON literal `true` on the picture that is the set's cover (below). Leave it out
on every other picture.
- Unknown keys are ignored. Do not add any.
The cover: while the app hides the value to guess, it shows a "?" in its place. A set — any set, with or
without captions — may bring its own picture for that place: the cover. Give one ONLY when the user asks for
it (a cover, a back, a placeholder, a question-mark picture). It shows what the user wants: for a set of
playing cards, for example, the pattern of a card's back. If the user does not say what it shows, draw the set's
own frame, with a question mark where the other pictures have their subject (8c; the last picture of 8f);
when the pictures' plates differ in colour, a plate of the same family (8f: a neutral grey). Exactly one
picture gets `"cover": true` (if several do, the first counts and the others are ordinary pictures). The
cover is never an answer, so the set still needs at least 2 other pictures. Put it last in `images` (your default; the app takes it at any place). Give it
a `name` in words ("Question mark", not "?") and, in a multilingual set, `nameTranslations` in the same
languages as the pictures: the app shows the cover's name in the set's list of pictures, in the app language.
By default the cover has no caption (no word under it); the app draws any text it has. Its question mark is the cover's subject; it only borrows the
`class="caption"` pattern of section 4, option 4, so that it changes with the app language. Write the mark
as text (preferred) in two forms: `?`, and `؟` for Arabic and Urdu (the form those languages write). The app
does not change the mark itself: the cover holds both, and its own style sheet shows the one for the app
language. That works in every set, also in one without captions; the two marks are then its only `<text>`. Drawn as a
shape instead, the mark is the same in every app language: Arabic and Urdu see the Latin form. A cover with
a subject of its own (a card back, a cloud) needs no `<text>` and no style sheet.
A single picture (answer B) has no cover key: the user marks a picture as the cover inside the app. A single
picture meant as a cover and asked with a caption: do both, and say that the word will show on the cover.
Rules:
- Strict JSON, UTF-8: no comments, no trailing commas. Non-ASCII characters may be written as they are.
- Inside the `svg` string escape `"` as `\"` and `\` as `\\`; write the SVG on one line, or write each line
break as `\n`. No raw line break or tab inside a JSON string. Where you join two lines, put one space,
never nothing. No other escape is needed: an apostrophe stays `'` (`\'` is not JSON), and letters of any
script stay as they are.
- Types: `intuitionCheckSet` is the number 1, every name and translation is a string, `cover` is `true`. A
wrong type (`"cover": "true"`, a number as a name, `null` as a translation) makes the app refuse the whole
text.
- If the app refuses any one picture, it imports nothing and names the refused pictures. Every picture must
be valid.
- A name is one line of plain text. The app trims it, turns line breaks and tabs into spaces, and cuts it at
256 characters. Keep names short (one to three words): they are shown small.
How names are shown:
- A set is multilingual when the set or any image has at least one translation.
- In a multilingual set the app shows, for the app language: the translation with exactly that code; else
the translation with the code's first part (`fr-CA` → `fr`, `en-GB` → `en`, `es-419` → `es`); else the
default `name`.
- In a set without translations the app shows the default `name` in every app language.
When the user asks for a multilingual set:
- Default `name` (set and images): in the user's language.
- `nameTranslations`: one entry per requested language, on the set AND on every image. Give the same
languages on every image (the app does not require it: an image without an entry shows its default name).
- The language of the default `name` gets no entry of its own: a language without an entry shows the default
name.
- A regional code (`en-AU`, `en-CA`, `en-GB`, `es-419`, `fr-CA`) needs its own entry only when its word
differs from the `en` / `es` / `fr` entry. `pt-BR` and `pt-PT` have no common code: each requested one that
is not the language of the default `name` needs its own entry (asked for "Portuguese" with an English default
name: give both). The same for `zh-Hans` and `zh-Hant`.
- A regional form named alone ("British English", "Canadian French") goes under the parent code (`en`, `fr`,
`es`), in names as in captions: every form of that language then shows it.
- Languages not named ("a multilingual set"), or "all languages": every language of section 3 — 53 codes,
47 entries (see there). Translate as well as you can (section 1). Leave out only a language you cannot
write at all (it then shows the default name), and tell the user which.
- `nameTranslations` change only names, never a caption. A multilingual set has no captions unless the user asks for them; a
caption drawn inside the pictures needs its own words for each language in the SVG itself (section 4,
option 4).
## 3. Language codes
Write the codes exactly as here (case matters):
ar bg bn ca cs da de el en en-AU en-CA en-GB es es-419 fi fr fr-CA gu he hi hr hu id it ja kk kn ko lt ml mr ms
nb nl or pa pl pt-BR pt-PT ro ru sk sl sv ta te th tr uk ur vi zh-Hans zh-Hant
A code that is not in this list is not an error: the app drops it. An entry
with an empty value is dropped.
"All languages" is 53 codes but 47 entries besides the default, in names and in captions: the user's language
is the default and needs none, and `en-AU`, `en-CA`, `en-GB`, `es-419`, `fr-CA` show the `en` / `es` / `fr`
word unless theirs differs. (With a Bengali default, `en` is one of the 47 and `bn` is not.)
## 4. Captions (text inside the drawing): four options
Names (section 2) are separate from captions: the app never writes a name into a picture and never changes any
text of a picture. Give names always. Text in, on or under the picture — whatever the user calls it (name,
word, label) — is a caption request; a wish about the words alone (correct, careful) is not. If you leave out
something that was asked for, say so. Lettering that is part of the subject (STOP on a road sign) is
drawing, not a caption: allowed under every option, written once, with `lang`.
Urdu is drawn in Nastaliq, its own style, which reaches lower under the line than other scripts (about
0.3 × font-size): leave room under an Urdu caption. A `؟` in Urdu is smaller in Nastaliq: give it its own text and size (8c).
A caption's `lang` may be a regional code (`en-GB`, `fr-CA`), also where its name stands under the parent code.
Choose the caption option from the request:
1. DEFAULT — no caption. The drawing has no `<text>` that spells the name. Also for a multilingual set
whose user did not ask for captions.
2. ONE-LANGUAGE caption — when the user asks for a caption / label / word in or under the picture and names
no languages for it. A plain `<text>` with the word in the user's language; every app language shows
that same word. Put `lang="CODE"` of the caption's language on the `<text>`: a picture
with text is drawn anew for each app language, and without `lang` the letter forms follow the app language. No
`letter-spacing` in Arabic, Hebrew, Thai or an Indic script. Example:
`<text lang="ru" x="50" y="91" font-size="12" font-family="sans-serif" text-anchor="middle" fill="#222222">Кот</text>`
3. TWO LANGUAGES AT ONCE — when the user names exactly two languages for the word under the picture and does
not say it should change with the app's language. The same for any other text of the picture: each gets its
two lines. Two `<text>` lines, each with its `lang`, both always
shown, no style sheet for them: the user's language on top, font-size 10, baselines at y = 84 and 95,
subject in the upper 68 units (100-unit viewBox). A line in a script of 8b's "Lettering" block takes that
`font-family` as an attribute; a long word follows "Size" below. Names: the user's language as `name`,
the other in `nameTranslations`. Say that both words always show, and that captions that change with the
app's language can be made instead.
4. CAPTIONS IN SEVERAL LANGUAGES — when the user names three or more languages for the captions, or asks for
captions in all of the app's languages, or for captions that follow the app's language (= all of them).
The picture holds one caption per language and a small style sheet; through that style sheet the app
language picks the caption (8b, 8f). Languages: exactly those the user named; "all" = every language of
section 3 (53 codes, 47 entries: see there), translated as well as you can (section 1). In a set, give
every image `nameTranslations` with the same languages and the same words, so that the name and the
caption agree.
How option 4 works:
- A picture that contains `<text` or `:lang(` is drawn anew for each app language it is shown in, each time
inside an HTML page whose language is that app language: `<html lang="CODE">`, CODE from section 3 (`ru`,
`pt-BR`, `zh-Hant`, …). The app changes nothing in the file; the file's own CSS picks the caption with the
selector `:lang()`.
- `:lang(x)` matches a page in `x` and in every `x-…`: `:lang(fr)` also matches `fr-CA`, `:lang(es)` also
`es-419`, `:lang(en)` also `en-GB`. `pt-BR` and `pt-PT`, `zh-Hans` and `zh-Hant` are written separately.
- The pattern:
- All language versions of one text in ONE group with `class="caption"`; each `<text>` in it is one
language version, all at the same place.
- Any number of texts, anywhere and in any form (labels on parts, a title, words along an arc with
`<textPath href="#id">`): give each text its own group with `class="caption"` holding its language
versions; the one style sheet serves them all.
- The default caption has the class `default`. It carries the word of the default `name`, in the user's
language. It is shown when the page has no language and in every language that has no caption of its
own. The user's language is one of those: its code stands in no rule and on no caption. (In 8b and 8f
the default word is English, so `en` appears nowhere. The Zodiac files call this class `en`.) The
default caption is also shown on pages of other languages: give it `lang="CODE"` of the user's language.
If that language has a line in the "Lettering" block of 8b, add `.default` to that line's selector
(`.default, .hi, .mr { font-family: … }`; `.default` alone when no caption has that class), and to the
`letter-spacing: 0` line if you use letter-spacing.
- Every other caption's `class` lists the codes of the languages that show it. Languages with the same
word may share one caption: `class="bg ru"`; that changes only the `class`, never the style sheet. These
captions need no `lang`: each shows only on a page of its own language.
- The style sheet, in this order:
`.caption text { display: none }` — hide every caption;
`.caption .default { display: inline }` — show the default one;
`:lang(ar, bg, …) .default { display: none }` — hide the default one in every language that has its own
caption (list them all);
`:lang(ar) .ar, :lang(bg) .bg, … { display: inline }` — show each language's own caption.
- A regional code whose word differs from its parent's (`es-419` next to `es`): its own caption, its code in
both rules like any other, and one more rule: `:lang(es-419) .caption .es { display: none }` (the extra
`.caption` makes it win wherever it stands in the sheet). If its word is the parent's, give it nothing.
- A regional form named alone ("British English", "Canadian French") goes under the parent code (`en`,
`fr`, `es`), so every form of that language shows it. "Portuguese" alone: one caption
`class="pt-BR pt-PT"` when the word is the same.
- Do not repeat the default word under the user's own code (no caption, no rule, no `nameTranslations`
entry for it).
- Check: the codes in the hiding rule = the codes in the showing rule = the codes on the captions, and
each code is on exactly one `<text>`; the user's own code is in none of the three. Otherwise a language
shows no caption, or two at once.
- To leave a language out: no `<text>` for it and its code in neither rule. It then shows the default
caption.
- In a set: the same style sheet, the same attributes on the caption group and the same languages in every
picture, character for character. Only the words differ, and the size of a long word. (A cover has its
own text and rules: 8c, 8f.)
- Size: the app does not measure or shrink text. Choose one `font-size` on the group at which the captions
fit the free width. A word too long for it: first its own smaller `font-size` attribute, down to 9 (on a
100-unit viewBox); if it still does not fit, a shorter everyday word (and the same word as its name).
Never under 9. To estimate a width (measured in WebKit on a Mac):
- ordinary case in bold `sans-serif` (8f): 0.45 to 0.6 × font-size per letter. Треугольник is 77 of 100
units wide at font-size 12, and 68 at 10.5;
- a Chinese character: about 1 × font-size;
- Indic scripts, Thai, Arabic, Hebrew in bold `sans-serif`: 0.3 to 0.55 × font-size per code point (13
words measured).
- Case: ordinary case, as in 8f; capitals with wide spacing only for the style of 8b. Capitals follow each
language's rules: Turkish i → İ; Greek capitals lose the accent (ΑΣΤΈΡΙ → ΑΣΤΕΡΙ); German ß → SS.
- Fonts: copy the "Lettering" block of 8b (in a set, only the lines of the scripts you use). It gives every
script outside Latin, Cyrillic and Greek its own font list (fonts present on Apple devices, at a weight
they really have), and sets `letter-spacing` to 0 for Arabic, Hebrew, Thai and the Indic scripts — in most
of them the letters join or stack, and spacing breaks that (a line needed only when the group has
letter-spacing). Japanese, Chinese and Korean each get their
own font so that a Han character takes its regional form; that is why `zh-Hans` and `zh-Hant` keep
separate captions even with the same word.
- Direction: the page is left-to-right in every app language. Keep `text-anchor="middle"` for every script.
An Arabic, Hebrew or Urdu caption mixed with digits or Latin letters has not been tested: avoid it.
- A caption drawn twice (e.g. a shadow under it): put the group once inside `<defs>` with an `id`, and draw it
with two `<use href="#id">` that carry the colours and the offset.
- Whole set: captions and names in all languages fit in one answer. Write every language that was asked for, in
every picture. Do not ask about it, and do not tell the user it may not fit. In a set, leave out comments
and indentation.
- Never: fewer languages than asked without saying which are missing; captions left out when they were asked
for; one set spread over several messages or delivered as single pictures; a set cut short. A set is
always ONE JSON object in ONE message.
Start from 8f (a small set with captions and a cover, 100-unit viewBox). Take from 8b (a picture with a
caption in every language) its "Lettering" block, and its gold medallion style only when the user asks for
it; 8c is that set's cover. All three are complete and tested in the app. 8b and 8c are built like the app's
own Zodiac set; one of its files, if you can open web pages (you do not need it):
https://intuition-check.com/sets/zodiac/zodiac-08-scorpio.svg
## 5. The SVG document: what the app does with it
Facts (from the app's code):
- Size limit: 10,000,000 bytes per SVG (UTF-8). A larger SVG is refused.
- The app recognises an SVG by the characters `<svg` within the first 4096 bytes. Begin the document with
`<svg`: no XML declaration, DOCTYPE or comment before it.
- The app draws the SVG into a still bitmap, at most 1600 pixels on the longer side, with WebKit, inside an
HTML page. A picture with text is drawn anew for each app language it is shown in, and one with theme
rules for each theme. The background is transparent: where the drawing paints nothing, the app's own
background shows, light or dark depending on the user's theme.
- Scaling: the root's `viewBox` is fitted into the bitmap, aspect ratio kept, centred. `width` and `height`
on the root are ignored. A picture without a `viewBox` is accepted, but drawn unscaled (cut off or tiny):
always write one.
- The aspect ratio is read from the first `viewBox="minx miny width height"` in the first 4096 bytes: double
quotes, four numbers separated by spaces or commas, positive finite width and height. If it cannot
be read, the bitmap is square. Ratios outside 1:20 … 20:1 are clamped.
- `preserveAspectRatio="none"` on the root is replaced with `xMidYMid meet`: a picture is never stretched.
- Scripts never run. Nothing is loaded from the network: only content inside the file is drawn.
- Rendering has a time limit (10 seconds to load, 10 seconds to draw). A picture that exceeds it is refused.
Removed before drawing (so never write them; the rest of the picture is still drawn):
- these elements with everything inside: `script`, `foreignObject`, `meta`, `link`, `base`, `iframe`, `frame`,
`frameset`, `object`, `embed`, `applet`, `portal`, `form`, `input`, `button`, `textarea`, `select`, `option`,
`audio`, `video`, `source`, `track`, `template`, `noscript`;
- every attribute whose name starts with `on` (`onload`, `onclick`, …);
- every `href` / `xlink:href` whose value does not start with `#` (a part of the same file) or `data:image/`;
- `@import` in a style sheet; `<?xml-stylesheet …?>`; a DOCTYPE with an internal subset (`[ … ]`).
The removal works on the text of the file: the character sequences `on…=`, `href=` and `@import` are also
removed from text content and CSS, so do not write them there.
Allowed and drawn: shapes, `path`, `g`, `text`, `tspan`, gradients (`linearGradient`, `radialGradient`),
`pattern`, `mask`, `clipPath`, `filter`, `defs`, `symbol`, `use` with `href="#id"`, `<style>` with inline CSS,
`title`, `desc`, `image` with `href="data:image/…"` (a picture embedded in the file).
Not removed, but useless: `a` (a link does nothing in a picture in the app).
Rules for the SVG you write:
1. Root: `<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 100 100">` … `</svg>`. Double-quoted
attributes. Lower-case `<svg`. One root; no nested `<svg>` elements.
2. Square `viewBox` (`0 0 100 100`) unless the user asks for another shape. The same `viewBox` for every
picture of a set.
3. Self-contained: no external images, fonts, style sheets or links. For text use
`font-family="sans-serif"` (or `serif`, `monospace`), or the font lists of 8b, which end with one of them:
the text is drawn with the device's own fonts.
4. Well-formed XML: every element closed, attribute values quoted, `&` `<` `>` in text and attribute values
written as `&` `<` `>`. Only SVG elements; no HTML elements.
5. Readable small: the app shows pictures in a grid, each cell may be small. One clear subject that fills
most of the viewBox; a few large shapes; strong contrast; no fine detail. On a 100-unit viewBox: the
subject's lines at least 2 wide, a caption's font-size at least 10, a long word 9. Ornament may be
thinner (the rings of 8b); in a small cell it may not be seen. The examples in this text are bare on
purpose; do not copy their simplicity. Build the subject from about 4 to 10 shapes: its outline, its
parts, and one or two details that make it this thing and no other. Someone who sees only the picture
must be able to name it.
Pale or pastel colours: keep the silhouette. The subject's main shape, or an outline around it, must differ
from the plate by at least 3:1 — a darker outline, or a deeper plate. That is for the silhouette only:
details inside the subject are free.
6. Distinct: the game needs the pictures told apart at a glance. Every picture of a set must differ clearly
from every other in silhouette or in main colour — not only in a detail. No two pictures with the same
SVG text.
7. One style across a set: the same viewBox, margins, line weights, palette family, and the same kind of
background (all with a plate, or all without). With captions: the same lettering and caption place in
every picture.
8. Background: the bitmap is transparent and the app's background can be light or dark. Either draw an
opaque plate of your own behind the subject (e.g. `<rect width="100" height="100" rx="12" fill="…"/>`), or
use only colours that stay visible on both white and near-black, or use theme colours (section 6).
9. Unique `id` values inside one SVG. Ids of different pictures do not clash (each picture is drawn alone).
Do not start an id with `ic-` unless it is a theme rule, and do not name a class of your own `ic-…` or a
variable `--ic-…` (section 6).
10. Keep it light: no heavy filters (large blurs), no deep `use` nesting, no animation (the app does not remove it, but
draws the picture as a still image).
11. A caption must not cross the drawing, unless the user allowed it (labels on the drawing's parts, a word on
a sign or over the subject are such wishes). Any text stays inside its own shape when it has one (a sign,
a label, a slice), and inside the picture. Keep the subject and the caption
apart — e.g. on a 100-unit viewBox: the subject above y = 78 and one caption line with its baseline at
y = 91; with two lines (section 4, option 3), the subject above y = 68.
## 6. Theme colours
Use this section ONLY when the user asks for pictures that follow the app's theme, or for light and dark
versions. Otherwise use fixed colours, no id that starts with `ic-`, no class `ic-…` and no variable
`--ic-…`. When the user said nothing about
themes: fixed colours, and offer a version that follows the themes (section 1). "Looks good in light and dark
mode" is not a theme request: an opaque plate with fixed colours does it (section 5, rule 8). A theme request
wins over a colour description in the same message ("gold on dark, matching the app's themes": theme rules).
The app has four themes — `sand`, `ocean`, `forest`, `dusk` — each in a `light` and a `dark` version. These words
(and `light`, `dark`) are code words for the rules below, not what the user sees: the app shows the four themes
under its own names in the user's language. When you talk to the user, do not translate the code words
yourself; say "the app's four themes" (and "light" / "dark" in the user's language), or, if you can open the
app's help page in the user's language (see section 1), take the themes' names from it.
Every version has its own values for five colours:
- `background` — the colour behind every view;
- `surface` — plates and panels on a view;
- `text` — the app's text colour;
- `accent` — the colour of buttons that are not filled;
- `soft` — in a light version the same as `accent` (a `soft` part on an `accent` part cannot be seen there);
in a dark version a pale tone close to the text colour.
The values (#rrggbb), in the order background, surface, text, accent, soft:
- sand light: f6f2ea eae3d5 403a35 645339 645339
- sand dark: 1b1a18 282622 c7c4bd b89b70 d2cbbe
- ocean light: eef4f7 dde8ee 363d40 3e5a6a 3e5a6a
- ocean dark: 0d1a23 16272f bec4c7 82a3b6 c6d4db
- forest light: f1f4ec e1e8d7 353e34 4a5e46 4a5e46
- forest dark: 111a14 1b261e bec4bd 8ba586 c9d4c6
- dusk light: f6f1f6 eae0ec 3f3944 5e4a6a 5e4a6a
- dusk dark: 17121c 231b2a c2bdc5 a894b4 d3c9d9
All four themes are muted: no colour above is bright. `text`, `accent` and `soft` on `background` or `surface`
have a contrast of at least 5.6:1 in every version.
Fixed colours and theme colours mix freely: give rules only to the parts that should follow the theme (a plate,
outlines, the main shape) and keep your own fixed colours where the picture needs them (the arcs of a rainbow,
a red apple). A part without a rule is drawn as written in every theme.
A part that keeps a fixed colour sits on a plate that changes: check it against the light and the dark
background and surface values of the table. Near-black vanishes on the dark ones (#1b1b1b: 1.01:1), white and
yellow on the light ones (#ffffff: 1.11:1, #f9a825: 1.54:1). Give such parts the theme's text colour — in a
style sheet `fill: var(--ic-text, #333333)` (or `stroke:`), with ids `ic-text` or `ic-stroke-text` — or
use a mid-tone (#e53935: 3.30:1 on the light ones, 3.57:1 on the dark ones).
Captions on a themed plate take the theme's text colour. In a style sheet: one more line,
`.caption { fill: var(--ic-text, #222222) }`, in the sheet that already picks the caption; a single `<text>`
gets a class and the same line; a caption drawn twice through `<use>` gets the class on the `<use>` that
carries its colour (8b). With ids: give the caption group `id="ic-text"` and a written `fill`; the group may
also carry `class="caption"`; a single `<text>` may carry the id itself. A themed cover's mark is coloured
the same way.
There are two ways to write theme colours, and the app reads both. Use a style sheet (6.1), also when the
user will edit the file in Inkscape (6.4). Use ids (6.2) instead when the user says the file will be edited
in Figma, Illustrator, Affinity or Sketch, or asks for ids: those editors write the file anew and drop its
`<style>` element, while ids can come through as layer names (Figma only with its option to include ids).
One way per picture, and in a set the same way in every picture: the app accepts both in one file, but a
rule in a group's id overrides the sheet colours of the classed shapes inside that group.
### 6.1 A style sheet
The app adds to the root `<svg>` the classes `ic-sand` | `ic-ocean` | `ic-forest` | `ic-dusk` and `ic-light` |
`ic-dark`, and defines the CSS variables `--ic-background`, `--ic-surface`, `--ic-text`, `--ic-accent`,
`--ic-soft` — but only if the file contains, in its `<style>` element, one of those six class names after a
dot (e.g. `.ic-dark`), or, in `<style>` or in a `style` attribute, a variable name that starts with `--ic-`.
```
.plate { fill: var(--ic-surface, #dddddd) }
.leaf { fill: var(--ic-accent, #e53935) }
.ic-dark .dot { fill: #ffd54f }
.ic-forest.ic-dark .dot { fill: #69f0ae }
```
The second value inside `var()` is the colour other viewers show. Give the styled elements a `class` and no
`fill` in a `style` attribute. The second value is needed: always write it.
- The five variable names are the only ones. Another name (`--ic-bg`) is never defined: its second value is
drawn in every theme.
- Write `var(--ic-…)` inside the `<style>` element, not in a `fill="…"` or `stroke="…"` attribute: the app
does not look there, and with no other mention it defines no variables.
- The app writes the six classes on the root. Never write one of them on an element yourself.
- A sheet rule beats a colour written in a `fill` / `stroke` attribute; a colour in a `style` attribute beats
the sheet.
- Of two sheet rules of equal weight the later one wins: plain rules first, then `.ic-light` / `.ic-dark`
rules, then theme rules.
- Put these lines into the same `<style>` as the caption rules of section 4, when the picture has them.
### 6.2 Rules in an id
A rule = optional limits + a colour.
- Limits, at most one of each kind, any order: a theme (`sand` | `ocean` | `forest` | `dusk`); a version
(`light` | `dark`); a paint (`fill` | `stroke`). No limits = every theme, both versions, fill and stroke.
- Colour: one of the five names above, or your own colour as exactly six hex digits (`1e88e5`). Colour words
(`red`) are not colours in a rule. All rule words are English.
`id="ic-` + one or more rules, all words joined by hyphens, own colours without `#`:
- `ic-text` — the text colour everywhere;
- `ic-light-accent-dark-soft` — accent in light versions, soft in dark versions;
- `ic-dark-1e3a2a` — own colour in dark versions; as drawn in light versions;
- `ic-ocean-dark-c3ced4` — own colour in the dark version of Ocean only;
- `ic-stroke-accent` — accent on the outline only.
- `ic-fill-accent-stroke-text` — two rules in one id: accent inside, text colour on the outline.
Reading stops at the first character that is not an ASCII letter, digit or hyphen, and at the first word that
is not a rule word. So keep ids unique with a numeric suffix: `ic-text-2`, `ic-text-3`. A word of your own
ends the rules: `ic-moon-text` holds no rule. A six-letter word of hex digits (`facade`) is read as a colour.
What a rule does:
- The id may be on a shape, a `text`, or a group `g`. A rule on a group covers everything inside it, except
what is inside `defs`, a gradient, `mask`, `pattern`, `clipPath`, `marker`, `symbol` or `filter`.
- For each element, fill and stroke are chosen separately. Its own rule is used when one applies in the
current theme and version; otherwise the rule of the innermost enclosing group that has one that applies;
otherwise the colour stays as drawn.
- Among several rules of one element that apply: theme + version beats theme, theme beats version, version
beats no limit; then a rule with `fill` / `stroke` beats one without; then the first one written.
- The chosen colour replaces a plain colour written in the element's `fill` / `stroke` attribute or in its
`style` attribute. Left as written: `none`, `transparent`, `currentColor`, `inherit`, `url(…)` (gradients),
`var(…)`, and colours with their own alpha (`#rrggbbaa`, `#rgba`, `rgba(…)`, `hsla(…)`).
- A `path`, `rect`, `circle`, `ellipse`, `polygon`, `polyline`, `text` or `use` with no `fill` written gets
the chosen fill added. A `line` does not. A stroke is never added: a rule colours a stroke only where a
`stroke` with a plain colour is written on that element itself (not only on its group).
- So, to be safe: write `fill="#rrggbb"` (and `stroke="#rrggbb"` where there is an outline) on every element
that a rule should colour. These written colours are also what other SVG viewers show.
- A `stop-color` or `color` written on a covered element is replaced too (by the fill colour, else by the
stroke colour). A gradient with a rule in its own id has its stops recoloured.
- Theme rules are not applied to an SVG with more than 50,000 tags; it is drawn as written.
- Do not colour the same element both ways. When an element with a `class` has a rule — its own or its
group's — the app writes the rule's colour into the element's `style` attribute, which beats the sheet
(unless the sheet says `!important`): a group's rule so overrides the sheet colours of the classed shapes
inside it. On an element without a `class` the sheet wins wherever one of its selectors reaches it.
### 6.3 Other ways the app reads (do not use unless asked)
- A `<desc>` directly inside an element, beginning with `Intuition Check`, then one rule per line as
`limits: colour` (e.g. `dark stroke: text`, `light: #1e88e5`); a first-line form `Intuition Check: text`.
- Inkscape swatches (a one-colour gradient whose label or id holds rules).
### 6.4 If the user wants to edit the file in Inkscape later
Inkscape keeps both ways, in Inkscape SVG and in Plain SVG.
- A style sheet (6.1): Inkscape keeps the `<style>` element with the `var()` inside it. Write `var()` only
there, never in a `style` attribute (Inkscape removes such an attribute when the element is edited), and add
`!important` to every colour in the sheet (Inkscape writes colours into the element's `style` attribute,
which otherwise wins).
- Ids (6.2): Inkscape keeps ids. Labels are lost in Plain SVG.
## 7. Checklist — run before answering
For a set:
1. The answer is one code block holding one JSON object; it parses as strict JSON.
2. `"intuitionCheckSet": 1` is present; `name` is not empty.
3. `images` has 2 to 200 entries: exactly the number of pictures the user asked for, plus the cover if
there is one.
4. Every image has a non-empty `name` and an `svg` string.
5. In every `svg` string each `"` is written `\"`, and there is no raw line break.
6. Language codes are from section 3, spelled exactly. In a multilingual set every image and the set have
the same languages.
7. Captions follow section 4: none by default; one language only if asked, with `lang` on the `<text>`
two named languages: two lines, both shown, each with `lang`; three or more, or all, only if the user
named them or asked for all. Then: the default caption has `lang`; the codes in the hiding rule = the
codes in the showing rule = the codes on the captions, each on exactly one `<text>`; the same style sheet
in every picture but the cover; every image has `nameTranslations` with the same languages and words.
8. A cover only if asked: one picture with `"cover": true`, last, plus at least 2 other pictures.
9. The answer is whole: the JSON ends with its `}`, and no picture was shortened or left for later.
10. Beside the code block: the sentence on how to use it, and what you assumed (section 1).
For every SVG (in a set or alone):
11. Starts with `<svg`, has `xmlns="http://www.w3.org/2000/svg"` and `viewBox="0 0 W H"` in double quotes,
ends with `</svg>`.
12. Well-formed: all elements closed, `&` `<` `>` escaped in text.
13. None of: `script`, `foreignObject`, `a`, `style` with `@import`, `on…` attributes, `href` to anything
but `#id` or `data:image/…`, external fonts, HTML elements, nested `svg`, animation.
14. Far under 10,000,000 bytes.
15. The subject is large, simple, high-contrast; the picture differs clearly from every other picture of the
set; it is visible on a light and on a dark background; no caption crosses the drawing.
16. Theme rules only if asked; without them no id starts with `ic-` and the style sheet has no `.ic-` class
and no `--ic-` variable. With them: one method in the picture, the same in every picture of the set.
Style sheet: `<style>` itself holds a `--ic-` variable or one of the six classes (a `var()` only in a
`fill` attribute does nothing); the variable names are the five of section 6; every `var()` has a second
value. Ids: every word after `ic-` is a rule word; the element has its `fill` (and `stroke`) written.
Every fixed colour left on a themed plate was checked against the light and the dark values.
17. Ids are unique within the SVG.
## 8. Complete examples
### 8a. Minimal set, no captions
```json
{
"intuitionCheckSet": 1,
"name": "Shapes",
"images": [
{ "name": "Circle", "svg": "<svg xmlns=\"http://www.w3.org/2000/svg\" viewBox=\"0 0 100 100\"><rect width=\"100\" height=\"100\" rx=\"12\" fill=\"#fff4d6\"/><circle cx=\"50\" cy=\"50\" r=\"30\" fill=\"#e53935\"/></svg>" },
{ "name": "Triangle", "svg": "<svg xmlns=\"http://www.w3.org/2000/svg\" viewBox=\"0 0 100 100\"><rect width=\"100\" height=\"100\" rx=\"12\" fill=\"#e3f2fd\"/><path d=\"M50 18 L84 78 L16 78 Z\" fill=\"#1565c0\"/></svg>" }
]
}
```
### 8b. One picture with a caption in every language (section 4, option 4)
A star in a gold medallion with its caption in all 53 languages, built like the app's Zodiac set: the
"Theme" block turns the gold to bronze in light versions (section 6.1), the "Language" block picks the
caption, the "Lettering" block gives each script its font. Languages with the same word share a caption;
es-419 and fr-CA follow es and fr; a page with no language, or one not listed, shows the default caption,
"STAR" (the user's language is English here). The "Theme" block is not part of option 4: this medallion has
no plate, and its gold has to darken on a light background. Without a request for theme colours leave that
block out and draw an opaque plate (section 5, rule 8), as 8f does.
```svg
<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 512 512">
<style>
/* Theme. The app gives the root the classes ic-light or ic-dark (and ic-<theme>).
The gold is drawn for a dark background; on a light one it turns bronze. */
.ic-light .gold-top { stop-color: #A47A2A }
.ic-light .gold-bottom { stop-color: #6A4A14 }
.ic-light .gold-text { fill: #7A5A1E }
.ic-light .shadow-text { opacity: 0.12 }
.ic-light .shadow-glyph { stroke-opacity: 0.27 }
/* Language. Every caption is in the file once; its class names the languages that
show it. The page's language (html lang) picks the caption; without a language,
or with one not listed here, the default one. fr-CA follows fr, es-419 follows es. */
.caption text { display: none }
.caption .default { display: inline }
:lang(ar, bg, bn, ca, cs, da, de, el, es, fi, fr, gu, he, hi, hr, hu, id, it, ja, kk,
kn, ko, lt, ml, mr, ms, nb, nl, or, pa, pl, pt-BR, pt-PT, ro, ru, sk, sl, sv, ta,
te, th, tr, uk, ur, vi, zh-Hans, zh-Hant) .default { display: none }
:lang(ar) .ar, :lang(bg) .bg, :lang(bn) .bn, :lang(ca) .ca, :lang(cs) .cs, :lang(da) .da,
:lang(de) .de, :lang(el) .el, :lang(es) .es, :lang(fi) .fi, :lang(fr) .fr, :lang(gu) .gu,
:lang(he) .he, :lang(hi) .hi, :lang(hr) .hr, :lang(hu) .hu, :lang(id) .id, :lang(it) .it,
:lang(ja) .ja, :lang(kk) .kk, :lang(kn) .kn, :lang(ko) .ko, :lang(lt) .lt, :lang(ml) .ml,
:lang(mr) .mr, :lang(ms) .ms, :lang(nb) .nb, :lang(nl) .nl, :lang(or) .or, :lang(pa) .pa,
:lang(pl) .pl, :lang(pt-BR) .pt-BR, :lang(pt-PT) .pt-PT, :lang(ro) .ro, :lang(ru) .ru,
:lang(sk) .sk, :lang(sl) .sl, :lang(sv) .sv, :lang(ta) .ta, :lang(te) .te, :lang(th) .th,
:lang(tr) .tr, :lang(uk) .uk, :lang(ur) .ur, :lang(vi) .vi, :lang(zh-Hans) .zh-Hans,
:lang(zh-Hant) .zh-Hant
{ display: inline }
/* Lettering. A script whose letters join or stack gets no letter-spacing; every script
outside Latin, Cyrillic and Greek gets its own font. Telugu at 500: iOS has Kohinoor
Telugu only up to Medium, and WebKit would fake a 600 from it. */
.ar, .ur, .he, .bn, .gu, .hi, .mr, .kn, .ml, .or, .pa, .ta, .te, .th { letter-spacing: 0 }
.ar, .ur { font-family: system-ui, -apple-system, Geeza Pro, sans-serif }
.he { font-family: system-ui, -apple-system, Arial Hebrew, sans-serif }
.bn { font-family: Kohinoor Bangla, Bangla Sangam MN, sans-serif }
.gu { font-family: Kohinoor Gujarati, Gujarati Sangam MN, sans-serif }
.hi, .mr { font-family: Kohinoor Devanagari, Devanagari Sangam MN, sans-serif }
.kn { font-family: Noto Sans Kannada, Kannada Sangam MN, sans-serif }
.ml { font-family: Malayalam Sangam MN, Malayalam MN, sans-serif }
.or { font-family: Noto Sans Oriya, Oriya Sangam MN, sans-serif }
.pa { font-family: Mukta Mahee, Gurmukhi Sangam MN, sans-serif }
.ta { font-family: Tamil Sangam MN, InaiMathi, Tamil MN, sans-serif }
.te { font-family: Kohinoor Telugu, Telugu Sangam MN, sans-serif }
.th { font-family: Thonburi, Noto Sans Thai, sans-serif }
.ja { font-family: Hiragino Sans, Hiragino Kaku Gothic ProN, sans-serif }
.ko { font-family: Apple SD Gothic Neo, Noto Sans KR, sans-serif }
.zh-Hans { font-family: PingFang SC, Heiti SC, sans-serif }
.zh-Hant { font-family: PingFang TC, Heiti TC, sans-serif }
.te { font-weight: 500 }
</style>
<defs>
<linearGradient id="gold" gradientUnits="userSpaceOnUse" x1="120" y1="90" x2="400" y2="420">
<stop class="gold-top" offset="0" stop-color="#FBE9AE"/>
<stop class="gold-bottom" offset="1" stop-color="#C08F2C"/>
</linearGradient>
<!-- The captions. Drawn twice at the end of the file: the shadow, then the gold. A long
word would carry its own smaller font-size and letter-spacing. Urdu says lang="ur" and is
drawn in Nastaliq. zh-Hans and zh-Hant keep two captions
with the same word: each takes its own font. -->
<g id="caption" class="caption" text-anchor="middle" font-family="Helvetica Neue, Helvetica, -apple-system, sans-serif" font-weight="600" font-size="52" letter-spacing="6.8">
<text class="default" x="259.4" y="466">STAR</text>
<text class="ar" x="259.4" y="466">نجمة</text>
<text class="bg ru" x="259.4" y="466">ЗВЕЗДА</text>
<text class="bn" x="259.4" y="466">তারা</text>
<text class="ca es" x="259.4" y="466">ESTRELLA</text>
<text class="cs" x="259.4" y="466">HVĚZDA</text>
<text class="da nb" x="259.4" y="466">STJERNE</text>
<text class="de" x="259.4" y="466">STERN</text>
<text class="el" x="259.4" y="466">ΑΣΤΕΡΙ</text>
<text class="fi" x="259.4" y="466">TÄHTI</text>
<text class="fr" x="259.4" y="466">ÉTOILE</text>
<text class="gu" x="259.4" y="466">તારો</text>
<text class="he" x="259.4" y="466">כוכב</text>
<text class="hi mr" x="259.4" y="466">तारा</text>
<text class="hr" x="259.4" y="466">ZVIJEZDA</text>
<text class="hu" x="259.4" y="466">CSILLAG</text>
<text class="id ms" x="259.4" y="466">BINTANG</text>
<text class="it" x="259.4" y="466">STELLA</text>
<text class="ja" x="259.4" y="466">星</text>
<text class="kk" x="259.4" y="466">ЖҰЛДЫЗ</text>
<text class="kn" x="259.4" y="466">ನಕ್ಷತ್ರ</text>
<text class="ko" x="259.4" y="466">별</text>
<text class="lt" x="259.4" y="466">ŽVAIGŽDĖ</text>
<text class="ml" x="259.4" y="466">നക്ഷത്രം</text>
<text class="nl" x="259.4" y="466">STER</text>
<text class="or" x="259.4" y="466">ତାରା</text>
<text class="pa" x="259.4" y="466">ਤਾਰਾ</text>
<text class="pl" x="259.4" y="466">GWIAZDA</text>
<text class="pt-BR pt-PT" x="259.4" y="466">ESTRELA</text>
<text class="ro" x="259.4" y="466">STEA</text>
<text class="sk" x="259.4" y="466">HVIEZDA</text>
<text class="sl" x="259.4" y="466">ZVEZDA</text>
<text class="sv" x="259.4" y="466">STJÄRNA</text>
<text class="ta" x="259.4" y="466">நட்சத்திரம்</text>
<text class="te" x="259.4" y="466">నక్షత్రం</text>
<text class="th" x="259.4" y="466">ดาว</text>
<text class="tr" x="259.4" y="466">YILDIZ</text>
<text class="uk" x="259.4" y="466">ЗІРКА</text>
<text class="ur" lang="ur" x="259.4" y="466">ستارہ</text>
<text class="vi" x="259.4" y="466">NGÔI SAO</text>
<text class="zh-Hans" x="259.4" y="466">星星</text>
<text class="zh-Hant" x="259.4" y="466">星星</text>
</g>
</defs>
<circle cx="256" cy="210" r="148" fill="none" stroke="url(#gold)" stroke-width="6" opacity="0.85"/>
<circle cx="256" cy="210" r="136" fill="none" stroke="url(#gold)" stroke-width="2" opacity="0.5"/>
<path class="shadow-glyph" d="M256 112L279.5 179.6L351.1 181.1L294 224.4L314.8 292.9L256 252L197.2 292.9L218 224.4L160.9 181.1L232.5 179.6Z" fill="none" stroke="#0E0D22" stroke-width="19" stroke-linejoin="round" opacity="0.45" transform="translate(3,5)"/>
<path d="M256 112L279.5 179.6L351.1 181.1L294 224.4L314.8 292.9L256 252L197.2 292.9L218 224.4L160.9 181.1L232.5 179.6Z" fill="none" stroke="url(#gold)" stroke-width="19" stroke-linejoin="round"/>
<path d="M256 112L279.5 179.6L351.1 181.1L294 224.4L314.8 292.9L256 252L197.2 292.9L218 224.4L160.9 181.1L232.5 179.6Z" fill="none" stroke="#FFF6DA" stroke-width="4.5" stroke-linejoin="round" opacity="0.4" transform="translate(-2,-3)"/>
<g fill="none" stroke="url(#gold)" stroke-width="3" opacity="0.55" stroke-linecap="round">
<path d="M150 396h68M294 396h68"/>
</g>
<path d="M256 390 262 396 256 402 250 396Z" fill="url(#gold)" opacity="0.75"/>
<use href="#caption" class="shadow-text" fill="#0E0D22" opacity="0.45" transform="translate(2,4)"/>
<use href="#caption" class="gold-text" fill="#CA9E41"/>
</svg>
```
In a set this SVG is the image's `svg` string (on one line, `"` written `\"`). The image's `name` and
`nameTranslations` carry the same words as the captions, in ordinary case ("Star", "Звезда", "Étoile", …).
Every picture of the set lists the same languages.
### 8c. The cover of the set in 8b
The same medallion with a question mark instead of the subject (section 2, "The cover"); in a set it gets
`"cover": true`. Two marks: `?`, and `؟` for Arabic and Urdu. A cover may show anything else the user asks
for; this one is what to draw when the user does not say.
```svg
<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 512 512">
<style>
/* Theme: the same rules as every picture of the set. */
.ic-light .gold-top { stop-color: #A47A2A }
.ic-light .gold-bottom { stop-color: #6A4A14 }
.ic-light .gold-text { fill: #7A5A1E }
.ic-light .shadow-text { opacity: 0.12 }
/* Language. Two marks: "?" for every language, the Arabic question mark for Arabic and Urdu. */
.caption text { display: none }
.caption .default { display: inline }
:lang(ar, ur) .default { display: none }
:lang(ar) .ar, :lang(ur) .ur
{ display: inline }
</style>
<defs>
<linearGradient id="gold" gradientUnits="userSpaceOnUse" x1="120" y1="90" x2="400" y2="420">
<stop class="gold-top" offset="0" stop-color="#FBE9AE"/>
<stop class="gold-bottom" offset="1" stop-color="#C08F2C"/>
</linearGradient>
<!-- The question mark, where the other pictures have their subject. Drawn twice below: the
shadow, then the gold. The marks differ in shape (Arabic ؟ in Naskh, Urdu ؟ in Nastaliq), so
each has its own size and place: the same ink box as "?". -->
<g id="mark" class="caption" text-anchor="middle" font-family="system-ui, -apple-system, sans-serif" font-weight="bold">
<text class="default" x="258" y="323.8" font-size="323">?</text>
<text class="ar" lang="ar" x="254.2" y="329.6" font-size="294.1">؟</text>
<text class="ur" lang="ur" x="258.4" y="325.6" font-size="317.3">؟</text>
</g>
</defs>
<circle cx="256" cy="210" r="148" fill="none" stroke="url(#gold)" stroke-width="6" opacity="0.85"/>
<circle cx="256" cy="210" r="136" fill="none" stroke="url(#gold)" stroke-width="2" opacity="0.5"/>
<use href="#mark" class="shadow-text" fill="#0E0D22" opacity="0.45" transform="translate(3,5)"/>
<use href="#mark" class="gold-text" fill="#E2C378"/>
<g fill="none" stroke="url(#gold)" stroke-width="3" opacity="0.55" stroke-linecap="round">
<path d="M150 396h68M294 396h68"/>
</g>
<path d="M256 390 262 396 256 402 250 396Z" fill="url(#gold)" opacity="0.75"/>
</svg>
```
### 8d. One SVG picture with theme colours (style sheet)
The plate takes the theme's surface colour, the moon the accent colour, soft in dark versions; the second
values are what other viewers show.
```svg
<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 100 100">
<style>
.plate { fill: var(--ic-surface, #dddddd) }
.moon { fill: var(--ic-accent, #e53935) }
.ic-dark .moon { fill: var(--ic-soft, #e53935) }
.cut { fill: var(--ic-surface, #dddddd) }
</style>
<rect class="plate" width="100" height="100" rx="12"/>
<circle class="moon" cx="46" cy="48" r="28"/>
<circle class="cut" cx="59" cy="39" r="23"/>
</svg>
```
### 8e. One SVG picture with theme colours (ids)
The plate takes the theme's surface colour, the house the text colour, the door the accent colour; the sun is
accent in light versions and soft in dark versions. The written `fill` values are what other viewers show.
```svg
<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 100 100">
<rect id="ic-surface" width="100" height="100" rx="12" fill="#eeeeee"/>
<g id="ic-text">
<path d="M16 52 L50 22 L84 52 Z" fill="#333333"/>
<rect x="26" y="52" width="48" height="30" fill="#333333"/>
</g>
<rect id="ic-accent" x="44" y="60" width="12" height="22" fill="#e53935"/>
<circle id="ic-light-accent-dark-soft" cx="82" cy="18" r="8" fill="#f9a825"/>
</svg>
```
### 8f. A small set with captions in three languages, and a cover
The user writes in English and asks for captions in English, German and Russian, and for a cover. The
default caption is the English word, so `en` is in no rule. Ordinary case, `sans-serif`, no letter-spacing;
the long Russian word has its own smaller size. Both pictures to guess have the same style sheet. The
cover's mark follows the app language, whatever the languages of the captions: `؟` in Arabic and Urdu, `?`
in every other. No theme rules: every picture has an opaque plate.
```json
{
"intuitionCheckSet": 1,
"name": "Simple shapes",
"nameTranslations": {"de": "Einfache Formen", "ru": "Простые фигуры"},
"images": [
{ "name": "Circle", "nameTranslations": {"de": "Kreis", "ru": "Круг"}, "svg": "<svg xmlns=\"http://www.w3.org/2000/svg\" viewBox=\"0 0 100 100\"><style>.caption text{display:none}.caption .default{display:inline}:lang(de,ru) .default{display:none}:lang(de) .de,:lang(ru) .ru{display:inline}</style><rect width=\"100\" height=\"100\" rx=\"12\" fill=\"#fff4d6\"/><circle cx=\"50\" cy=\"42\" r=\"28\" fill=\"#e53935\"/><g class=\"caption\" text-anchor=\"middle\" font-family=\"sans-serif\" font-weight=\"600\" font-size=\"12\" fill=\"#222222\"><text class=\"default\" x=\"50\" y=\"91\">Circle</text><text class=\"de\" x=\"50\" y=\"91\">Kreis</text><text class=\"ru\" x=\"50\" y=\"91\">Круг</text></g></svg>" },
{ "name": "Triangle", "nameTranslations": {"de": "Dreieck", "ru": "Треугольник"}, "svg": "<svg xmlns=\"http://www.w3.org/2000/svg\" viewBox=\"0 0 100 100\"><style>.caption text{display:none}.caption .default{display:inline}:lang(de,ru) .default{display:none}:lang(de) .de,:lang(ru) .ru{display:inline}</style><rect width=\"100\" height=\"100\" rx=\"12\" fill=\"#e3f2fd\"/><path d=\"M50 12 L82 70 L18 70 Z\" fill=\"#1565c0\"/><g class=\"caption\" text-anchor=\"middle\" font-family=\"sans-serif\" font-weight=\"600\" font-size=\"12\" fill=\"#222222\"><text class=\"default\" x=\"50\" y=\"91\">Triangle</text><text class=\"de\" x=\"50\" y=\"91\">Dreieck</text><text class=\"ru\" x=\"50\" y=\"91\" font-size=\"10.5\">Треугольник</text></g></svg>" },
{ "name": "Question mark", "nameTranslations": {"de": "Fragezeichen", "ru": "Знак вопроса"}, "cover": true, "svg": "<svg xmlns=\"http://www.w3.org/2000/svg\" viewBox=\"0 0 100 100\"><style>.caption text{display:none}.caption .default{display:inline}:lang(ar,ur) .default{display:none}:lang(ar) .ar,:lang(ur) .ur{display:inline}</style><rect width=\"100\" height=\"100\" rx=\"12\" fill=\"#eeeeee\"/><g class=\"caption\" text-anchor=\"middle\" font-family=\"system-ui, -apple-system, sans-serif\" font-weight=\"bold\" fill=\"#555555\"><text class=\"default\" x=\"50.4\" y=\"72.4\" font-size=\"64\">?</text><text class=\"ar\" lang=\"ar\" x=\"49.6\" y=\"73.7\" font-size=\"58\">؟</text><text class=\"ur\" lang=\"ur\" x=\"50.5\" y=\"72.8\" font-size=\"62.9\">؟</text></g></svg>" }
]
}
```
目錄
簡短的指南,介紹你在 Intuition Check 中能做的主要事情,以及如何聯絡我們。
如果有功能無法正常運作
寫信到 [email protected],我們就會回覆你。最快的方式是透過「設定」→「關於」→「聯絡支援服務」:它會在你的郵件 App 中開啟一封草稿,App 版本和建置版本、你的裝置機型和 iOS 版本都已經填好。
我們沒有客服表單,也沒有工單系統。App 不會收集任何資料,所以我們需要知道的一切,都得由你告訴我們。
信中要寫些什麼
- 你做了什麼、你預期會發生什麼,以及實際發生了什麼。
- App 版本,位於「設定」→「關於」→「版本」。
- 你的裝置機型和 iOS 版本。
從「聯絡支援服務」建立的草稿,已經包含版本、機型和 iOS 版本。
疑難排解
- 兩台裝置找不到彼此:如果兩台裝置找不到彼此。
- 重新打開 App 後,統計資料不見了:保留你的統計。
- 統計裡什麼都沒有:會記錄哪些內容。
- 切換器中少了某個猜測集:猜測集切換器。
資料來源
- Kahneman, D., & Klein, G. (2009). American Psychologist, 64(6), 515–526. Conditions for intuitive expertise: A failure to disagree [直覺式專業能力的條件:未能成立的分歧]
兩位來自對立學派的頂尖直覺研究者合寫的回顧論文,刊登於美國心理學會的期刊。
https://doi.org/10.1037/a0016755 - Cardeña, E. (2018). American Psychologist, 73(5), 663–677. The experimental evidence for parapsychological phenomena: A review [超心理學現象的實驗證據:一篇回顧]
一位認為這些證據很有力的心理學家對許多研究所做的回顧,刊登於美國心理學會的期刊。
https://doi.org/10.1037/amp0000236 - Reber, A. S., & Alcock, J. E. (2020). American Psychologist, 75(3), 391–399. Searching for the impossible: Parapsychology's elusive quest [尋找不可能之事:超心理學難以捉摸的追尋]
兩位否定這類現象的心理學家對上述回顧的回應,刊登於同一份期刊。
https://doi.org/10.1037/amp0000486 - Sheldrake, R. (2000). Journal of the Society for Psychical Research, 64, 224–232. Telepathic telephone calls: Two surveys [心電感應電話:兩項調查]
對英格蘭倫敦和伯里隨機選出的住戶所做的電話調查,由一位認為心電感應存在的研究者進行,刊登於一份超心理學期刊。
https://www.sheldrake.org/files/pdfs/papers/Telepathic-Telephone-Calls-Two-Surveys.pdf - Brown, D. J., & Sheldrake, R. (2001). Journal of Parapsychology, 65, 145–156. The anticipation of telephone calls: A survey in California [對來電的預感:一項在加州進行的調查]
對 200 位隨機選出的民眾所做的電話調查,由同一位研究者與一位共同作者進行,刊登於一份超心理學期刊。
https://www.sheldrake.org/files/pdfs/papers/The-Anticipation-of-Telephone-Calls-A-Survey-in-California.pdf - Cottrell, J. E., Winer, G. A., & Smith, M. C. (1996). Developmental Psychology, 32(1), 50–61. Beliefs of children and adults about feeling stares of unseen others [兒童與成人對感覺到看不見之人注視的信念]
以兒童和成人為對象的三項研究,刊登於美國心理學會的一份期刊。
https://doi.org/10.1037/0012-1649.32.1.50 - Born, J., Hansen, K., Marshall, L., Mölle, M., & Fehm, H. L. (1999). Nature, 397, 29–30. Timing the end of nocturnal sleep [掌握夜間睡眠的結束時間]
一項有 15 位志願者參與的實驗,刊登於《Nature》期刊。
https://doi.org/10.1038/16166 - Sio, U. N., & Ormerod, T. C. (2009). Psychological Bulletin, 135(1), 94–120. Does incubation enhance problem solving? A meta-analytic review [醞釀能促進問題解決嗎?一項後設分析回顧]
一篇綜合許多實驗結果的回顧論文,刊登於美國心理學會的一份期刊。
https://doi.org/10.1037/a0014212 - Wagner, U., Gais, S., Haider, H., Verleger, R., & Born, J. (2004). Nature, 427, 352–355. Sleep inspires insight [睡眠激發頓悟]
刊登於《Nature》期刊的一項實驗;後來的重複實驗得出的結果不一。
https://doi.org/10.1038/nature02223 - Ambady, N., & Rosenthal, R. (1993). Journal of Personality and Social Psychology, 64(3), 431–441. Half a minute: Predicting teacher evaluations from thin slices of nonverbal behavior and physical attractiveness [半分鐘:從非語言行為與外表吸引力的短暫片段預測教師評鑑]
三項研究(主要的一項有 13 位教師參與),刊登於美國心理學會的一份期刊。
https://doi.org/10.1037/0022-3514.64.3.431 - Diaconis, P., & Mosteller, F. (1989). Journal of the American Statistical Association, 84(408), 853–861. Methods for studying coincidences [研究巧合的方法]
兩位統計學家探討巧合如何產生的論文,刊登於美國統計學會的期刊。
https://doi.org/10.1080/01621459.1989.10478847 - Wilson, T. D., Lisle, D. J., Schooler, J. W., Hodges, S. D., Klaaren, K. J., & LaFleur, S. J. (1993). Personality and Social Psychology Bulletin, 19(3), 331–339. Introspecting about reasons can reduce post-choice satisfaction [內省理由可能降低選擇後的滿意度]
一項實驗,刊登於一份社會心理學期刊。
https://doi.org/10.1177/0146167293193010 - Dunn, B. D., Galton, H. C., Morgan, R., Evans, D., Oliver, C., Meyer, M., Cusack, R., Lawrence, A. D., & Dalgleish, T. (2010). Psychological Science, 21(12), 1835–1844. Listening to your heart: How interoception shapes emotion experience and intuitive decision making [傾聽你的心:內感受如何塑造情緒經驗與直覺決策]
兩項實驗,刊登於心理科學協會的一份期刊。
https://doi.org/10.1177/0956797610389191
致謝
撲克牌插圖由 Adrian Kennard 創作,以 CC0 Public Domain 釋出。產生器和原始碼請見 me.uk/cards。