Initializing Rules and Skills | Bondar Academy

Lesson Summary

This video lesson discusses how to manage and transfer custom rules and skills in a Playwright test automation project . The focus is on maintaining consistency across projects and avoiding manual copying of files. Key Concepts Source of Truth: Maintain a users directory as the ultimate source for rules and skills. Custom Skills: Create custom skills that initialize rules for each new project. Project-Level Rules: Keep rules at the project level to avoid context pollution in terminal sessions. Process Overview The lesson outlines the following steps for initializing rules in a new project: Check if the project has a package.json file. Create a cloud rules folder if it does not exist. Verify if the rule file already exists and handle accordingly (overwrite, skip, or update). Load the rule content from the users directory into the new project. Example Skills The instructor demonstrates initializing two skills: Playwright scripting Playwright architecture Each skill checks for the necessary conditions and creates corresponding rule files in the project. Future Lessons The next lesson will cover how to keep skills and rules up-to-date, ensuring that the users directory remains the latest source of truth. For practical application, the skills used in this lesson are available for download below the video.