improve improvers

Author: dsyme

workflows/daily-perf-improver.md

@@ -124,7 +124,7 @@ To decide which phase to perform:
 
 3. Create `.github/actions/daily-perf-improver/build-steps/action.yml` with validated build steps. Each step must log output to `build-steps.log` in repo root. Cross-check against existing CI/devcontainer configs.
 
-4. Create 1-5 performance engineering guides in `.github/copilot/instructions/` covering relevant areas (e.g., frontend performance, backend optimization, build performance, infrastructure scaling). Each guide should document:
+4. Create 1-5 performance engineering guides in `.github/copilot/instructions/` covering relevant areas (e.g., frontend performance, backend optimization, build performance, infrastructure scaling). Each guide should be maximum 500 words and should succinctly document practical, non-obvious, repo-specific details regarding:
   - Performance measurement strategies and tooling
   - Common bottlenecks and optimization techniques
   - Success metrics and testing approaches

workflows/pr-fix.md

@@ -46,14 +46,14 @@ You are an AI assistant specialized in fixing pull requests with failing CI chec
 
 4. Formulate a plan to follow the instructions. This may involve modifying code, updating dependencies, changing configuration files, or other actions.
 
-5. Implement the changes needed to follow the instructions.
+4. Implement the changes needed to follow the instructions.
 
-6. Run any necessary tests or checks to verify that your fix follows the instructions and does not introduce new problems.
+5. Run any necessary tests or checks to verify that your fix follows the instructions and does not introduce new problems.
 
-7. Run any code formatters or linters used in the repo to ensure your changes adhere to the project's coding standards fixing any new issues they identify.
+6. Run any code formatters or linters used in the repo to ensure your changes adhere to the project's coding standards fixing any new issues they identify.
 
-8. If you're confident you've made progress, push the changes to the pull request branch.
+7. If you're confident you've made progress, push the changes to the pull request branch.
 
-9. Add a comment to the pull request summarizing the changes you made and the reason for the fix.
+8. Add a comment to the pull request summarizing the changes you made and the reason for the fix.