菜单
Write any link or URL so it resolves where it is rendered, not where it lives in the repo. Use when authoring or editing a link — in docs/wg specs, crate READMEs and docstrings, the npm-published wasm package README, or skills. This is the engine-repo variant of the grida links doctrine.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
How to think about names in the Grida repo — not conventions, but what a name commits you to, reveals about the system, and costs to change. The central discipline is that a strict, honest name refuses to grow, and that refusal drives the repo's shape (flat modules, small agnostic packages, suffix siblings). Use when planning a new package, crate, module, directory, route group, or test corpus — the name comes first.
Manual-invocation only. Five-phase feature loop (audit → ground → fixture → implement → verify) for driving a single CSS feature to Chromium parity in the grida htmlcss renderer.
Manual-invocation only. Five-phase feature loop (audit → ground → fixture → implement → verify) for driving a single SVG feature to Chromium parity in the grida `htmlcss::svg` renderer. Sibling to `dev-render-htmlcss-feature` (HTML/CSS path); same loop shape, different corpus (resvg-test-suite + Chrome bake) and different scoring (multi-oracle: consensus / disputed / UB).
Doctrine for drafting and keeping working-group docs under `docs/wg/**` — RFC/RFD specs and findings/research/glossary. A WG doc is a language-agnostic, code-agnostic study of a domain: it argues *why* and defines *what*, never *how in our code*. Use when writing or editing anything under `docs/wg/`, an RFC/RFD, a spec, a design note, a glossary, or research findings — including "write up the design", "document the spec", or "capture what we learned". Not for plans/TODOs (untracked `*.plan.md`), user docs, or SDK API refs — use `docs` to route those.
Guides authoring, organizing, and referencing test fixtures across the engine repo. Use when creating new fixtures, writing tests that depend on fixtures, or deciding what should be checked into git.
Guides work on the Grida file format (.grida): the FlatBuffers schema and the Rust decoder that loads it into the canvas runtime. Use when working with .grida files, the FlatBuffers schema, codegen, or debugging format issues. (The TS reader/writer packages live in the grida product repo.)
基于 SOC 职业分类
| name | links |
| description | Write any link or URL so it resolves where it is rendered, not where it lives in the repo. Use when authoring or editing a link — in docs/wg specs, crate READMEs and docstrings, the npm-published wasm package README, or skills. This is the engine-repo variant of the grida links doctrine. |
A link is correct or broken at the surface it is rendered on, for that surface's audience — not where the text lives in the repo. Before you write any link: (1) where is this text rendered? (2) who reads it there? (3) when they click, where does it resolve from that host — and is that the thing you meant?
| Surface | Lives in | Audience |
|---|---|---|
| GitHub (repo browse) | everything — incl. docs/wg/** (also published by this repo's www/ docs app, which resolves the same .md-suffixed relative links; GitHub remains the canonical host) | engine developers |
npm (npmjs.com) | crates/grida-canvas-wasm package README | package users |
| Raw / no host | IDE, stack traces, compiled output | whoever has it |
| URL | What |
|---|---|
https://github.com/gridaco/nothing | This repo. File → …/blob/main/<path>; dir → …/tree/main/<path>; main only, never a SHA |
https://github.com/gridaco/grida | The product monorepo (editor, packages, service docs). Same file/dir forms |
https://grida.co | The product · https://grida.co/docs = the product docs site (publishes grida's docs tree) |
| Rendered in | Target | Use |
|---|---|---|
| anywhere in this repo | anything in this repo (crates, docs/wg, fixtures, format) | relative repo path — same host (GitHub) everywhere |
| anywhere in this repo | a grida-repo file/dir | absolute `https://github.com/gridaco/grida/blob |
| anywhere in this repo | a published grida docs page (staying clusters: platform, ai, …) | hosted URL https://grida.co/docs/<path> |
| npm package README | anything in-repo | absolute https://github.com/gridaco/nothing/blob/main/<path> — relative dies on npmjs.com |
| any | external | https://… as-is |
https://grida.co/docs/wg/<engine-cluster>/… links. The
docs site does not publish this repo's wg tree (canvas, format, research,
engine feat-*). Old published URLs survive via a redirect shim in grida —
do not author new links through a redirect; use the same-repo relative
path (in-repo surfaces) or this repo's absolute GitHub URL (external
surfaces).main only — never pin a commit/branch SHA.#fragment: link the file, not a guessed anchor, unless
verified in the target host's slug scheme./Users/...), /tmp, untracked or gitignored files
(fixtures/local/** may be described as local-only, never linked as if
it resolves). If git ls-files doesn't show it and it isn't a public URL,
it does not exist for the audience.