Frontend & Design · By inkline

Repro-first QA for Inkline — minimal .ink.tsx reproductions, the visual-parity and cross-target harnesses, fuzz targets, and how to audit teammates' claims.

inkline/inkline

How Inkline components are built and kept consistent — the headless/styled split, family anatomy, prop/axis conventions, recipe consumption, the current 5-family catalog and its gap list.

inkline/inkline

How design tokens and recipes flow from styleframe into Inkline — the presets, the two faces of virtual:styleframe, recipe class contracts, theming, and the rules for custom CSS in components.

inkline/inkline

Phase 2 of building an Inkline component — write the .ink.tsx source.

inkline/inkline

The .ink.tsx authoring API — defineComponent, the compiler macros (defineProps, defineModel, defineEmits, defineSlot, hasSlot), signals, control flow, slots, two-way binding, events — plus…

inkline/inkline

Phase 1 of building an Inkline component — design the API. An agent skill from inkline/inkline.

inkline/inkline

Anatomy and maintenance of inkline-starter- repos and examples — the two starter flavors, what every starter must include, per-framework specifics, and the…

inkline/inkline

Phase 3 of building an Inkline component — author single-source Storybook stories.

inkline/inkline

Build a new Inkline component end-to-end — research the API, implement the headless + styled .ink.tsx source, add Storybook stories, write cross-target tests, and finalize docs/changeset.

inkline/inkline

Phase 5 of building an Inkline component — finalize docs and the release.

inkline/inkline

The seven framework output packages and the boundaries Inkline lives on — exports contracts, peer-dep/version matrix, per-target capability gaps, idiom fidelity, and the styleframe upstream…

inkline/inkline