AI SummaryWindsurf Rules for HttpScanner.com provides coding best practices and guidelines covering version control, clean architecture, database management, and CI/CD workflows using GitHub Actions. Developers using Windsurf IDE benefit from standardized development practices for HTTP scanning projects.
Install
Copy this and paste it into Claude Code, Cursor, or any AI assistant:
I want to add the "http-scanner — Windsurf Rules" prompt rules to my project. Repository: https://github.com/bartosz-io/http-scanner Please read the repo to find the rules/prompt file, then: 1. Download it to the correct location (.cursorrules, .windsurfrules, .github/prompts/, or project root — based on the file type) 2. If there's an existing rules file, merge the new rules in rather than overwriting 3. Confirm what was added
Description
Windsurf Rules for http-scanner
Guidelines for VERSION_CONTROL
GIT • Use conventional commits to create meaningful commit messages • Use feature branches with descriptive names following US-1-user-story • Write meaningful commit messages that explain why changes were made, not just what • Keep commits focused on single logical changes to facilitate code review and bisection • Use interactive rebase to clean up history before merging feature branches • Leverage git hooks to enforce code quality checks before commits and pushes GITHUB • Use pull request templates to standardize information provided for code reviews • Implement branch protection rules for master branch to enforce quality checks • Configure required status checks to prevent merging code that fails tests or linting • Use GitHub Actions for CI/CD workflows to automate testing and deployment • Implement CODEOWNERS files to automatically assign reviewers based on code paths • Use GitHub Projects for tracking work items and connecting them to code changes
Guidelines for ARCHITECTURE
CLEAN_ARCHITECTURE • Strictly separate code into layers: entities, use cases, interfaces, and frameworks • Ensure dependencies point inward, with inner layers having no knowledge of outer layers • Use interfaces (ports) and implementations (adapters) to isolate external dependencies • Create use cases that orchestrate entity interactions for specific business operations • Implement mappers to transform data between layers to maintain separation of concerns
Guidelines for SQL
POSTGRES • Use connection pooling to manage database connections efficiently • Use materialized views for complex, frequently accessed read-only data
Guidelines for CI_CD
GITHUB_ACTIONS • Check if package.json exists in project root and summarize key scripts • Check if .nvmrc exists in project root • Check if .env.example exists in project root to identify key env: variables • Always use terminal command: git branch -a | cat to verify whether we use main or master branch • Always use env: variables and secrets attached to jobs instead of global workflows • Always use npm ci for Node-based dependency setup • Extract common steps into composite actions in separate files • Once you're done, as a final step conduct the following: for each public action always use <tool>"Run Terminal"</tool> to see what is the most up-to-date version (use only major version) - extract tag_name from the response: • `bash curl -s https://api.github.com/repos/{owner}/{repo}/releases/latest `
Discussion
Health Signals
My Fox Den
Community Rating
Sign in to rate this booster
Works With
Any AI assistant that accepts custom rules or system prompts