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 会自动为这个回合计分。参见会记录哪些内容。
快速点选
猜测集的所有值都排列在一个网格里。每次点按都是一个单独的回合。在主动直觉模式下,值在你点按的那一刻随机抽出;在被动直觉模式下,值会提前抽出,就在你上一次点按之后。命中时可以用绿色闪光和振动来标示。
值超过 1000 个的数字猜测集没有网格:可以在这个猜测集的设置中缩小范围,或者用“逐个”玩法来玩。
连续系列
在主动直觉模式下,选一个你想要的值,用意念想定它,然后点按它:App 会随机抽出一个连续系列的值,并数出其中有多少个与你点按的值相符。一个连续系列可以抽取 2 到 12 次,也可以是 100、1000、1 万、10 万、100 万或 1000 万次。长度在主界面上设置。在“设置”→“连续系列”中,“系列时长”滑块可以把各次抽取分散在最多 10 秒内;设为 0 时,抽取之间没有间隔。每个连续系列在统计中记为一条记录。
选择“连续系列”会把模式切换为主动直觉。
扑克牌和数字
扑克牌猜测集使用一副 36 张或 52 张的牌,可以带大小王,也可以不带。数字猜测集使用最多 9 位的数字——最大位数由你来选。两者都在这个猜测集的设置界面中更改:在主界面上,点按猜测集切换器旁边的齿轮。
简洁视图
在主界面的任意位置长按,可以隐藏切换器、工具栏、状态选择栏和提示。再长按一次,它们就会回来。回合数和结果保持显示。
在“设置”→“外观与反馈”的“简洁视图”下,“显示按钮”会在工具栏中加入眼睛按钮(点按它即可开启简洁视图),“记住简洁视图”会让简洁视图在 App 重新启动后保持开启。
回合数
主界面可以显示你玩了多少个回合,以及你的表现:模式和玩法的每种组合各有一个回合数和一个结果,还有一个按钮可以重置回合数并清除结果。切换到另一个猜测集也会重置所有的回合数和结果。
要让回合数和结果在 App 重新启动后仍然保留,请在“设置”→“统计”中打开“保存回合数和结果”。这个选项在“在设备上保存统计数据”打开时可用。
猜测集
猜测集就是你从中猜测的那一组值:扑克牌、数字或一组图像。一开始,主界面只显示“数字”和“扑克牌”。点按主界面上猜测集切换器旁边的 ,就可以添加 App 自带的其他猜测集。
猜测集切换器
主界面顶部的切换器会显示你的猜测集。使用默认的“切换器样式”时,如果切换器要显示的猜测集有一个或两个,它会显示按钮;从三个起则显示当前猜测集的名称,由它打开猜测集列表。在“切换器样式”中选择“独立界面”时,切换器总是打开这个列表。
每个猜测集都有自己的“使用”开关。关闭这个开关的猜测集在任何地方都不会出现——不在主界面的猜测集切换器里,不在搭档游戏里,也不在统计里——但它会留在“设置”→“猜测集”→“管理猜测集”中你的猜测集列表里;重新打开这个开关,它的统计也会随之回来。
猜测集切换器旁边的 按钮会打开“添加猜测集”界面。其中列出了 App 自带的其他猜测集,可以直接添加到主界面;它们下方有一个用来创建空猜测集的按钮(之后你可以往里面添加自己的图像),还有“你的 AI 助手”区块,用来添加 AI 助手制作的猜测集。猜测集切换器旁边的齿轮按钮会打开当前所选猜测集的设置。在“设置”→“猜测集”中,可以用“显示添加猜测集按钮”和“显示猜测集设置按钮”把这两个按钮隐藏起来。
现成套组
点按主界面上猜测集切换器旁边的 ——或者打开“设置”→“猜测集”→“管理猜测集”,点按 并选择“现成套组”。打开一个套组,然后点按“添加到我的猜测集”。
你添加的猜测集是你自己的副本:你可以给它重新命名、调整图像的顺序、让其中一些图像不参与游戏、和搭档一起玩它,或者把它发给别人。
用你自己的图像制作猜测集
在主界面上:点按切换器旁边的 ,然后点按现成套组下方的“空的图像集”。保留名称“我的图像”,或者输入另一个名称,然后点按“创建”。App 会切换到这个新的猜测集并打开它。
或者打开“设置”→“猜测集”→“管理猜测集”,点按 并选择“空的图像集”,然后给猜测集命名,再点按“创建”。新的猜测集会随之打开。
在猜测集里点按 ,从“照片”或“文件”中添加图像——一次可以添加多张——或者用“相机”一张一张地拍,也可以用“从剪贴板粘贴”粘贴拷贝的图像或 SVG。
图像名称
在猜测集本身的界面中点按一张图像,即可放大查看。它的“名称”就是下方的字段:可以输入、修改或清除。从“文件”添加的图像,名称一开始是文件名(不含扩展名);从“照片”或“相机”添加的图像,以及用“从剪贴板粘贴”添加的图像,一开始都没有名称。在有多种语言名称的猜测集中,字段下方的“各语言的名称”保存这张图像在每种语言中的名称。图像下方显示 App 所保存文件的格式和大小。
AI 助手可以为你制作图像,也可以制作整个猜测集:用 AI 制作你自己的猜测集。
顺序、布局以及哪些图像参与游戏
在猜测集自己的界面中,“排列”可以让你拖动图像来排出新的顺序,并为网格选择“每行图像数”、“对齐”和“完整显示”。
长按一张图像,可以看到更多选项:
- “不在游戏中使用”会把这张图像留在猜测集里,但它从不会被抽中。“在游戏中使用”会让它重新参与游戏。
- 选择标记为“?”占位图后,在“逐个”玩法中,值还隐藏着的时候就会显示这张图像。它本身从不会被抽中。每个猜测集只能有一张“?”占位图。
重新命名与删除
名称是猜测集界面中的第一个文本栏。对于现成套组,在这里修改的是 App 当前语言下的名称;其他语言的名称在“各语言的名称”中。
要删除一个猜测集,可以在“设置”→“猜测集”→“管理猜测集”中你的猜测集列表里轻扫它,或者长按它,然后选择“删除”。App 会先询问你。这个猜测集的统计数据会随它一起删除。
发送猜测集
发送一个猜测集
用你自己的图像制作的猜测集,可以作为一个扩展名为 .guesset 的文件来传送。这个文件包含图像、图像的顺序、布局和猜测集的名称,以及哪些图像参与游戏、哪一张是“?”占位图。“扑克牌”和“数字”是 App 内置的,无法发送。
- 打开“设置”→“猜测集”→“管理猜测集”。
- 长按这个猜测集,然后选择“导出…”。猜测集里的共享按钮也有同样的作用。
- 选择发送方式:邮件、信息、隔空投送、“文件”或其他 App。
要和附近的人一起玩某个猜测集,并不需要文件:参见用你自己的图像来玩。
打开别人发给你的猜测集
在邮件、信息或“文件”中点按一个 .guesset 文件,或者接受通过隔空投送发来的这种文件,然后用 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 关闭后它们就会消失。此操作无法撤销。
清除
统计界面的底部有:
- 清除“…”的全部统计——筛选条件中所选猜测集记录的全部统计。
- 删除筛选后的 … 条统计记录——仅限筛选条件所显示的记录。
- 清除全部统计——全部内容。
App 会请你确认其中每一项删除,而且任何一项都无法撤销。
导出
点按统计界面工具栏中的共享按钮,然后点按“将统计导出为文本文件”。这个文件是一张表格 (CSV),包含的正是你的筛选条件所显示的那些记录:每个回合一行;在“连续系列”玩法中,则是每个连续系列一行。Numbers 表格等电子表格 App 可以打开它。你或许也会觉得,把这个文件给你使用的 AI 助手看,然后问它一些问题会很有用,例如:“我的直觉在什么情况下似乎发挥得更好,在什么情况下更差?”
结果的解读方式
统计不只是计算命中次数。它会把你的结果与随机猜测在可能值数量相同时会得到的结果相比较,并用通俗的话告诉你:你是高于随机、低于随机,还是在随机范围之内。
你的结果与随机
在“猜对的次数”下面,“你的结果”显示在“随机可得”旁边。同样的 30% 可能意味着相反的事情:如果有 3 个可能的值,随机猜测大约能得到 33%,所以 30% 略低于随机水平;如果是一副 52 张的牌,随机猜测大约能得到 2%,所以 30% 远高于随机水平。随机概率按每个回合各自的可能值数量计算。
判定
App 会给出判定:从“与随机水平相当”,经过略高于或略低于随机水平、明显高于或明显低于随机水平,一直到“远高于随机水平”或“远低于随机水平”。它还会说明,对随机猜测来说,这样的结果有多罕见,例如“大约每 300 次才会出现一次”。
回合数少的时候,单凭随机,结果就会大幅波动。所以每多一个回合,判定就会更稳定一些。
被动直觉与主动直觉对比
当你在两种模式下都有回合时,“被动直觉与主动直觉的对比”会显示每种模式的命中次数和命中率,让你看出哪一种更适合你。“连续系列”玩法不显示这一项。
最长连续命中
“最长连续命中”会列出你连续猜对次数最多的几次,并附上日期和时间,以及你当时记录的状态。间隔超过“回合之间的最长间隔”(你可以在这个区块中设置它)会中断连续命中;你记录的状态发生变化,也会中断连续命中。
随时间的变化
当你在两个不同的日子都有回合之后,“命中率随时间的变化”会画出你每天的命中率。“按时段”会分别显示上午、下午、晚上和夜间。
值
当统计只显示单个猜测集的数据,并且这个猜测集最多有 100 个值时,统计会列出你最常猜对的值,以及你最常和最少选作猜测的值——一旦你的猜测次数达到这个猜测集中值的数量,其中还会包括你从未选过的值。
人们常常会偏向某些值、回避另一些值,而且有些值可能比其他值更常被猜对。
结果可能会变化
你的结果可能会随状态和所处的情况而变化。下面这些都不是定论——它们是你在玩的时候值得留意的可能性:
- 你的状态。刚醒来时或深夜、精力充沛或疲倦时、平静或紧张时,你的表现可能会不一样。玩的时候记录你的状态,统计就会按状态和按时段对比你的回合。
- 自信。感到自信,或者充满怀疑,可能与你的得分情况相吻合。
- 低于随机也算数。猜对的次数明显少于随机所预测的,这同样是对随机的偏离。一种解读是:那一刻直觉在和你作对,而不是什么都没有发生。
- 值。你猜对某些值的次数可能远多于其他值,有些值你可能一次也猜不对,即使你选它们的次数和选其他值一样多。
数字能说明什么
App 能告诉你,你的结果是否偏离了纯粹的随机——但永远无法告诉你原因,即使从数据来看原因似乎显而易见。请把这些数字当作值得探索的东西,而不是衡量你自己的固定标准。另见直觉。
你的状态
状态选择栏
主界面上的状态选择栏可以让你记录自己此刻的状态:“精力充沛”或“疲倦”、“平静”或“紧张”、“有把握”或“没把握”、“专注”或“涣散”、心情,以及所处的情况,比如“刚起床”、“喝咖啡后”或“运动后”。你记录的内容会随你从那时起玩的每个回合一起记下,直到你更改它,或者 App 把它忘掉为止。
这样,统计就会按状态和按时段对比你的回合,每个连续命中也会显示你当时记录的状态。详见结果可能会变化。
什么时候会被忘掉
由“设置”→“你的状态”中的“重置记录的状态”决定:
- “App 启动时”——默认选项。下次启动时,不会有任何已记录的状态。
- “暂停之后”——如果你没有玩的时间超过了选定的“暂停时长”(15 分钟到 1 天),它就会被忘掉。
- “永不”——一直保留,直到你更改它。
你自己的状态
在“设置”→“你的状态”→“管理状态”中,你可以重新命名、重新排序、添加和隐藏状态,添加你自己的维度,还可以用某个维度自己的“使用”开关把它关闭:关闭的维度会离开状态选择栏,新的回合不会记录它,统计中也不再包含它。
要完全去掉状态选择栏,请关闭“记录回合中的状态”;这样就完全不会记录任何状态。
在简洁视图中,状态选择栏会被隐藏;在“逐个”玩法中关闭了猜测记录时,状态选择栏也会被隐藏。
外观与功能
主题
“设置”→“外观与反馈”中有四种主题——“沙色”、“海洋”、“森林”和“黄昏”——每种都有浅色和深色版本。“外观”可以选择“浅色”、“深色”或“系统”;选择“系统”时,App 会跟随设备的设置,并随之切换。主题还会为扑克牌和大多数现成图像着色。
反馈
在“命中反馈”下,“振动”和“动画”会用一次振动和一下绿色闪光来提示猜对;其中任何一个都可以关闭。它们适用于“快速点选”玩法中的每次点按、“连续系列”玩法中一个系列的每次抽取都命中时,以及“逐个”玩法中在显示之前输入猜测时。没猜中时既不会振动,也不会闪光。振动还需要打开“系统触感反馈”,它位于“设置”App 的“声效与触感反馈”中。
“点按时的脉动动画”会让你在“快速点选”和“连续系列”玩法中点按的格子短暂地脉动一下;在“逐个”玩法中,如果你自行判定回合或不记录回合,你显示出的值也会脉动一下。
更清爽的主界面
主界面上几乎所有内容都可以隐藏。每个开关都位于它所属的设置界面中:
- “设置”→“玩法与模式”:两个“显示切换器”开关,一个用于玩法,一个用于模式。
- “设置”→“猜测集”:“显示切换器”、“显示添加猜测集按钮”、“显示猜测集设置按钮”。
- “设置”→“快速点选”:“显示网格选项按钮”。
- “设置”→“逐个”:“显示提示”。
- “设置”→“连续系列”:“在主界面显示系列长度”、“在主界面显示系列时长”、“显示网格选项按钮”(与“设置”→“快速点选”中的是同一个开关)。
- “设置”→“你的状态”:“记录回合中的状态”。
- “设置”→“统计”:“显示统计按钮”。
- “设置”→“搭档游戏”:“显示搭档游戏按钮”。
- 每种玩法的设置(“快速点选”、“逐个”、“连续系列”):“显示回合数”、“显示结果开关”、“显示结果”。
要把某个猜测集从切换器中去掉,请在这个猜测集的设置中关闭“使用”;这样它也会从搭档游戏和统计中消失。打开简洁视图,可以一次性隐藏主界面上的大部分元素。
功能
“设置”→“功能”中有一个“连续系列玩法”开关,以及一个“主界面上的回合数与结果”开关。关闭后,相应的功能会从主界面和“设置”中消失。
语言
“设置”→“语言”可以让你独立于设备的语言来设置 App 的语言,它还决定数字和日期的书写方式。在“建议语言”下,列表先显示系统语言,然后按设备上设定的顺序显示设备语言中 App 提供的每一种;其余所有语言随后列在“其他语言”下。如果新语言的阅读方向与之前相反,请在切换后关闭 App 再重新打开(书写方向只有在重新启动后才会正确切换)。
在“设置”中,“语言”一行的下方是“在设置中显示提示”开关;它用于显示或隐藏各项设置下方的说明。
免费的 1 小时与订阅
免费的 1 小时
App 可以免费下载,并包含 1 小时的 App 内使用时长,让你试用其中的一切。这 1 小时只在 App 打开并显示在屏幕上时计时,你每一次的使用时间都会累计在一起——App 关闭或在后台时不会计时。
这 1 小时用完后,订阅界面会自动打开。如果这些时间还不够你决定是否订阅,你可以再多用一些:“重置免费的 1 小时”可以再给你 1 小时,最多 3 次——总共 4 小时的免费时长。
订阅
在那之后,要继续使用 App,可以订阅;订阅有两种方案:“每月”和“每年”。订阅支持家人共享。
开始订阅
打开“设置”→“订阅”→“立即订阅”。
管理或取消
订阅由 Apple 收费。“设置”→“订阅”→“管理订阅”会带你前往你的订阅。你也可以用标准方式管理这个 App 的订阅:在设备的设置中,通过你的 Apple 账户的订阅来管理。取消订阅会停止以后的自动续订,但在当前订阅期结束之前,你仍然可以使用。
按月订阅的用户可以通过“设置”→“订阅”→“改用年度方案”转为年度方案。
退款
退款由 Apple 处理:请前往 reportaproblem.apple.com 申请退款。我们无法访问你的付款信息,也无法自行办理退款——不过如果出了问题,也请写信告诉我们,因为这是我们了解到问题的唯一途径。
恢复购买
在新设备上,打开“设置”→“订阅”→“立即订阅”,然后点按“恢复购买”。这也能找回家庭成员与你共享的订阅。请使用当初订阅时所用的 Apple 账户,或同一家人共享群组中的某个 Apple 账户。
你的数据
简而言之
没有账户,也没有服务器。App 不会把你的数据发送给我们,也不会发送给任何其他公司。搭档游戏只与另一台设备交换数据——在两台设备共同连接的 Wi‑Fi 网络上,或在两者彼此靠近时在设备之间。
数据存放在哪里
你的设置、猜测集(包括你添加的图像)以及状态列表,都存储在你的设备上,存放在 App 自己的存储空间里。在你打开“在设备上保存统计数据”之前,统计数据只在 App 运行期间留在内存中。
和其他任何 App 的数据一样,这些内容都会包含在设备的备份中。
App 不含数据分析,也不含崩溃报告。
当你写信给我们时
你发给我们的电子邮件属于普通的往来通信:我们只在回复你所需的时间内保留它。
完整细节见隐私政策。
用 AI 制作你自己的猜测集
你可以请 AI 助手(例如聊天机器人)为猜测集绘制图像,或者制作整个猜测集。这些图像是 SVG 图画。SVG 图像中的文字可以有多种语言,App 会用 App 所设置的语言显示这些文字。图像还可以采用 App 主题的颜色——无论是主题的浅色版本还是深色版本。猜测集可以有自己的“?”占位图:值隐藏时显示的图像。助手需要格式说明;下面的每个请求都包含这份说明的地址。
制作猜测集
- 把下面的一个请求拷贝到助手的对话中,并按你的需要修改:题材、图像数量(2 到 200 张)、语言。
- 如果助手无法打开网页,还要把格式说明也交给它:在面向 AI 的格式说明部分中点按“拷贝”,然后把说明粘贴到同一个对话中;或者点按“保存”,然后附上保存的文件。
- 助手会把猜测集放在一个代码块中回复,前后常常附有几句说明。只拷贝代码块:在许多聊天 App 中,代码块有自己的拷贝按钮。
- 在 App 中,点按主界面上的 ,然后在“添加猜测集”界面中点按“从剪贴板粘贴”。如果助手在另一台设备(例如 Mac)上运行,就在那台设备上把代码块保存为名称以 .json 结尾的文件,然后改为点按“从文件导入”。新的猜测集会被添加并选中;点按“开始猜测”即可前往主界面。这些步骤的正下方也有同样的按钮。
如果出现错误,请让助手修正。
不带图注的猜测集:
为 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制作单张图像
助手也可以只制作一张图像。拷贝它的代码块,打开你自己的一个图像集,点按 ,再点按“从剪贴板粘贴”。图像添加后没有名称:点按它,在“名称”中输入名称。你也可以把代码块保存为名称以 .svg 结尾的文件,然后在猜测集中点按 并选择“文件”;文件名去掉 .svg 后就成为图像的名称。
为 Intuition Check 这个 App 绘制一张猫的 SVG 图像。请先阅读格式说明并遵循它:https://intuition-check.com/llm-formats.txt猜测集还可以有什么
请助手解释格式允许做哪些事,并为每一种可能各给一个请求示例:
请阅读 Intuition Check 这个 App 的格式说明:https://intuition-check.com/llm-formats.txt
用简短、浅显的话告诉我,在猜测集和图像中可以做些什么:图像如何跟随 App 的主题——不同的主题,浅色和深色版本;猜测集及其图像的名称如何加上其他语言的翻译;图像可以有哪几种图注;猜测集的“?”占位图(它的背面)可以显示什么。对每一种可能,给出一个我可以发给你的请求示例。先不要绘制任何东西。面向 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。