skills.rest
AbhiRKeesara
AbhiRKeesaraCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

code-organization

Organize Playwright projects into domain-based folder structures and naming conventions.

Updated Jan 31, 2026
Search Tags:#structure#playwright#naming-conventions#domain-driven#project-organization#page-objects
One-click install
npx skills add https://github.com/AbhiRKeesara/test-automation-skills --skill code-organization-abhirkeesara
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-organization
Source: https://github.com/AbhiRKeesara/test-automation-skills/tree/main/skills/code-organization
Command: npx skills add https://github.com/AbhiRKeesara/test-automation-skills --skill code-organization-abhirkeesara

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Code Organization Skill helps teams structure Playwright projects by business domain, reducing maintenance, onboarding time, and confusion.

Core Features & Use Cases

  • Recommended Folder Structure: guidelines for tests, page-objects, fixtures, and utilities organized by domain.
  • Naming & Co-location: rules for descriptive file names and keeping related files together.
  • Use Case: Organize tests into domains like pharmacy, patient-portal, and billing to improve discoverability and reuse.

Quick Start

Start by aligning your project with the recommended folder structure, then adopt domain-based naming and co-location practices.

Frequently Asked Questions about code-organization

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

FAQPage Schema
How do I structure a Playwright project by domain?▼

Structure a Playwright project by domain by organizing tests, page-objects, fixtures, and utilities into business domains like pharmacy, patient-portal, or billing. This reduces maintenance, onboarding time, and confusion.

What are the naming conventions for Playwright tests and page-objects?▼

Playwright naming conventions require descriptive file names and co-location of related files within domain folders. Keeping tests, page-objects, and fixtures together improves discoverability and reuse across the project.

What is the best way to organize Playwright fixtures and utilities?▼

The best way to organize Playwright fixtures and utilities is co-locating them within a recommended domain-based folder structure. This aligns resources with specific business domains to improve discoverability and reuse.

Can I use domain-driven structure to reorganize an existing Playwright project?▼

Yes, domain-driven structure applies to both new project setups and reorganizations. It guides folder layouts, naming conventions, and co-located resources to align existing tests, page-objects, and fixtures by business domain.

Why should I organize Playwright tests by business domain instead of file type?▼

Organizing Playwright tests by business domain reduces maintenance and onboarding time. Domain-driven structure groups related tests, page-objects, and fixtures together, preventing confusion and improving discoverability.

Does a domain-based Playwright folder layout require specific dependencies?▼

No, a domain-based Playwright folder layout requires no specific dependencies. It enforces a recommended folder structure, naming conventions, and co-location practices natively within your existing project setup.

Related Skills

Explore More Software Engineering Skills→
krl76krl76

unity-project-scout

Inspect Unity version, packages, asmdefs, and folder structures for baseline assessment.

Community
Intermediate
leather-ioleather-io
28

testing-patterns

Codify Vitest testing conventions for TypeScript unit and integration tests.

Official
Intermediate
sehoon787sehoon787
16

e2e-testing

Automate Playwright end-to-end test creation with Page Object Model patterns.

Community
Advanced
DojoGenesisDojoGenesis
2

file-management

Generate documented directory structure plans with tree diagrams and naming conventions.

Community
Intermediate