ark-ui
"Design, build, or refine evidence-based Hypergryph-inspired interfaces. Covers Arknights, Endfield, Ex Astris, POPUCOM, studio UI, and 12 named Terra factions including Rhine Lab, Lungmen, Laterano, and Penguin Logistics. Choose the identity, actual user task, and one of four independent depth levels. Use for dashboards, game menus, dossiers, route tools, component systems, and visual QA."
Safety scan
A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.
Badge for your README
Markdown
[](/listings/brandon030722--ark-ui-skill)HTML
<a href="/listings/brandon030722--ark-ui-skill"><img src="/api/listings/brandon030722--ark-ui-skill/badge.svg" alt="findsafeskills safety rating" /></a>Install
Install instructions from the README
As written by the repo's author. findsafeskills has not verified these steps.
使用 Git 克隆到 Codex 技能目录:
git clone https://github.com/Brandon030722/ark-ui-skill.git "$CODEX_HOME/skills/ark-ui"
已经存在旧版本时,先备份自己的改动,再在该目录执行 `git pull`。安装后可直接在任务中写 `$ark-ui` 调用。
指定阵营时,`$ark-ui` 会从仓库里的 [Terra 子包](packs/terra-faction-ui/SKILL.md)读取对应的配方、布局和控件。现有的 `$terra-faction-ui` 调用者可以从此仓库取同名子包独立安装。旧 Terra 仓库保留此前的版本与历史。
What was scanned
The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.
SKILL.md · Manifest · 185 lines
- ---
- name: ark-ui
- description: "Design, build, or refine evidence-based Hypergryph-inspired interfaces. Covers Arknights, Endfield, Ex Astris, POPUCOM, studio UI, and 12 named Terra factions including Rhine Lab, Lungmen, Laterano, and Penguin Logistics. Choose the identity, actual user task, and one of four independent depth levels. Use for dashboards, game menus, dossiers, route tools, component systems, and visual QA."
- ---
- # Ark UI
- Build original interfaces from documented visual and implementation evidence, not from vague “cyberpunk” prompting. Preserve usability, accessibility, project conventions, and the user's product identity.
- ## Choose the visual owner
- - **Named Terra faction or institution:** route through the [Terra workflow](packs/terra-faction-ui/SKILL.md) and [faction index](packs/terra-faction-ui/references/faction-index.md). The faction owns the palette, spatial layout, control mechanics, motion, and evidence confidence. Use its references and starter in place of the product-family defaults below.
- - **Named product or studio, or broad Arknights UI:** use the product-family workflow below.
- - **Mixed brief:** choose the owner of the primary task. Borrow at most one explicitly named trait from a secondary identity.
- For design and refinement in either branch, apply [task-first refinement](references/interface-refinement.md). Match structure, typography, and surface behavior to the selected identity and test the result through its real controls.
- ## Start here
- 1. Inspect the target project, framework, viewport, existing tokens, and user content.
- 2. Choose one family; do not average every product into one style:
- - `ark`: black/white/cyan industrial information system.
- - `endfield`: white/charcoal/signal-yellow technical field system.
- - `exa`: midnight/white/aqua cosmic-archival system with serif contrast.
- - `popucom`: blue/yellow/orange playful platform system.
- - `corporate`: black/white/acid-lime restrained studio identity.
- 3. Choose one application depth independently from the family:
- - `1 / minimal / 极简`: family identity through tokens, type, geometry, and one strong state cue.
- - `2 / moderate / 中等`: family shell plus one controlled texture/instrument layer and restrained reveal motion.
- - `3 / complex / 复杂`: multi-zone shell, layered stage, broad component coverage, and coordinated instrumentation. Use the anonymized system-wide reference in `references/depth-levels.md` as the calibration baseline.
- - `4 / maximal / 极繁`: bespoke section compositions, state-driven instrumentation, and coordinated motion across a fully re-art-directed responsive system.
- 4. If the user specifies a depth, preserve it. Otherwise default to `moderate` for productivity/product UI and `complex` for game-adjacent or showcase UI; state the assumption. Ask only when the depth would materially change scope or rework.
- 5. Read [references/design-language.md](references/design-language.md), [references/depth-levels.md](references/depth-levels.md), and only the chosen family in [references/recipes.md](references/recipes.md). For multi-family comparisons or family-specific depth behavior, also read [references/family-depth-matrix.md](references/family-depth-matrix.md).
- 6. For implementation or code review, also read [references/frontend-evidence.md](references/frontend-evidence.md).
- 7. For source attribution, provenance, or asset decisions, read [references/source-ledger.md](references/source-ledger.md) and [references/legal.md](references/legal.md).
- ## Lock the design contract
- Before changing code, state a compact contract: `family`, `depth`, evidence pattern, and what the primary screen must let the user do. Treat family and depth as orthogonal axes: `endfield + minimal` and `endfield + maximal` share identity but not visual saturation.
- When the user asks to choose, present the four numbered levels with one recommended level based on product type. Keep family selection and depth selection as separate decisions instead of showing a large cross-product matrix.
- Depth measures implementation coverage and orchestration, not content density. Increasing depth may add meaningful layers, responsive recomposition, and state-aware motion; it never permits fake telemetry, duplicate copy, extra colors, smaller essential text, or weaker accessibility. Read the full rubric in [references/depth-levels.md](references/depth-levels.md) before implementation.
- ## Implement
- - Start from semantic content and task hierarchy. Use the visual grammar to expose state, navigation, and priority.
- - Reuse project components and tokens when present. Otherwise copy `assets/starter-vanilla/` or use `assets/react/ArkUI.jsx` with `assets/react/ark-ui.css`.
- - When renaming starter classes, IDs, data attributes, or ARIA targets, update every JavaScript selector and reference in the same pass. A styled page with broken DOM wiring is not complete.
- - Use `assets/tokens/ark-ui.tokens.json` as a reference, then rename tokens to match the target project.
- - Represent the contract with root attributes when practical: `data-ark-theme="endfield"` and `data-ark-depth="complex"`. Keep component selectors semantic so either axis can change independently.
- - Prefer CSS/SVG geometry, gradients, rules, masks, and original abstractions over copied game art.
- - Keep one dominant accent. Treat secondary accents as state or product-family signals.
- - Pair Chinese or primary labels with short uppercase English micro-labels only when it clarifies hierarchy.
- - Use square or very small-radius geometry, 1px rules, cropped edges, strong negative space, and intentional asymmetry.
- - Use motion to reveal hierarchy: masked slide, clipped wipe, restrained pulse, or directional drift. Honor `prefers-reduced-motion`.
- - Build responsive layouts deliberately. Convert side rails to compact top/bottom navigation on portrait screens; do not merely scale the desktop composition.
- - Preserve keyboard access, visible focus, readable contrast, semantic controls, and meaningful alt text.
- ## Iterate with an evidence lock
- Use this loop when the user asks for repeated refinement or says the interface
- is ugly, too dark, or too text-heavy:
- 1. Name the primary family, application depth, and exact public pattern from the source ledger
- before changing code. If a second family is useful, borrow one constrained
- trait only; do not merge its full palette or decoration system.
- 2. Inventory persistent copy as `decision`, `changing state`, or `explanation`.
- Keep decision data visible, compress repeated state, and move optional
- explanation behind an explicit, accessible details affordance.
- Assign every persistent datum one visual owner: comparable values belong to
- candidate cards, while a focus dossier owns only additional context. Do not
- repeat the same metric in both places.
- A dedicated rules, archive, or reference view is already the explicit detail
- layer: optimize it for scanning and grouping, but do not delete necessary
- rules merely to match the density of a persistent HUD. Remove a summary that
- only enumerates the visible sections beneath it; it is duplicate navigation,
- not rule content. For an unambiguous procedural gesture, prefer a compact
- symbolic mapping such as `hand → rear → front`, but keep every exact value,
- prerequisite, stop condition, and exception in visible text.
- Copy reduction must not collapse decision UI into unlabeled icons. Keep
- comparable numbers and explicit action verbs. In a 36–42 px status chip,
- prefer one readable `label + value` line over two undersized text tiers.
- Put immediate-resolution copy in one owner (usually the decision header or
- commit action), not the header, explainer, and footer at the same time.
- A transient phase, toast, or transition banner owns only its subject/state
- and one immediate action or outcome. Persistent HUD values remain with the
- HUD. Do not manufacture protocol names, system codes, channel labels, load
- meters, or decorative telemetry merely to make the banner feel technical.
- On transition and result screens, let the status dossier own current values
- and let the report own narrative outcome plus the next unlock. Never mirror
- the dossier's telemetry in the report merely to fill the available space.
- On route or topology screens, let the graph own choices, the top HUD own
- comparable run values, and the bottom rail own only the selected summary and
- explicit actions. Put full mechanics in a pre-commit detail layer instead of
- repeating them persistently. Stretch the graph between header and footer on
- short, wide viewports; do not solve collisions by shrinking essential text.
- A pre-commit detail layer must still partition ownership: one run-state
- dossier, then distinct target, mechanic, risk, and outcome facets. Do not add
- a general “run check” card that repeats the dossier. Keep facet labels visible
- so copy reduction does not turn the screen into unexplained icons.
- 3. Change one shared token family, one depth behavior, and one representative screen per pass.
- When pure black feels flat, first lift neutral tokens or stage lighting within
- the chosen evidence family; do not invent gradients, glow, or a new accent.
- For a modal shade, try the next existing neutral surface token at restrained
- opacity before altering the panel or adding a color. The shade should separate
- layers without turning the full viewport into a flat black field.
- If an illustrated backdrop is too saturated, restrain it with the same
- evidence-locked neutral wash rather than replacing it with flat black or a
- large accent-colored field.
- 4. Preserve the recovered space. Give it to primary content or negative space
- instead of filling it with decorative telemetry.
- 5. Capture before and after at the same viewport. Revert or revise if the result
- is not visibly closer to the cited evidence, reduces legibility, introduces
- collisions, or makes a truthful mechanic harder to find.
- 6. Repeat only after compile, interaction, contrast, and screenshot checks pass.
- For choices that commit immediately, preserve that consequence in one short
- state line or action label even when longer instructional prose is removed.
- If a representative state is difficult to reach, add a deterministic,
- non-persistent QA entry before judging screenshots. Non-persistent means the
- harness explicitly suppresses save writes and save deletion, not only that it
- creates an in-memory object. If coordinate automation is unreliable, expose
- the exact modal or confirmation state through that QA entry rather than
- waiving interaction evidence. For an auto-hiding transition, the QA entry
- may restart the normal animation with auto-hide disabled; it must not change
- production timing. Capture and validate while the transient UI is visible.
- Never optimize from a guessed or stale state.
- ## Avoid
- - Do not copy Hypergryph, Arknights, Endfield, Rhodes Island, Monster Siren, or other protected logos, character art, key art, UI screenshots, or CDN assets into deliverables unless the user has rights and explicitly supplies them.
- - Do not redistribute production bundles or the proprietary/unclear-license fonts observed on official sites.
- - Do not claim reconstructed code is Hypergryph source code.
- - Do not add random hexagons, terminal noise, scanlines, glitch, neon gradients, or dense HUD decoration without an information role.
- - Do not combine cyan, signal yellow, aqua, magenta, orange, and lime in one interface merely because they occur across different products.
- - Do not hide primary content behind splash screens, autoplay audio, or inaccessible hover-only controls.
- - Do not interpret `maximal` as permission for random HUD noise, fake system codes, perpetual motion, or decoration on every component.
- - Do not achieve `minimal` by deleting labels, states, focus cues, prerequisites, or necessary explanations.
- ## Validate
- 1. Run the target project's tests, lint, and build.
- 2. Run the bundled heuristic audit:
- ```bash
- node "$CODEX_HOME/skills/ark-ui/scripts/audit-ark-ui.mjs" <html-or-css-path>
- ```
- 3. Render at desktop and portrait widths. Inspect clipping, text collisions, focus order, active state, and reduced-motion behavior.
- 4. Exercise the primary controls in a browser and check for runtime errors; do not infer behavior from static markup alone.
- 5. Confirm every decorative element either supports grouping, direction, state, or world-building.
- 6. Confirm provenance: official production evidence is cited, third-party code is license-checked, and output code is original or properly attributed.
- 7. For text-density passes, confirm that removed copy is redundant or remains
- available through a visible, keyboard-accessible details control.
- 8. Confirm every icon-only control is a familiar secondary action or has an
- accessible name. Purchase, commit, destructive, and state-comparison actions
- retain visible verbs and values even in compact layouts.
- 9. Compare the representative screen against the selected depth in [references/depth-levels.md](references/depth-levels.md). Judge shell transformation, stage layers, component coverage, state instrumentation, motion, and responsive recomposition—not raw element count.
- 10. Confirm the densest screen does not exceed the selected depth by more than one local level, and the primary screen is not below it. Document intentional local exceptions.
- ## Research new official pages
- When the task requires freshness or a product not covered in the ledger, inspect the public page and its loaded CSS/JS. Use the analyzer on a URL or downloaded CSS:
- ```bash
- python3 "$CODEX_HOME/skills/ark-ui/scripts/analyze-css-evidence.py" <css-url-or-file>
- ```
- Record the page URL, asset URL, retrieval date, observed framework, colors, fonts, and reusable pattern in `references/source-ledger.md`. Separate direct observations from inference.
- ## Bundled code
- - `assets/starter-vanilla/`: dependency-free responsive demo and starting point.
- - `assets/react/`: portable React shell, panels, theme switcher, and CSS.
- - `assets/tokens/ark-ui.tokens.json`: five evidence-derived theme families using safe fallback font stacks.
- - `assets/showcases/`: five original, inspectable complex-level UI samples with four-level depth controls.
- - `assets/promo/`: editable promotional compositions and eight generated landscape/portrait PNGs.
- - `references/depth-levels.md`: four-level application-depth rubric, selection rules, complex-level calibration, and validation scorecard.
- - `references/family-depth-matrix.md`: family-specific shell, content, instrumentation, and depth adaptation rules.
- - Starter and React assets expose `data-ark-depth` / `depth` alongside the existing family selector.
- - `scripts/scaffold-ark-ui.py`: copy a starter into a new or empty destination.
- - `scripts/audit-ark-ui.mjs`: flag missing accessibility/responsiveness and common imitation clichés.
- - `scripts/analyze-css-evidence.py`: extract color, font, motion, and geometry evidence from public CSS.
- - `scripts/capture-showcases.mjs`: render the five samples at exact desktop and optional mobile CDP viewports, then fail on horizontal overflow.
- - `scripts/capture-promos.mjs`: regenerate the social promotion set from the original showcase screenshots.
README.md · README · 139 lines
- # Ark UI
- Ark UI 将四个产品风格、一个工作室风格和十二套泰拉阵营界面整合进同一仓库。使用时独立选择视觉归属和应用深度。
- 1. **视觉归属**:`ark`、`endfield`、`exa`、`popucom`、`corporate`,或[泰拉十二阵营](packs/terra-faction-ui/references/faction-index.md)。
- 2. **应用深度**:`minimal`、`moderate`、`complex`、`maximal`。
- 本项目不是相关游戏或厂商的官方项目,不包含受保护的标志、角色立绘、宣传图或生产环境代码。风格族只用于描述从公开页面归纳出的构图、色彩、排版、几何和动效规律。
- 
- 上图是这套技能的设计契约:先选择一个风格族,再独立选择实施深度。深度衡量的是壳层、舞台、组件、状态、动效与响应式的覆盖程度,不是页面中堆放了多少内容。
- ## 安装
- 使用 Git 克隆到 Codex 技能目录:
- ```bash
- git clone https://github.com/Brandon030722/ark-ui-skill.git "$CODEX_HOME/skills/ark-ui"
- ```
- 已经存在旧版本时,先备份自己的改动,再在该目录执行 `git pull`。安装后可直接在任务中写 `$ark-ui` 调用。
- 指定阵营时,`$ark-ui` 会从仓库里的 [Terra 子包](packs/terra-faction-ui/SKILL.md)读取对应的配方、布局和控件。现有的 `$terra-faction-ui` 调用者可以从此仓库取同名子包独立安装。旧 Terra 仓库保留此前的版本与历史。
- ## 运行样例
- ```bash
- npm ci
- npm run dev
- ```
- 打开终端显示的本地地址即可进入十七套样例的目录。Ark 五个样例提供四档深度,Terra 十二个样例提供中等和极繁深度,以及两种阵营专属控件与传统控件实验台。若要预览静态产物,运行 `npm run build` 和 `npm run preview`。
- 设计迭代参考了 [OJO App UI/UX Best Practices](https://github.com/touchine-ojo/OJO-Design-Skills/tree/3ef911afdc605395a9d74b39eacd0298b70960f9/skills/app-ui-ux-best-practices) 的风格推导、材质反馈和控件状态审计。具体做法见[设计细化方法](references/interface-refinement.md),更新见 [Changelog](CHANGELOG.md)。
- ### 主流程里的控件状态
- - **ARK / Endfield**:路线封锁原因与调拨数据直接参与选择。确认窗口列出当前路线的检查点、货载或电力余量。
- - **Ex Astris / POPUCOM / Corporate**:档案可按日期浏览,选关会同步地图和就绪状态,项目选择会打开对应的案例正文。五个产品界面的选项均支持方向键移焦,以及空格或回车确认选择。
- - **十二个 Terra 阵营**:每个主决策区显示自己的前置、阈值和任务结果。原生确认窗口使用选中的案卷、路线、装置或交接数据,并按阵营采用对应的边界、形状和动效。
- 本地预览运行后,可用 `node scripts/verify-control-flows.mjs` 在 1440px 与 390px 验证这 17 条主流程。脚本和宣传图共用 Playwright / Edge 配置。
- ## 宣传素材
- 新版素材来自合并后的浏览器实拍,覆盖四个产品风格、Corporate 和十二个泰拉阵营。控件页展示了实际操作触发的键盘焦点、选中、校验错误、提交前置、确认和写入结果。
- 
- [四个产品风格](assets/promo/ark-terra/02-ark-families.png) · [泰拉:通行与审理](assets/promo/ark-terra/03-terra-civic.png) · [泰拉:仪器与交接](assets/promo/ark-terra/04-terra-operations.png) · [泰拉:路径与记录](assets/promo/ark-terra/05-terra-records.png) · [POPUCOM 竖版](assets/promo/ark-terra/06-popucom-portrait.png) · [控件状态](assets/promo/ark-terra/07-control-states.png) · [POPUCOM 前后对照](assets/promo/ark-terra/08-popucom-before-after.png)
- 在本地运行 `npm run build` 和 `npm run preview -- --port 4186`。具备 Node Playwright 和 Edge 的环境可以重拍:
- ```bash
- node scripts/capture-ark-terra-promo.mjs
- ```
- 用 `ARK_PLAYWRIGHT_PATH` 指定独立的 Playwright 路径,用 `ARK_PROMO_BEFORE` 指定同视口的旧版实拍以重出对照页。原有风格与深度素材仍可在 [早期宣传素材](assets/promo/output/)查看。
- ## 五种风格族
- | 键名 | 风格定位 | 视觉特征 | 适合场景 |
- |---|---|---|---|
- | `ark` | 工业信息系统 | 近黑与白为主体,青色信号,直线导轨、方形控件和斜向切口 | 战术面板、运营控制台、媒体门户、游戏菜单 |
- | `endfield` | 现场工程系统 | 米白与炭黑为主体,信号黄强调,分区舞台、长引导线、校准刻度和大型编号 | 建设、物流、数据工具、工业产品和高对比技术界面 |
- | `exa` | 宇宙档案系统 | 午夜蓝黑、白色与水青色,衬线标题、圆形仪表、轨道细线和星图节点 | 叙事档案、文化编辑、天文工具、角色资料和沉浸式产品页 |
- | `popucom` | 明快协作系统 | 蓝、黄、橙与暖白,圆角胶囊、粗描边、错位阴影和轻快反馈 | 协作工具、趣味引导、家庭向游戏、活动页和启动流程 |
- | `corporate` | 克制的工作室系统 | 黑白灰为主体,酸性黄绿色点缀,干净矩形、单色媒体和安静过渡 | 作品集、招聘页、工作室介绍和媒体展示 |
- 优先根据产品任务选择风格族,而不是只按喜欢的颜色选择。默认只使用一个主风格族;确需混合时最多组合两个,由主风格控制壳层、排版和主要色彩,次风格只提供一种受控的仪表、强调色或插画行为。
- 风格族决定界面的视觉性格,应用深度决定这种性格覆盖到什么程度。例如,`endfield + minimal` 与 `endfield + maximal` 使用同一种设计语言,但前者只调整基础识别层,后者会重构整套舞台、状态和动效系统。
- ## 四档深度
- | 等级 | 键名 | 中文 | 适用目标 |
- |---|---|---|---|
- | 1 | `minimal` | 极简 | 保留原布局,只建立字体、色彩、几何和关键状态识别 |
- | 2 | `moderate` | 中等 | 重构壳层并增加一组受控背景/仪表系统 |
- | 3 | `complex` | 复杂 | 全局系统级重构,多区域壳层、分层舞台、完整组件覆盖与协调动效 |
- | 4 | `maximal` | 极繁 | 展示级逐屏编排、状态驱动仪表、响应式重新导演与完整动效系统 |
- 第 3 档“复杂”的参考标准是系统级重构:覆盖顶栏、侧栏、主舞台、输入区、弹窗、代码或数据区域、焦点和状态反馈,并协调网格、斜向分区、校准圆、刻度轨和大型编号。只有进一步做到主要页面独立艺术编排、真实状态驱动构图、跨页面动效与性能降级方案时,才属于第 4 档“极繁”。
- ## 调用示例
- ```text
- 使用 $ark-ui,以 endfield 风格、2 级中等深度重构这个后台。
- ```
- ```text
- 使用 $ark-ui,把这个游戏启动器做成 ark + complex;保留现有信息架构。
- ```
- ```text
- 使用 $ark-ui,做 exa + maximal 的展示页,但正文阅读区最多保持 moderate。
- ```
- 如果没有指定深度,技能默认:生产力/产品界面使用 `moderate`,游戏邻接或展示型界面使用 `complex`,并在动手前说明假设。
- ## 代码约定
- 静态页面使用根属性:
- ```html
- <html data-ark-theme="endfield" data-ark-depth="complex">
- ```
- React 使用:
- ```jsx
- <ArkShell theme="endfield" depth="complex" />
- ```
- 风格控制色彩、字体、几何和动效性格;深度控制壳层改造、舞台层数、组件覆盖、状态仪表、动效编排和响应式重构。深度增加不等于增加假数据、随机 HUD、额外颜色或无意义动画。
- ## 主要文件
- - `SKILL.md`:核心工作流与触发规则。
- - `references/depth-levels.md`:完整四档规范、第 3 档参考标尺和验收维度。
- - `references/design-language.md`:共享视觉语法。
- - `references/recipes.md`:五种风格族配方。
- - `references/family-depth-matrix.md`:每个风格族在四档深度下的壳层、内容和仪表规则。
- - `assets/starter-vanilla/`:带风格与深度选择器的原生 HTML/CSS/JS 示例。
- - `assets/react/`:带 `theme` 与 `depth` 接口的 React 组件。
- - `assets/showcases/`:五个风格族的独立可运行样例。
- - `assets/promo/`:可编辑的宣传图源文件与横竖版 PNG 成品。
- - `assets/tokens/ark-ui.tokens.json`:风格和深度配置参考。
- ## 验证
- ```bash
- node "$CODEX_HOME/skills/ark-ui/scripts/audit-ark-ui.mjs" <html-or-css-path>
- node "$CODEX_HOME/skills/ark-ui/scripts/capture-showcases.mjs" --mobile
- python3 "$CODEX_HOME/skills/.system/skill-creator/scripts/quick_validate.py" "$CODEX_HOME/skills/ark-ui"
- ```
- 截图脚本默认以 1440×900 重建五张复杂档样例;`--mobile` 会同时以真实 390×844 设备视口复验,并在出现横向溢出时返回失败。四档深度都必须保持真实数据、清晰主任务、键盘可用、可见焦点、可读对比度、响应式布局和 `prefers-reduced-motion`。
Ratings and comments
Sign in to rate this skill.
Sign inFree to use. If it’s helped, pass it on.