菜单
Guides authoring, organizing, and referencing test fixtures in this repo. Use when creating new fixtures, writing tests that depend on fixtures, or deciding what should be checked into git. Engine fixtures (rendering corpora) live in the engine repo.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/gridaco/grida --skill fixtures命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Research, compare, and update AI model configurations. Covers text model tiers, image and video generation models, image tool models, pricing data sourcing, and provider-cost metering against prepaid org credit. Use when bumping model versions, adding new models, updating pricing, or auditing model specs against provider documentation.
Set up, download, verify, and seed the optional Grida Library developer corpus into local Supabase. Use when Library browse/search, Desktop reference picking, or agent Library tools need realistic local assets and Gemini embeddings; also use when changing the gridaco/grida consumer for gridaco/library developer-corpus releases.
Use BEFORE editing any file in `supabase/migrations/` or `supabase/schemas/`, OR when the user runs a `/database` subcommand (`compact local migration`, `rls scenarios`, `align`). Encodes the three contracts that protect the Grida database layer: applied migrations are immutable, RLS implementation mirrors tests (never the reverse), `schemas/*.sql` is the human-readable end-state. Companion to `supabase/AGENTS.md` (RLS, grants, security boundaries).
基于 SOC 职业分类
正在显示 SKILL.md
| name | fixtures |
| description | Guides authoring, organizing, and referencing test fixtures in this repo. Use when creating new fixtures, writing tests that depend on fixtures, or deciding what should be checked into git. Engine fixtures (rendering corpora) live in the engine repo. |
Fixtures are static input files — .fig archives, clipboard captures,
markdown samples, .grida documents — used as deterministic inputs to
parsing and I/O tests. They exist so that tests are reproducible,
self-contained, and don't depend on external services or generated data.
<domain>-<property>[-<descriptor>].<ext> — the
filename alone should tell you what's being tested.fixtures/
├── test-fig/ # Figma clipboard / .fig fixtures (LFS: *.fig, *.deck)
├── test-figma/ # Figma archive / REST fixtures
├── test-canvas/ # .canvas (dotcanvas) fixtures
├── test-markdown/ # Markdown fixtures
├── fonts/ # ← FROZEN SNAPSHOT (engine-owned)
├── images/ # ← FROZEN SNAPSHOT (engine-owned)
├── test-grida/ # ← FROZEN SNAPSHOT (engine-owned)
└── text-editor/ # ← FROZEN SNAPSHOT (engine-owned)
The engine repo owns the canonical, evolving copies of fonts/, images/,
test-grida/ and text-editor/ (its crates consume them at compile/test
time, with full git history carried over). The copies here exist only so
staying tests keep passing at their original paths — consumers:
@grida/fonts, @grida/refig, @grida/io, the editor reducer round-trip,
@grida/text-editor. Do not edit them here; re-snapshot deliberately
from the engine repo if the canon evolves. See
fixtures/README.md.
New engine fixtures (rendering, SVG/HTML corpora, engine formats) go to the engine repo: https://github.com/gridaco/nothing/tree/main/fixtures. New fixtures for staying product code go in a grida-owned directory here.
Large, third-party, or license-restricted corpora are never committed —
the engine repo keeps its own gitignored fixtures/local/ convention.
Never reference a gitignored local path in committed code, tests, or
documentation — it does not exist in CI or on other developers' machines.
If a doc must mention one (e.g. the refig corpus workflow in the io-figma
skill), clearly mark it local-only and note the download/build step.