القائمة
Create a new browser QA flow file from the template
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | qa-new-flow |
| description | Create a new browser QA flow file from the template |
You are creating a new browser QA flow spec in qa/browser-flows.
Args: $ARGUMENTS
If no args or --help is present, print usage and stop.
Usage:
/qa-new-flow --id=flow-id --title="Short title" --resources=assistant-settings,conversation-rules --goal="What it verifies"--parallel-safe=true --conflicts-with=other-flow-id,another-flow-id --preconditions="Signed in" --cleanup="Remove test rule"Steps:
id, title, resources).
id is a URL-safe slug (lowercase, numbers, dashes only) and matches the filename.qa/browser-flows/<id>.md using qa/browser-flows/_template.md as a base.parallel_safe, conflicts_with), include them in the front matter.
conflicts_with as a YAML list by splitting the --conflicts-with value on commas (even for a single id).--goal is provided, replace the Goal section placeholder with it.--preconditions is provided, replace the existing Preconditions section placeholder list with those items.--cleanup is provided, replace the Cleanup section placeholder with it.Do not overwrite an existing flow file without explicit confirmation.
Guidelines for testing the application with Vitest, including unit tests, integration tests (emulator), AI tests, and eval suites for LLM features
Cursor Cloud VM setup and service startup instructions for local development
Guidelines for implementing LLM (Language Model) functionality in the application
Simplify and refine recently modified code for clarity, consistency, and maintainability while preserving exact behavior. Use when asked to simplify, polish, refactor lightly, or clean up current-session changes before review or PR.
Commit changes and open a pull request with safe metadata
Review prompt and tool-description changes in a branch or PR. Use when asked to audit system prompts, prompt builders, tool descriptions, prompt inputs, or nearby evals/tests; summarize what changed; identify guidance that feels eval-shaped or too heavy for product use; and find repeated instructions between the main prompt and tool descriptions.