skills.rest
linaproai
linaproaiOFFICIAL
Explore all skills by this author →
WebsiteGitHub

lina-e2e

Standardize Playwright E2E test organization, naming, and TC ID assignment.

147|28|Updated Apr 24, 2026
Search Tags:#test automation#playwright#e2e testing#openspec#page object model#test case management#lina-pro
One-click install
npx skills add https://github.com/linaproai/linapro --skill lina-e2e
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: lina-e2e
Source: https://github.com/linaproai/linapro/tree/main/.agents/skills/lina-e2e
Command: npx skills add https://github.com/linaproai/linapro --skill lina-e2e

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates inconsistent E2E test case organization, naming, and ID management in LinaPro projects, which leads to messy test suites, duplicate TC IDs, and hard-to-maintain test code.

Core Features & Use Cases

  • Standardized Directory Layout: Defines clear separate paths for host feature tests and source plugin tests to keep test code organized by functional ownership.
  • Consistent Naming & ID Rules: Enforces TC{NNN}-{brief-name}.ts file naming and sequential per-module TC ID assignment to avoid conflicts and improve test traceability.
  • Full Test Workflow Guidelines: Covers test file structure, page object model conventions, fixture usage, OpenSpec task mapping, and screenshot verification requirements.
  • Use Case: When developing new LinaPro features or source plugins, use this Skill to create compliant, independent E2E tests that align with project quality standards.

Quick Start

Use the lina-e2e skill to create a new Playwright E2E test case for the notebook module following the project's directory and naming conventions.

Frequently Asked Questions about lina-e2e

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I standardize Playwright E2E test case naming and directory structure?▼

Standardized Playwright E2E tests use a TC{NNN}-{brief-name}.ts file naming convention and enforce separate directory layouts for host features and source plugins to maintain organization and prevent duplicate IDs.

What is the page object model convention for Playwright E2E tests in full-stack projects?▼

The page object model convention structures Playwright E2E tests by separating UI element selectors and interactions into reusable page classes, ensuring test independence and maintainable test code across modules.

How do I assign sequential test case IDs to avoid conflicts in E2E testing?▼

Sequential test case IDs are assigned per-module using the TC{NNN} format, ensuring each module maintains its own sequence to avoid duplicate TC IDs and improve test traceability across the suite.

Does Playwright E2E testing work with OpenSpec change task planning?▼

Playwright E2E testing integrates with OpenSpec change task planning by mapping test cases to OpenSpec tasks, ensuring new features and source plugins have compliant, independent tests aligned with quality standards.

Why does my E2E test suite become hard to maintain without standardized screenshots?▼

Without standardized screenshot verification, E2E test suites lack consistent visual validation, making failures difficult to trace; enforcing screenshot standards ensures maintainable and compliant test outcomes.

Related Skills

Explore More Software Engineering Skills→
xu-xiangxu-xiang
1.8k

tdd-workflow

Enforce test-driven development workflows with 80% coverage across unit, integration, and E2E tests.

Community
Basic
jls42jls42
1

Tests de Régression Visuelle

Capture and compare UI screenshots across viewports to detect visual regressions.

Community
Intermediate
incubateur-ademeincubateur-ademe
45

create-e2e-test

Automate Playwright end-to-end tests using page objects and fixtures.

Official
Intermediate
petrkindlmannpetrkindlmann
64

cypress-automation

Automate end-to-end and component testing with Cypress for TypeScript frontend applications.

Community
Advanced