Skip to content

Components

Every component, live

246 React components in 21 groups, built on React Aria and styled only with the tokens. Each one is shown in the light, dark and high contrast themes, with code to copy and its accessibility notes.

Actions

Everything a person presses to do something: buttons and their states, links that look like buttons, copy, close, grouped and toggled actions, keyboard hints and the handles that reorder lists. Built to WCAG 2.2 AA as a target: visible focus, 24px minimum targets, keyboard for every action and states said in words, not colour alone.

Agents

The pieces of a view where several coding agents run side by side: panes with their state, the workspace tree, an overview of every session, the toolbar under a terminal and the steps of a pipeline. A session state always has a word and its own glyph shape, so colour never carries it alone, and every part reflows down to a 320px screen. Built to WCAG 2.2 AA as a target.

Brand

The Skribly marks and the small identity badges around them: the logo, the wordmark, the app lockup, people, agents, git hosts, trackers and sites. Badges use letters on a tint of a colour token, so they read in every theme and never rely on colour.

Charts

Plain SVG charts and figures for reports and dashboards, built to WCAG 2.2 AA as a target. Each chart is a named figure with a written summary; the arrow keys step through the data points and read each one; every value is also in a table behind a disclosure. Series differ by colour and by line pattern, and marks switch to system colours in forced colours. Charts draw at the width of their box, so labels keep their size at any zoom and thin out on narrow screens.

Code

The parts of a code workspace: changed files, the commit box with its reasons, the commit graph and refs, the pull request of a branch, the status under an editor, search results across files, and a page preview with its address bar and device sizes. Rows sit in List and TreeView from the data group, so arrow keys, typeahead and selection come from React Aria.

Content

Text people read: rendered Markdown, a write-and-preview field, code with a copy button, single commands, program output and a still terminal screen. Code and output scroll inside their own box, so the page never scrolls sideways.

Conversation

Chats with an agent and comment threads: the message log, bubbles, tool steps, the message box with attachments, and comments with a Markdown form. Every state carries a word and an icon, and failures that block are announced at once.

Data

Tables, lists, trees and timelines for showing records. Each collection has the same loading, empty and error states, and every interactive one runs on React Aria for keyboard, selection and screen reader support. Built to WCAG 2.2 AA as a target.

Feedback

Status, messages and loading. Success, information, warning and error share one system: each has a tone, an icon shape and a word, so colour never carries the meaning alone. Messages that arrive later are read out through polite live regions, and blocking errors through assertive ones.

Forms

Fields with one look and one message system: a label with a required or optional mark, help text, a status in the ok, info or warn tone, and an error with an icon. Every message is linked to its control, errors set aria-invalid, and a summary links to the fields after a failed submit. Built to WCAG 2.2 AA, from 320px up.

Media

Files and images: the library grid and its tiles, uploads, a picker dialog, an ordered image field for forms, crop and focal point, and the fields of an image preset. Built to WCAG 2.2 AA as a target: every tile, frame and marker has a keyboard and screen reader path, states are said in words with a glyph, and every layout reflows from 320px.

Ways to move between views, pages and filters: tabs, link tabs, segmented choices, tab strips that close, breadcrumbs, pagination, filter chips and the language controls. Built to WCAG 2.2 AA as a target, from 320px wide up.

Onboarding

Help for the first minutes: a guided tour that points at the interface, a first-steps card driven by real data, and checklists with the way to fix each item. Progress is always said in words as well as shown.

Ops

Running and tending the tools around the code: containers and compose files, alerts, audit findings with their score, plugins and rules with switches, a catalogue of skills, install and sign-in steps, editor themes and connected accounts. Rows sit in a List from the data group, so arrow keys, typeahead and selection come from React Aria.

Overlays

Layers over the page: dialogs, confirmations, popovers, menus and tips. Each one traps or returns focus, closes on Escape, keeps a visible border in forced-colors mode and fits a 320px screen, where the modal becomes a bottom sheet.

Pages

Whole screens for signing in, resetting a password and reporting an error. They reflow from 320px up, keep every message as a tone, an icon and a word, and are built to WCAG 2.2 AA as a target.

Finding things: the top-bar search with grouped results and the / key, the command palette, quick open for files, result rows and groups, search options and match highlighting. Built to WCAG 2.2 AA as a target, from 320px wide up.

Shell

The frame around every Skribly screen: the web layout with a dark sidebar and a top bar, the desktop layout with a title bar, an activity bar, a status bar and a dock, and split panes. It measures its own width, so it reflows the same in a narrow window, at 400% zoom and in a preview, and its sheets hold focus on small screens.

Surfaces

The boxes a screen is built from: cards, stat tiles, the welcome banner, settings sections, the list of things that need attention, dividers and selectable tiles. Each one reflows from 320px up and keeps its edges in Windows high contrast.

Theme and accessibility

Light, dark and high contrast themes with the reader settings of the Skribly apps: text size, reduced motion, a strong focus ring and underlined links. Also the small pieces every page needs: a skip link, hidden labels and live announcements. Built to WCAG 2.2 AA as a target.

Tracker

Issues and the board of Skribly Tracker, and the tasks the Agent pulls from any tracker. Status, priority and type each pair a glyph shape with a word, so nothing rests on colour; lists reflow from 320px; the board moves cards by pointer, keyboard, screen reader and a one-tap menu, and says what happened through live regions. Built to WCAG 2.2 AA as a target.

Search this site

Arrows move through the results, Enter opens one, Esc closes. Ctrl K /