C
cheliknagite/nucifera
Design skill for Claude Code: a precise dark Linear-grade style with a light Dusk theme, Cyrillic-ready…
在 GitHub 查看 ↗链接已于 2026-11-12 核查 · HTTP 200 · 打开的是厂商自己的官网
- ★ 数取值
- 1 ★ · cheliknagite/nucifera · 取自 GitHub 搜索 API · (2026-11-13 20:00:50 核对)
- 来源明细
- 从该仓库的 GitHub 页面直接读取 · 条目类型:开源项目
- 收录与活跃
- 收录于 2026-10-24 · 最近见到 2026-11-14 · 共见到 25 次 · 被 1 个来源列出
- 评分构成
- 综合分 103 · 1 ★ · 1 个来源 · repo
常见问题(答案都来自我们的记录)
它适合谁 / 用来做什么?
我们把它归在这些标签下: Claude 技能。标签来自条目自身,不是我们强加的分类。
谁维护它、还在更新吗?
仓库
cheliknagite/nucifera;我们收录于 2026-10-24;最近见到 2026-11-14。这里没有"官方认证"或"质量评级"——我们只记录来源与时间。# nucifera
以下摘录自该仓库的 README(片段) · 在 GitHub 读完整 README →
A design skill for Claude Code. It makes Claude design interfaces in one precise style, in the line of Linear, Raycast and Reflect: a monochrome dark theme and a light "Dusk" theme with a violet accent, and it checks the rendered screens before handing them over.
> Named after Cocos nucifera, the coconut palm: a dark shell with a light inside, like the two themes. Status: 0.4.3, early. See "What it does not promise".
## What it does
Starts with a scene, not a template. Before any code Claude writes to .design/DESIGN.md: who looks at the screen and where, the direction, the accent, one signature element taken from the subject's own world (a paint-thickness map for a car inspection, an appointment book for a barbershop), what must be visible on the first screen, and a motion map: every change of state with its recipe.
Builds from a closed set of tokens and components. tokens.css defines both themes by role (surfaces, lines, text, accent, main action); kit.css has about fifteen components (rows, hero card, stat, chips, fields, key-value, states). No raw colours in screens.
Gives each screen a face. Before building, Claude names what makes the screen unlike any other product's and reads two reference cards for that screen type next to a "generic twin": how a default generator would build the same content. The cards describe real products (what they measure, what to take, what not to copy) as text only.
Moves with intent, in two tempos. Frequent things move at the speed of shipped products (menus in 240 ms); rare moments get a calm tempo. Ready recipes in kit.css and motion.js: presses that answer, menus that grow from their trigger, a sliding selection, sheets you can drag away, toasts, screen changes with direction, a waiting ladder that never flickers. Seven moments, at most one per screen: a photo that grows into its detail, the signature arriving once, a number that settles after an action, a success check, one pass of light over the main button, a landing's live product window, and on websites a window that pours out of the element you clicked and back into it, like the Mac genie. Prices and results never wait for an animation, and reduced motion keeps the meaning.
Reads without effort. Body text 16px, secondary text 14px in one grey, data as plain label-value lists instead of boxes and grids, a status shown only when it is the exception, drawings that need no legend.
Names the AI tells and what to do instead. Sixteen rules in the core and a dated list of 41 in the references: no coloured glows, no gradient buttons, no decorative dots, no small grey text in several shades, no data cut into boxes, no eyebrow labels on every heading, no washed-out photos, no airy screens where users came for data, and more. A vague "avoid the AI look" only swaps one default for another; named patterns with replacements hold.
Checks pixels with code. scripts/verify.mjs renders every mockup screen at 360, 390 and 430px in the dark theme and at 390px in the light one, and reports overflow, contrast, touch targets, fonts that did not load, small text, extra shades of grey, coloured glows, glass count, accent use and Cyrillic line-height, plus motion lint (transition: all, ease-in, endless loops). No npm packages: it uses your installed Chrome, Edge or Chromium.
> Named after Cocos nucifera, the coconut palm: a dark shell with a light inside, like the two themes. Status: 0.4.3, early. See "What it does not promise".
## What it does
Starts with a scene, not a template. Before any code Claude writes to .design/DESIGN.md: who looks at the screen and where, the direction, the accent, one signature element taken from the subject's own world (a paint-thickness map for a car inspection, an appointment book for a barbershop), what must be visible on the first screen, and a motion map: every change of state with its recipe.
Builds from a closed set of tokens and components. tokens.css defines both themes by role (surfaces, lines, text, accent, main action); kit.css has about fifteen components (rows, hero card, stat, chips, fields, key-value, states). No raw colours in screens.
Gives each screen a face. Before building, Claude names what makes the screen unlike any other product's and reads two reference cards for that screen type next to a "generic twin": how a default generator would build the same content. The cards describe real products (what they measure, what to take, what not to copy) as text only.
Moves with intent, in two tempos. Frequent things move at the speed of shipped products (menus in 240 ms); rare moments get a calm tempo. Ready recipes in kit.css and motion.js: presses that answer, menus that grow from their trigger, a sliding selection, sheets you can drag away, toasts, screen changes with direction, a waiting ladder that never flickers. Seven moments, at most one per screen: a photo that grows into its detail, the signature arriving once, a number that settles after an action, a success check, one pass of light over the main button, a landing's live product window, and on websites a window that pours out of the element you clicked and back into it, like the Mac genie. Prices and results never wait for an animation, and reduced motion keeps the meaning.
Reads without effort. Body text 16px, secondary text 14px in one grey, data as plain label-value lists instead of boxes and grids, a status shown only when it is the exception, drawings that need no legend.
Names the AI tells and what to do instead. Sixteen rules in the core and a dated list of 41 in the references: no coloured glows, no gradient buttons, no decorative dots, no small grey text in several shades, no data cut into boxes, no eyebrow labels on every heading, no washed-out photos, no airy screens where users came for data, and more. A vague "avoid the AI look" only swaps one default for another; named patterns with replacements hold.
Checks pixels with code. scripts/verify.mjs renders every mockup screen at 360, 390 and 430px in the dark theme and at 390px in the light one, and reports overflow, contrast, touch targets, fonts that did not load, small text, extra shades of grey, coloured glows, glass count, accent use and Cyrillic line-height, plus motion lint (transition: all, ease-in, endless loops). No npm packages: it uses your installed Chrome, Edge or Chromium.
收录徽章(可选)
想把收录标记放进 README 就复制这行,可选,不影响收录。
[](https://anclum.com/zh/s/cheliknagite-nucifera/)
- 来源
- github · https://github.com/cheliknagite/nucifera
- 按领域浏览
- Claude 技能
- Traction
- 1 ★
- 收录于
- 今天
同类推荐
所属领域与标签
每个标签都能点进去看同类的全部条目。数字是当前库里的真实条数。