🤖 AI Assistant Instructions

📋 Primary Reference Document

CRITICAL: Always use

CODING_STANDARDS.md

as the primary reference document when:

Writing new code
Reviewing existing code
Making suggestions for improvements
Implementing new features
Creating tests
Refactoring code

🎯 Key Guidelines

Before Writing Any Code:

Read
```
CODING_STANDARDS.md
```
first
Follow all established patterns and conventions
Maintain consistency with existing codebase
Use the exact naming conventions, import patterns, and code structure defined in the standards

Code Generation Rules:

✅ Always use TypeScript path aliases (
```
@pages/*
```
,
```
@utils/*
```
, etc.)
✅ Always include
```
.js
```
extensions in imports
✅ Always follow the Page Object Model pattern established in the project
✅ Always use Faker.js for test data generation
✅ Always follow the established test structure and naming conventions
✅ Always use the exact import order and patterns shown in standards

File Structure to Follow:

pages/ - Page Object classes extending BasePage
tests/ - Test files using established patterns
utils/ - Helper functions and TypeScript types
constants/ - Application constants with `as const`
config/ - Configuration files
fixtures/ - Custom Playwright fixtures

Test Patterns to Use:

Use custom fixtures from
```
@fixtures/pages.js
```
Follow test naming:
```
should [action] [expected result]
```
Use
```
test.describe.serial()
```
for dependent tests
Use
```
generateTestUser()
```
for test data
Use established assertion patterns

Git Conventions:

Simple commit messages:
```
feat: description
```
,
```
fix: description
```
, etc.
No overly detailed commit messages
Use established branch naming patterns

🚨 IMPORTANT

This document (

CODING_STANDARDS.md

) is the single source of truth for this project. When in doubt, always refer to it. The standards document reflects the actual codebase and should be treated as the authoritative guide for all development decisions.

📚 Additional Context Files

```
README.md
```
- Project setup and running instructions
```
package.json
```
- Dependencies and scripts
```
tsconfig.json
```
- TypeScript configuration with path mapping
```
playwright.config.ts
```
- Test configuration

🎯 Key Guidelines

Read

CODING_STANDARDS.md

first

Follow all established patterns and conventions

Maintain consistency with existing codebase

Use the exact naming conventions, import patterns, and code structure defined in the standards

✅ Always use TypeScript path aliases (

@pages/*

@utils/*

, etc.)

✅ Always include

.js

extensions in imports

✅ Always follow the Page Object Model pattern established in the project

✅ Always use Faker.js for test data generation

✅ Always follow the established test structure and naming conventions

✅ Always use the exact import order and patterns shown in standards

pages/ - Page Object classes extending BasePage
tests/ - Test files using established patterns
utils/ - Helper functions and TypeScript types
constants/ - Application constants with `as const`
config/ - Configuration files
fixtures/ - Custom Playwright fixtures

Use custom fixtures from

@fixtures/pages.js

Follow test naming:

should [action] [expected result]

Use

test.describe.serial()

for dependent tests

Use

generateTestUser()

for test data

Use established assertion patterns

Simple commit messages:

feat: description

fix: description

, etc.

No overly detailed commit messages

Use established branch naming patterns

🤖 AI Assistant Instructions

🤖 AI Assistant Instructions

📋 Primary Reference Document

🎯 Key Guidelines

Before Writing Any Code:

Code Generation Rules:

File Structure to Follow:

Test Patterns to Use:

Git Conventions:

🚨 IMPORTANT

📚 Additional Context Files

Related Skills

Nano Banana Pro

Markdown Converter

1password

🤖 AI Assistant Instructions

📋 Primary Reference Document

🎯 Key Guidelines

Before Writing Any Code:

Code Generation Rules:

File Structure to Follow:

Test Patterns to Use:

Git Conventions:

🚨 IMPORTANT

📚 Additional Context Files