Vc Web Testing logo

Vc Web Testing

CommunityPopular
withkynam
vc-web-testing

Web testing with Playwright, Vitest, k6. E2E/unit/integration/load/security/visual/a11y testing. Use for test automation, flakiness, Core Web Vitals, mobile gestures, cross-browser.

Overview

Publisherwithkynam
Repositoryvibecode-pro-max-kit
Skill namevc-web-testing
Stars
1.1K
Forks
234
Bundled files
26
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.

  • 26 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

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

Installation

Install the Vc Web Testing 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.
    https://github.com/withkynam/vibecode-pro-max-kit/tree/main/.claude/skills/vc-web-testing
  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/withkynam/vibecode-pro-max-kit.git /tmp/vibecode-pro-max-kit
mkdir -p .claude/skills
cp -r /tmp/vibecode-pro-max-kit/.claude/skills/vc-web-testing .claude/skills/vc-web-testing
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Vc Web Testing 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 Vc Web Testing 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 Vc Web Testing 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.

Web Testing Skill

Output style: Follow process/development-protocols/communication-standards.md — answer-first, plain language, no unexplained jargon, TL;DR on long responses.

Comprehensive web testing: unit, integration, E2E, load, security, visual regression, accessibility.

Quick Start

bash
npx vitest run                    # Unit tests
npx playwright test               # E2E tests
npx playwright test --ui          # E2E with UI
k6 run load-test.js               # Load tests
npx @axe-core/cli https://example.com  # Accessibility
npx lighthouse https://example.com     # Performance

Testing Strategy (Choose Your Model)

ModelStructureBest For
PyramidUnit 70% > Integration 20% > E2E 10%Monoliths
TrophyIntegration-heavyModern SPAs
HoneycombContract-centricMicroservices

→ ./references/testing-pyramid-strategy.md

Reference Documentation

Core Testing

  • ./references/unit-integration-testing.md - Vitest, browser mode, AAA
  • ./references/e2e-testing-playwright.md - Fixtures, sharding, selectors
  • ./references/playwright-component-testing.md - CT patterns (production-ready)
  • ./references/component-testing.md - React/Vue/Angular patterns

Test Infrastructure

  • ./references/test-data-management.md - Factories, fixtures, seeding
  • ./references/database-testing.md - Testcontainers, transactions
  • ./references/ci-cd-testing-workflows.md - GitHub Actions, sharding
  • ./references/contract-testing.md - Pact, MSW patterns

Cross-Browser & Mobile

  • ./references/cross-browser-checklist.md - Browser/device matrix
  • ./references/mobile-gesture-testing.md - Touch, swipe, orientation

Performance & Quality

  • ./references/performance-core-web-vitals.md - LCP/CLS/INP, Lighthouse CI
  • ./references/visual-regression.md - Screenshot comparison
  • ./references/test-flakiness-mitigation.md - Stability strategies

Accessibility & Security

  • ./references/accessibility-testing.md - WCAG, axe-core
  • ./references/security-testing-overview.md - OWASP Top 10
  • ./references/security-checklists.md - Auth, API, headers

API & Load

  • ./references/api-testing.md - Supertest, GraphQL
  • ./references/load-testing-k6.md - k6 patterns

Checklists

  • ./references/pre-release-checklist.md - Complete release checklist
  • ./references/functional-testing-checklist.md - Feature testing

Scripts

Initialize Playwright Project

bash
node ./scripts/init-playwright.js [--ct] [--dir <path>]

Creates best-practice Playwright setup: config, fixtures, example tests.

Analyze Test Results

bash
node ./scripts/analyze-test-results.js \
  --playwright test-results/results.json \
  --vitest coverage/vitest.json \
  --output markdown

Parses Playwright/Vitest/JUnit results into unified summary.

CI/CD Integration

yaml
jobs:
  test:
    steps:
      - run: pnpm run test:unit      # Gate 1: Fast fail
      - run: pnpm run test:e2e       # Gate 2: After unit pass
      - run: pnpm run test:a11y      # Accessibility
      - run: npx lhci autorun       # Performance

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Vc Web Testing AI skill do?

Web testing with Playwright, Vitest, k6. E2E/unit/integration/load/security/visual/a11y testing. Use for test automation, flakiness, Core Web Vitals, mobile gestures, cross-browser.

Why use Vc Web Testing on TypingMind?

Because you install it once and use it with any model. Vc Web Testing 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 Vc Web Testing in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/withkynam/vibecode-pro-max-kit/tree/main/.claude/skills/vc-web-testing. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Vc Web Testing?

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 Vc Web Testing?

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

Is the Vc Web Testing AI skill free?

Yes. It is published on GitHub by withkynam 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 👇