Home / cogvera-labs / next-expo-supabase-agent-harness · GitHub

authoring-vertical-slice SKILL.md skillA

authoring-vertical-slice from cogvera-labs/next-expo-supabase-agent-harness is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned

mdr add cogvera-labs/next-expo-supabase-agent-harness/authoring-vertical-slice@git:20261102.d0f625e

Pins git:20261102.d0f625e in mdr.lock. Pin the fingerprint instead.

Audit grade: A, 17 of 17 checks passed
Kind: SKILL.md skill
Repository: cogvera-labs/next-expo-supabase-agent-harness
Path: template/base/.claude/skills/authoring-vertical-slice/SKILL.md
Versions recorded: 5
Latest version: git:20261102.d0f625e, committed Nov 2, 2026
First version recorded: Sep 30, 2026
Size: 11,042 bytes
Repository stars: 8
License: Apache-2.0

The migration -> RLS -> ./client read -> tRPC procedure -> web screen -> mobile screen -> test recipe for shipping one whole feature slice through the Next 16 web + Expo 57 mobile + Supabase monorepo in a single turn. Use when asked to add a feature, procedure, or screen end-to-end.

Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.

What the file says

# Authoring a vertical slice

One backend, two surfaces: a `packages/verticals/<slice>` domain, a tRPC procedure in
`@app/api` that `apps/web` serves and `apps/mobile` consumes, and a Server Action for the
web write. Build the slice in this strict order. Each layer has a lazy reference file — read
it before writing that layer (progressive disclosure keeps context lean). Delegate the two
non-trivial layers to the named subagent.

## Step 0 — read the contracts surface FIRST, and stop if the operation already exists

Before you write anything, read what the API already exposes:

- `tools/generated/action-inventory.json` — every tRPC procedure `appRouter` exposes, one
  committed row per procedure (emitted by `tools/gen-action-inventory.mjs`, regen-diffed by
  the `contracts` gate).
- `tools/generated/event-catalog.json` — every event the platform and vertical catalogs
  declare (emitted by `tools/gen-event-catalog.mjs`).
- `packages/api/src/routers/*.ts` — the routers themselves (`notes.ts` is the worked
  example, `system.ts` the health/`me` pair).

If an equivalent operation already exists, STOP and reuse it — a second `list`/`create` for
…

Read the whole file at its exact version.

How to install

The exact contents, by fingerprint

mdr add cogvera-labs/next-expo-supabase-agent-harness/authoring-vertical-slice@sha256:4c9cce4ec79f6a37

The line at the top of this page pins the label git:20261102.d0f625e, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.

Badge

[![mdr](https://markdownregistry.com/badge/art_xpowlb3bf6l4q2fj.svg)](https://markdownregistry.com/a/art_xpowlb3bf6l4q2fj)

1 badge image fetches in 30 days. What the badge shows.

Versions

The registry has recorded 5 versions of this file, between Sep 30, 2026 and Nov 2, 2026, about one every 8 days.

version	committed	commit	size	audit
git:20261102.d0f625e latest	2026-11-02	d0f625e	11,042 B	A	view · diff
git:20261021.a22139a	2026-10-21	a22139a	10,727 B	A	view · diff
git:20261006.2a1ce00	2026-10-06	2a1ce00	10,225 B	A	view · diff
git:20261006.6f9d456	2026-10-06	6f9d456	9,557 B	A	view · diff
git:20260930.1462bf9	2026-09-30	1462bf9	7,895 B	A	view

Audit of the latest version

A 17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.

pass: Frontmatter block present
pass: Frontmatter declares a name
pass: Frontmatter declares a description
pass: Size between 200 bytes and 200 KB (11042 bytes)
pass: No zero-width or bidi control characters
pass: No instruction hidden inside an HTML comment
pass: No link to an exfiltration or paste host
pass: No credential-shaped string
pass: No instruction to send local credentials anywhere
pass: No text hidden with inline styles
pass: No prompt-injection phrasing
pass: No curl or wget piped into a shell
pass: No recursive delete of root, home or parent
pass: No instruction to read or print local credentials
pass: No base64 blob over 200 characters
pass: No link to a raw IP address
pass: No script tag

Source

GitHub

cogvera-labs/next-expo-supabase-agent-harness · 8 stars · license Apache-2.0 · pushed 2026-11-07 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_xpowlb3bf6l4q2fj
GET https://markdownregistry.com/api/v1/resolve?ref=cogvera-labs/next-expo-supabase-agent-harness/authoring-vertical-slice
GET https://markdownregistry.com/api/v1/blob/4c9cce4ec79f6a37fcd3a3abd79f624441b508078fc9bddaec8d8d7b21131f2b

Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.

Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.

More from cogvera-labs/next-expo-supabase-agent-harness

authoring-e2ee-feature SKILL.md skill

cogvera-labs/next-expo-supabase-agent-harness · plugin/skills/authoring-e2ee-feature/SKILL.md · The decide-the-columns -> schema -> ciphertext DAL -> seal/open at the screen -> store-policy -> DSR record ->…