Ring:Checking Frontend Quality logo

Ring:Checking Frontend Quality

Organization
LerianStudio
ring:checking-frontend-quality

Checking frontend quality against changed UI via ring:qa-frontend in accessibility, visual, e2e, or performance mode and aggregating pass/fail verdicts. Use when a frontend change needs standalone a11y, visual-snapshot, Playwright e2e, or Lighthouse/Core-Web-Vitals validation outside the dev cycle. Skip for backend-only or non-UI work, or inside ring:running-dev-cycle-frontend, which already runs these in Gate 0.

Overview

PublisherLerianStudio
Repositoryring
Skill namering:checking-frontend-quality
Stars
215
Forks
28
Bundled files
Instructions only
LicenseApache-2.0
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by LerianStudio on GitHub. Read the source before you install it.

Installation

Install the Ring:Checking Frontend Quality AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/LerianStudio/ring.git /tmp/ring
mkdir -p .claude/skills
cp -r /tmp/ring/dev-team/skills/checking-frontend-quality .claude/skills/lerianstudio-ring-checking-frontend-quality
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Ring:Checking Frontend Quality in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Ring:Checking Frontend Quality on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Ring:Checking Frontend Quality is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Frontend Quality Checks

When to use

  • A frontend task needs standalone quality validation outside ring:running-dev-cycle-frontend (which owns these checks in Gate 0).
  • You want to run one specific check (a11y, visual, e2e, or performance) against changed UI components, or all of them at once.

Skip when

  • Backend-only project with no UI components.
  • Task is documentation-only, configuration-only, or non-code.
  • Changes limited to build tooling, CI/CD, or infrastructure.
  • Inside ring:running-dev-cycle-frontend — that orchestrator already runs these in Gate 0.

Related

Complementary: ring:running-dev-cycle-frontend, ring:qa-frontend

Modes

ModeWhat it checks
accessibilityaxe-core automated scans, zero WCAG 2.1 AA critical/serious violations, keyboard nav, focus management
visualSnapshot tests across all component states and viewports (mobile 375px / tablet 768px / desktop 1280px)
e2ePlaywright user-flow tests across Chromium, Firefox, and WebKit (happy + error paths)
performanceLighthouse > 90 and Core Web Vitals (LCP < 2.5s, CLS < 0.1, INP < 200ms), bundle budget
allRuns all four modes in parallel and aggregates the verdicts

The deep per-mode requirements live in the agent's mode files (dev-team/agents/qa-frontend-modes/{accessibility,visual,e2e,performance}.md). Do not duplicate them here.

Step 1: Validate Input

Required: unit_id (TASK id), implementation_files, gate0_handoffs. Required: mode — one of accessibility | visual | e2e | performance | all. Optional: components_list, user_flows_path, performance_baseline.

Step 2: Dispatch

For a single mode, dispatch the QA analyst with the selected mode:

yaml
Task:
  subagent_type: "ring:qa-frontend"
  description: "Frontend {mode} checks for {unit_id}"
  prompt: |
    mode: {mode}
    unit_id: {unit_id}
    implementation_files: {implementation_files filtered to UI files}
    gate0_handoffs: {gate0_handoffs}
    # optional, when relevant to the mode:
    # user_flows_path, performance_baseline, components_list

    Load qa-frontend-modes/{mode}.md and follow it.

For mode: all, dispatch the four modes in parallel (one Task batch — four Task calls in a single message), each with the same inputs and its own mode. Aggregate the four verdicts into the output below.

Output

Aggregated pass/fail per mode:

markdown
## Frontend Quality Result
unit_id | mode(s): {mode or all}

| Mode | Result | Violations / Failures | Iterations |
|------|--------|-----------------------|------------|
| accessibility | PASS/FAIL | N | N |
| visual | PASS/FAIL | N | N |
| e2e | PASS/FAIL | N | N |
| performance | PASS/FAIL | N | N |

## Overall: PASS | FAIL
(FAIL if any dispatched mode failed.)

Frequently asked questions

What does the Ring:Checking Frontend Quality AI skill do?

Checking frontend quality against changed UI via ring:qa-frontend in accessibility, visual, e2e, or performance mode and aggregating pass/fail verdicts. Use when a frontend change needs standalone a11y, visual-snapshot, Playwright e2e, or Lighthouse/Core-Web-Vitals validation outside the dev cycle. Skip for backend-only or non-UI work, or inside ring:running-dev-cycle-frontend, which already runs these in Gate 0.

Why use Ring:Checking Frontend Quality on TypingMind?

Because you install it once and use it with any model. Ring:Checking Frontend Quality is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Ring:Checking Frontend Quality in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/LerianStudio/ring/tree/main/dev-team/skills/checking-frontend-quality. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Ring:Checking Frontend Quality?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Ring:Checking Frontend Quality?

As many as you like. As long as a model supports skills, you can use Ring:Checking Frontend Quality with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Ring:Checking Frontend Quality AI skill free?

Yes. It is published on GitHub by LerianStudio under the Apache-2.0 license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇