Skip to content

gridaco/grida / .agents/skills/grounding

grounding

Verified

Establish what is actually true and current for the surface you are about to change — not just search. Grounding = locate the authoritative source and reconcile sources that disagree (code vs doc, migration vs schema, memory vs current code, live vs archived), not take the first hit. Use before any grep/find/explore of the codebase or docs, when deciding which of several definitions is the real one, or when a doc or memory conflicts with the code. Covers the source-of-truth hierarchy, reconciliation discipline, scoped ripgrep, and the docs/tags.yml + docsearch.py index.

FileKindSize
SKILL.mdskill md4.4 KB
scripts/docsearch.pyexecutablescript10.8 KB
---
name: grounding
description: >
  Establish what is actually true and current for the surface you are
  about to change — not just search. Grounding = locate the
  authoritative source and reconcile sources that disagree (code vs doc,
  migration vs schema, memory vs current code, live vs archived), not
  take the first hit. Use before any grep/find/explore of the codebase
  or docs, when deciding which of several definitions is the real one,
  or when a doc or memory conflicts with the code. Covers the
  source-of-truth hierarchy, reconciliation discipline, scoped ripgrep,
  and the docs/tags.yml + docsearch.py index.
---

# Grounding

Grounding is establishing what is **actually true and current for the
surface you are about to change**, then acting on that — not on a guess,
a memory, or the first grep hit. The hard part is not search; it is
picking the **authoritative** source and **reconciling** sources that
disagree.

> Intentional seed. This holds only Grida-specific facts that are not
> obvious from `CLAUDE.md`/`AGENTS.md`. Grow it from real, discovered
> specifics (concept→file anchors that bite repeatedly, conflicts that
> actually happened and how they resolved). Do not pad it with generic
> search advice a competent agent already knows.

## Source of truth (scoped to the surface)

Authority is per-surface — the engine model and its TS mirror can each
be right for their own surface and still disagree. Name the surface,
then trust:

- **Canvas render/node model** → the Rust engine, now in the engine repo:
  https://github.com/gridaco/nothing/blob/main/crates/grida/src/node/schema.rs.
  The TS mirror `editor/grida-canvas/` is authoritative for _editor
  behavior_ and can lag the engine.
- **DB schema** → `supabase/migrations/` (applied, immutable);
  `supabase/schemas/*.sql` is a readable projection that can lag — use
  the **database** skill.
- **AI model facts** → the pinned public `@grida/ai-models` release;
  **current hosted offerings and operation schemas** → GG discovery.
  Grida authors only `data/ai/presets.json` product choices and
  `data/ai/native-inputs.json` implemented native/BYOK inputs. Marked
  TypeScript literals and Rust assets are generated consumers. Follow
  [`ai-models`](../ai-models/SKILL.md) for ownership and regeneration.
- **Directory contract** → the nearest `AGENTS.md`/`README.md`.
- **"I remember API X…"** → re-read current code; a memory is a claim
  about a _past_ state, verify before acting.

Disagreement → decide which wins _and why_ (`git log -1` recency, what
the running entrypoint imports, what tests assert); don't average;
surface a material conflict to the user. **Never authoritative even when
they match:** `docs/_history/`,
`docs/@designto-code/` (synced — truth is upstream), `.ref/`.
`docs/cli/` is the replacement CLI's maintained user guide; only its explicitly
retired legacy pages are historical. Follow `docs/AGENTS.md` for that boundary.

## Dead-tree traps

Some directories are git-tracked but dead — a bare `rg` from repo root
returns obsolete hits that look like confirmation: `docs/_history/`,
`.ref/`. (The legacy editor trees `.legacy/` and `packages/.legacy/` were
retired May 2026; recover from the
`snapshot/legacy-with-2023-grida-code-editor-at-202505` branch.) `rg` already skips gitignored build dirs
(`node_modules/`, `.next/`, …); don't waste flags there.
Scope positively, or exclude the dead trees:

```sh
rg PATTERN editor/grida-canvas packages
rg PATTERN -g '!**/docs/_history/**'
```

## Grounding the docs

~360 markdown files; only `docs/wg/**` and `docs/reference/**` (plus the
user-facing trees in `docs/AGENTS.md`) are maintained. `docs/tags.yml`
is the controlled vocabulary; `tags:` frontmatter is the navigation
signal. Use the index, don't grep bodies — `scripts/docsearch.py` reads
frontmatter only, self-installs via `uv`, runs from any cwd:

```sh
S=.agents/skills/grounding/scripts/docsearch.py
uv run $S tags                          # vocabulary + usage counts + drift
uv run $S find --tag figma --tag wg     # AND (--any=OR); + --has K --field K=V
uv run $S show wg/feat-fig/glossary/fig.kiwi.md   # one file's frontmatter only
```

Before trusting a doc over code: `draft: true` = proposal not built yet
(intent ahead); `doc_tasks:` or stale `git log -1` = likely behind.

## Related skills

`database` (DB source-of-truth), `research` (upstream/peer projects),
`naming` (where new things belong).
rea-changelog-updatemorluto/reaPrepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
academy-guideanthropics/skillsStop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
claude-apianthropics/skillsReference for the Claude API / Anthropic SDK — model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model migration. TRIGGER — read BEFORE opening the target file; don't skip because it "looks like a one-liner" — whenever: the prompt names Claude/Anthropic in any form (Claude, Anthropic, Fable, Opus, Sonnet, Haiku, `anthropic`, `@anthropic-ai`, `claude-*`, `us.anthropic.*`, `[1m]`); the user asks about an LLM (pricing/model choice/limits/caching) — never answer from memory; OR the task is LLM-shaped with provider unstated (agent/MCP/tool-definition/multi-agent/RAG/LLM-judge/computer-use; generate/summarize/extract/classify/rewrite/converse over NL; debugging refusals/cutoffs/streaming/tool-calls/tokens). SKIP only when another provider is being worked on (overrides all triggers): OpenAI/GPT/Gemini/Llama/Mistral/Cohere/Ollama named in the query; OR `grep -rE 'openai|langchain_openai|google.generativeai|genai|mistralai|cohere|ollama'` over the project hits (run this grep FIRST if no provider named — don't Read the file).Stars: 198kUpdated Claude CodeCodexUnverifiedInstall
doc-coauthoringanthropics/skillsGuide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.Stars: 198kUpdated Claude CodeCodexVerifiedInstall