---
title: "Data attributes"
description: "Every data-* attribute the system emits, the condition that produces it, and the values it can take."
url: "https://opsinjs.pensievelabs.org/docs/reference/generated/data-attributes"
source: "https://opsinjs.pensievelabs.org/docs/reference/generated/data-attributes.md"
section: "Reference"
kind: "reference"
reviewed: "2026-09-02"
reviewer: "engineering"
aliases: ["data-attributes", "styling hooks", "every data attribute"]
---

> Elements written as `<PascalCase … />` below are opsinjs documentation
> components. Their attributes are the content: the values they render are
> generated from `tokens/*.json` and `registry/catalogue.ts` and are
> published separately at https://opsinjs.pensievelabs.org/r/index.json and under the Reference
> section.
> Nothing is missing from this page. The data simply does not live in
> the prose.

Written by `scripts/build-reference.mts`. A data attribute is a styling contract covered by the versioning policy in the [Changelog](../../changelog.mdx): removing one, or changing when it appears, is a breaking change. [Styling](../../styling.mdx) describes the contract.

{/* opsinjs:generated:begin - everything below is replaced by scripts/build-reference.mts */}

<NoDataYet script="scripts/build-reference.mts" />

This script does not read the component sources for `data-*` attributes yet, so there is no table, which is not the same as no attribute being emitted. Every part carries `data-slot`, and `data-status`, `data-category` and `data-opsinjs-value` appear where they apply, with Base UI's `data-open`, `data-starting-style` and `data-ending-style` inherited. That is the whole component contract, closed at those four, as Styling describes. The squircle is not among them: Card, Callout and Dialog set an inline `corner-shape` property instead. `data-opsinjs-not-implemented` is a documentation-site marker, not a component attribute. Each component page lists its own attributes under Props interface.

{/* opsinjs:generated:end */}
