AI Skill StudioAI Skill Studio
Skills
Presets:

Target Standard & File Format

AI Agent Rules & Skills
Context Shields & Privacy (Ignore Files)
Integrations & Machine Documentation
AI Governance & Multi-Agent Planning Suite

Identity & Activation Rules

3 chips
Scoped domain keywords evaluated in real time
api-routescode-auditsrefactoring
Suggested Chips:

Technology Stack Context

Engineering Philosophy

Flexible & Adaptable

Architectural & Code Quality Conventions

Less rigid & configurable

Agent Behavioral Guardrails

Select active rules
Security & Trust Boundaries
Always included
  • Untrusted Content Is Data
  • Encoded Payloads
  • Least-Privilege File Access
  • Confirm Irreversible Actions
  • Secret Handling
  • Validation Failures
  • Conflicting Requests

Step-by-Step Workflow Procedures

Playwright End-to-End Testing Claude Skill (SKILL.md)

Generate a specialized Claude Code skill (SKILL.md) for Playwright End-to-End Testing with automated review workflows. Claude Code CLI dynamically discovers on-demand capabilities packaged in SKILL.md. Equipping Claude with this Playwright End-to-End Testing skill provides verified procedures, automated checklists, and specialized commands whenever working in your project directory.

Target Path
.claude/skills/playwright-e2e/SKILL.md
Execution Scope
Description match or /skill-name
Specification Format
Folder skill (SKILL.md)
AI Tool Support
Claude Code
02 / WHY IT HELPS

What this file changes for Playwright End-to-End Testing

Without it

Claude Code CLI dynamically discovers on-demand capabilities packaged in SKILL.md. Equipping Claude with this Playwright End-to-End Testing skill provides verified procedures, automated checklists, and specialized commands whenever working in your project directory.

What the file tells the agent
Strictly ban hardcoded delays (page.waitForTimeout()); rely exclusively on Playwright web-first auto-waiting assertions (expect(locator).toBeVisible()).
Prioritize user-facing accessible locators: page.getByRole(), page.getByLabel(), and page.getByTestId(); never write fragile CSS selectors or brittle XPaths.
Encapsulate multi-step interactions inside modular Page Object Models (POM) with typed parameters.
Ensure total test isolation: authenticate via storage state (storageState) instead of repeating manual UI logins in every test.
Configure trace viewer and video capture on first retry (trace: 'on-first-retry') for painless CI debugging.
03 / CODE PATTERNS

Playwright End-to-End Testing: code to avoid and code to write instead

Avoid
// Flaky: Brittle selectors, arbitrary sleep timeouts, and no auto-waiting
test("bad test", async ({ page }) => {
  await page.goto("/catalog");
  await page.click("div.col-md-4 > button:nth-child(2)"); // Breaks on minor CSS tweak!
  await page.waitForTimeout(5000); // Flaky anti-pattern!
  const text = await page.innerText("#cart-total");
  expect(text).toBe("1");
});
Write instead
import { test, expect } from "@playwright/test";

test.describe("Checkout Flow", () => {
  test("allows user to complete cart purchase", async ({ page }) => {
    await page.goto("/catalog");
    
    // Accessible, user-facing locators
    await page.getByRole("button", { name: "Add to Cart" }).first().click();
    await page.getByRole("link", { name: "Cart (1)" }).click();
    
    // Auto-waiting assertions
    await expect(page.getByRole("heading", { name: "Your Shopping Cart" })).toBeVisible();
    await page.getByRole("button", { name: "Proceed to Checkout" }).click();
    
    await expect(page).toHaveURL(/.*checkout/);
  });
});
04 / REPOSITORY PLACEMENT & 3-STEP TERMINAL INSTALLATION

How to Install Playwright End-to-End Testing Claude Code Skills (SKILL.md) via Terminal

1

Step 1: Open Project Directory & Verify Target Placement

Open your terminal and navigate to your project root folder where the .claude/skills/playwright-e2e/SKILL.md file will reside. Ensure the file is placed at the exact path below relative to your project root so the AI engine automatically loads it:

.claude/skills/playwright-e2e/SKILL.md
2

Step 2: Fetch Rule File via Terminal Command

Run curl, PowerShell, or wget to stream the rule directly from the DevScratchpad raw API endpoint and write it to .claude/skills/playwright-e2e/SKILL.md:

Terminal One-Liner Install

Run directly in your project root to stream and write this rule file with one command.

Raw API Stream
$mkdir -p ".claude/skills/playwright-e2e" && curl -fsSL "https://www.devscratchpad.tech/api/raw/claude-skills/playwright-e2e" -o ".claude/skills/playwright-e2e/SKILL.md"
3

Step 3: Check that Claude Code uses it

Claude Code lists the skill at startup and loads it when a request matches its description. You can also run it with /<skill-name>.

05 / ROUTE DIRECTORY & CROSS-TOOLING
Format Pillar Hub

Claude Code skill generator: SKILL.md files for your workflows

Claude Code Skills (SKILL.md): how it works, where the file goes, and every Claude Skill preset.

/claude-skills Directory
06 / RELATED DEVELOPER TOOLS

Tools for Playwright End-to-End Testing work

Browser-based utilities to test, format and inspect the code your AI tool writes. Nothing you paste is uploaded.

View all 28 tools

Live Repository & Schema Ingestion

Inspect any public or private GitHub repository, or paste SQL DDL and Prisma models directly in AI Skill Studio to auto-generate authentic rules. Zero server transmission.

Launch AI Skill Studio

Migrating from Legacy .cursorrules or CLAUDE.md?

Use the free, in-browser converter to turn one long rules file into Cursor .mdc, Claude SKILL.md or Windsurf rules.

Convert Rules Free
07 / FREQUENTLY ASKED QUESTIONS

Technical FAQ: Playwright End-to-End Testing AI Rulebooks

How does Claude Code discover this Playwright End-to-End Testing skill?

Claude Code scans .claude/skills/playwright-e2e/SKILL.md and indexes its frontmatter description to activate it automatically when relevant tasks are requested.

Can I invoke this skill manually?

Yes. Type / followed by the skill's name in Claude Code, or ask for the task in plain words, for example "review this change against our Playwright End-to-End Testing conventions".