一键在 Manus 中运行任何 Skill

apple-store

星标4

分支1

更新时间2026年4月17日 10:04

Use when automating apple.com, configuring iPhones or other Apple products, navigating the Apple Store, adding items to bag, or writing tests for Apple Store flows. Covers site structure, purchase flows, bag behavior, and Apple-specific interaction patterns. Load live selectors from the browser; use the bundled reference only for site heuristics and flow guidance.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

lespaceman

lespaceman/athena-workflow-marketplace

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

Apple Store Automation Skill

This skill is a thin router. Use it together with agent-web-interface-guide for live browser work.

Workflow

Load agent-web-interface-guide before using browser MCP tools.
Read references/apple-store.md for Apple Store navigation, flow order, and bag heuristics.
Treat selectors in the reference as patterns, not guarantees. Derive the current eid and best live selector from the page with find, get_form, and get_element.
Re-check the page after each configuration step because Apple often enables downstream options only after prerequisites are selected.
Before any checkout or order placement step, confirm the final configuration and total.

同仓库更多 Skills

同仓库

capture-feature-evidence

lespaceman/athena-workflow-marketplace

Deeply explore a live app feature or a single mapped sub-feature and capture grounded evidence for downstream planning in `docs/qa/exploration-report.md` or a scoped file under `docs/qa/exploration/`. Use after the requested scope is already known, especially after `map-feature-scope` has identified bounded sub-features for a large feature. This skill owns observed product evidence and blockers for the scoped area; it does not perform feature decomposition, frame exploratory charters, prioritize risks, or write coverage plans.

2026-07-014

map-feature-scope

lespaceman/athena-workflow-marketplace

Quickly map a broad product feature into concrete sub-features before deep exploration begins. Use when a requested feature may span multiple routes, tabs, overlays, roles, or primary interactive surfaces and the agent needs to identify bounded exploration units, shared state, and blockers before spawning parallel browser subagents. This skill owns `docs/qa/feature-map.md`; it does not produce the final deep exploration evidence, coverage plan, or test specs.

2026-07-014

exploratory-test-writer

lespaceman/athena-workflow-marketplace

Define an exploratory testing charter: frame what to investigate, why it matters, and which risk hypotheses to test before or alongside the shared testing workflow. Triggers include "exploratory testing for...", "what should I investigate in this app", "help me think about what could go wrong", "risk hypotheses for...", "testing charter for...", "where should I probe deeper", or any request that needs structured thinking about test intent before coverage planning begins. This skill owns exploratory intent, risk framing, investigation order, and concrete follow-up asks for missing evidence; it does NOT own exploration evidence (capture-feature-evidence), final coverage prioritization (plan-test-coverage), or test case specs (generate-test-cases).

2026-07-014

add-playwright-tests

lespaceman/athena-workflow-marketplace

THE DEFAULT ENTRY POINT for the Playwright execution layer in the split testing suite. Use to add, create, or set up Playwright end-to-end tests for a feature, page, or application. It orchestrates the full Playwright workflow after shared exploration and planning: analyze the Playwright codebase, consume `docs/qa/feature-map.md`, `docs/qa/exploration-report.md`, `docs/qa/coverage-plan.md`, and `docs/qa/test-cases/*.md`, write production-grade test code, review it, and verify it with real execution. Delegates to `analyze-test-codebase`, `write-test-code`, `review-test-code`, and `fix-flaky-tests`, while relying on shared `map-feature-scope`, `capture-feature-evidence`, `plan-test-coverage`, `generate-test-cases`, and `review-test-cases`.

2026-07-014

analyze-test-codebase

lespaceman/athena-workflow-marketplace

Scans and reports on an existing Playwright test codebase. This skill should be used to inspect the current Playwright setup before writing, reviewing, or fixing tests, and should be loaded early when working in a new project to understand existing patterns. Covers: Playwright config, page objects, fixtures, helpers, auth/globalSetup patterns, test conventions, and directory structure. Triggers: "understand", "check", "show me", "inspect", or "analyze" the current test setup, config, infrastructure, patterns, or conventions. In the full add-tests workflow, this skill serves as an early read-only analysis sub-step before planning detailed coverage or writing code. This skill examines existing files and outputs a structured report. It does NOT write or fix tests, install Playwright, or explore live websites — for live-site exploration, use `capture-feature-evidence` so evidence is captured in `docs/qa/exploration-report.md`.

2026-07-014

review-test-code

lespaceman/athena-workflow-marketplace

Quality review of Playwright test code before final execution signoff. This skill should be used when implementation review of executable Playwright tests is needed, not for diagnosis of runtime flakiness. Triggers: "review test code", "review Playwright tests", "check test quality", "audit test implementation", "review my tests before merging", "check test code for issues", "review e2e tests", "code review Playwright", "are my tests stable", "check for brittle selectors", "review before running tests". Quality gate after write-test-code — catches brittle selectors, force:true misuse, networkidle overuse, Tailwind utility class selectors, exact numeric assertions, missing teardown, parallel-unsafe mutations, hardcoded data, missing assertions, test coupling, and convention divergence. Review-only — does NOT rewrite tests, does NOT run tests. Use fix-flaky-tests for fixing, write-test-code for rewriting.

2026-07-014

name	apple-store
description	Use when automating apple.com, configuring iPhones or other Apple products, navigating the Apple Store, adding items to bag, or writing tests for Apple Store flows. Covers site structure, purchase flows, bag behavior, and Apple-specific interaction patterns. Load live selectors from the browser; use the bundled reference only for site heuristics and flow guidance.
allowed-tools	null

Apple Store Automation Skill

This skill is a thin router. Use it together with agent-web-interface-guide for live browser work.

Workflow

Load agent-web-interface-guide before using browser MCP tools.
Read references/apple-store.md for Apple Store navigation, flow order, and bag heuristics.
Treat selectors in the reference as patterns, not guarantees. Derive the current eid and best live selector from the page with find, get_form, and get_element.
Re-check the page after each configuration step because Apple often enables downstream options only after prerequisites are selected.
Before any checkout or order placement step, confirm the final configuration and total.