scenario
Author or run cross-platform UI scenarios with selectors, screenshots, platform coverage and result reports.
- License 许可
- MIT
- 所属仓库
- 1aGh/maude
- 最近更新
- 2026-11-13
- Stars
- ★ 3
- Forks
- 0
01 前言 Front Matter
- name
- scenario
- hidden
- true
- description
- Author or run cross-platform UI scenarios with selectors, screenshots, platform coverage and result reports.
- allowed-tools
- Bash(agent-browser:*), Bash(agent-device:*), Bash(xcrun simctl:*), Bash(adb:*)
02 资源文件 15
- 参考文档_guide-00-overview.md521 B
- 参考文档_guide-01-repo-owned-scenario-guide-optional-overrides.md1014 B
- 参考文档_guide-02-platform-matrix.md1.3 KB
- 参考文档_guide-03-file-layout.md1.5 KB
- 参考文档_guide-04-step-shape.md763 B
- 参考文档_guide-05-infra-error-vs-product-fail-classification.md976 B
- 参考文档_guide-06-selectors-the-right-reach-order-proven.md1.2 KB
- 参考文档_guide-07-shareable-mobile-ux-scenario-body.md1.3 KB
- 参考文档_guide-08-parallelization-rule.md1.1 KB
- 参考文档_guide-09-phase-c-speed-levers-covers-manifest-skip-background-bo.md4.2 KB
- 参考文档_guide-10-running-an-existing-scenario.md2.2 KB
- 参考文档_guide-11-report-shape-deliverable.md2.3 KB
- 参考文档_guide-12-authoring-a-new-scenario.md1.5 KB
- 参考文档_guide-13-todo-not-yet-implemented.md1.3 KB
- 参考文档_guide-14-codebase-blockers-file-as-tickets-to-unblock-automation.md637 B
03 SKILL.md 正文
scenario
Follow host conventions for Claude Code or Codex.
Read any repo-owned scenario guide and resolve the platform matrix first. Preserve all requested platforms, stable selectors, screenshot proof and the report. Mark infrastructure errors separately from product failures; a skipped or unavailable platform is not a passing check. Use the run procedure for existing scenarios and authoring rules when creating one.
Read only the relevant procedure
The references below retain the complete procedure. Read the entry for the stage before performing it; conditional examples, setup and troubleshooting load only when needed. A staged workflow follows its applicable stages in order, including verification and close-out. References to another section mean the matching row here, not permission to skip that requirement. Do not read all references at once.
| When | Read |
|---|---|
| Initial orientation, prerequisites and scope | Overview |
| When performing this stage: Repo-owned scenario guide (optional overrides) | Repo-owned scenario guide (optional overrides) |
| When performing this stage: Platform matrix | Platform matrix |
| When performing this stage: File layout | File layout |
| When performing this stage: Step shape | Step shape |
| When performing this stage: Infra-error vs product-fail classification | Infra-error vs product-fail classification |
| When performing this stage: Selectors — the right reach order (proven) | Selectors — the right reach order (proven) |
| When performing this stage: Shareable mobile-UX scenario body | Shareable mobile-UX scenario body |
| When performing this stage: Parallelization rule | Parallelization rule |
| When performing this stage: Phase C speed levers — covers manifest, skip, background boot, web-only (DDR-061) | Phase C speed levers — covers manifest, skip, background boot, web-only (DDR-061) |
| When executing an existing scenario | Running an existing scenario |
| Before reporting results or handing off | Report shape (deliverable) |
| Before login, session reuse or authentication changes | Authoring a new scenario |
| When checking known limitations; not implemented behavior | TODO (not yet implemented) |
| When performing this stage: Codebase blockers (file as tickets to unblock automation) | Codebase blockers (file as tickets to unblock automation) |
04 同仓库更多 Skills
workflow-state
Read and update workflow state when planning, executing, completing, pausing or resuming project work.
ui-rules
UI hard-stop rules and audit method: WCAG 2.1 AA accessibility, responsive layout and motion.
testing-rules
Apply test quality rules during implementation and review: meaningful assertions, isolation and coverage.
security-rules
Apply application and AI security checks to code reviews, implementation and threat-driven validation.
question-protocol
Batch necessary questions from workflow participants, collect user answers and route them to the requester.
quality-gates
Resolve project quality commands, scoped checks, gate failures and validation fallbacks from workflow config.