Complete collection of AI agent skills including: - Frontend Development (Vue, React, Next.js, Three.js) - Backend Development (NestJS, FastAPI, Node.js) - Mobile Development (React Native, Expo) - Testing (E2E, frontend, webapp) - DevOps (GitHub Actions, CI/CD) - Marketing (SEO, copywriting, analytics) - Security (binary analysis, vulnerability scanning) - And many more... Synchronized from: https://skills.sh/ Co-Authored-By: Claude <noreply@anthropic.com>
3.2 KiB
3.2 KiB
Contributing to Playwright Skill
Thank you for considering contributing to the Playwright Skill plugin for Claude Code!
How to Contribute
Reporting Bugs
If you find a bug, please create an issue on GitHub with:
- Clear description of the problem
- Steps to reproduce
- Expected vs actual behavior
- Your environment (OS, Node version, Playwright version)
- Example code that demonstrates the issue
Suggesting Enhancements
Enhancement suggestions are welcome! Please:
- Check existing issues first to avoid duplicates
- Clearly describe the enhancement and its benefits
- Provide examples of how it would be used
Pull Requests
-
Fork the repository
git clone https://github.com/lackeyjb/playwright-skill.git cd playwright-skill -
Create a feature branch
git checkout -b feature/your-feature-name -
Make your changes
- Follow the existing code style
- Add tests if applicable
- Update documentation as needed
-
Test your changes
npm run setup # Test your changes with Claude Code -
Commit your changes
git add . git commit -m "feat: add your feature description" -
Push to your fork
git push origin feature/your-feature-name -
Create a Pull Request
- Go to the original repository
- Click "New Pull Request"
- Select your fork and branch
- Provide a clear description of your changes
Development Guidelines
Code Style
- Use clear, descriptive variable names
- Add comments for complex logic
- Keep functions focused on a single responsibility
- Follow existing patterns in the codebase
SKILL.md Guidelines
- Keep examples concise (8-15 lines)
- Always show
headless: falseby default - Include error handling in examples
- Add console.log statements for visibility
- Reference README.md for advanced topics
Commit Messages
Use conventional commits format:
feat:New featuresfix:Bug fixesdocs:Documentation changesrefactor:Code refactoringtest:Adding testschore:Maintenance tasks
Examples:
feat: add mobile device emulation helper
fix: resolve module resolution issue in run.js
docs: update installation instructions
File Structure
playwright-skill/
├── SKILL.md # Keep concise (~300 lines)
├── README.md # Full API reference
├── PLUGIN_README.md # Plugin distribution docs
├── run.js # Universal executor
├── package.json # Dependencies
├── plugin.json # Plugin metadata
└── lib/
└── helpers.js # Utility functions
Adding New Helpers
When adding functions to lib/helpers.js:
- Add clear JSDoc comments
- Include error handling
- Export the function
- Update SKILL.md to mention it
- Add example usage
Testing
Before submitting:
- Test with a fresh installation
- Verify examples in SKILL.md work
- Check that
run.jshandles edge cases - Ensure browser opens in visible mode by default
Questions?
Feel free to open an issue for discussion before starting work on major changes.
License
By contributing, you agree that your contributions will be licensed under the MIT License.