aziontech/webkit

A monorepo-driven ecosystem for scalable UI development, enabling shared design systems, component libraries, and optimized build pipelines.

This repository also configures its own agents. See what webkit tells them →

3Stars on the repository
60Mods indexed here, across every type
todayLast push, which is what freshness is scored on
MITLicence, which decides whether bodies are shown

webkit-adopter

01

aziontech/webkit

Agent Claude Code

Runs and explains the @aziontech/webkit adoption flow — npx @aziontech/webkit init. Sets up deps, lint configs, pre-commit, the webkit MCP, and the Claude Code bundle in this project, idempotently.

not rated 3 today A 57 tokens original MIT

aziontech/webkit

Agent Claude Code

Measures how much of an app already renders through @aziontech/webkit versus hand-rolled UI, and produces a prioritized backlog of custom components that have a webkit equivalent to adopt.

not rated 3 today A 45 tokens original MIT

webkit-expert

03

aziontech/webkit

Agent Claude Code

Answers "which @aziontech/webkit component should I use, and how?" Grounds every answer in the installed catalog and the webkit MCP — never invents a component or an import path.

not rated 3 today A 44 tokens original MIT

webkit-reviewer

04

aziontech/webkit

Agent Claude Code

Reviews a diff for correct and performant @aziontech/webkit usage — flat imports, theme tokens, tree-shaking, reuse over reinvention. The local (non-CI) design-system review.

not rated 3 today A 45 tokens original MIT

webkit-ui-verifier

05

aziontech/webkit

Agent Claude Code

Runs the visual and behavioral QA pass on a @aziontech/webkit app — builds and serves it, drives real routes with headless Chromium, and reports only what it observed across themes, console, a11y, states, and interaction.

not rated 3 today A 55 tokens original MIT

At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: