菜单
Orchestrates complete iOS app design workflow from idea to implementation. Use when starting a new iOS feature, planning iOS app architecture, or need end-to-end iOS design process.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Run a model through the omni-bench benchmark to MEASURE it — produce a run-artifact and score it, then read the numbers. Use when asked to run, benchmark, measure, evaluate, or "test the results of" a model with omni-bench — ASR (WER/CER, RTFx) or text generation (tok/s, TTFT, prefill tok/s, prompt-cache speedup). Covers the adapter seam (Transcriber/Generator), the prepare→run→score→diff CLI flow, the offline no-download smoke task, and how to interpret each metric. NOT for publishing to a leaderboard (use omni-bench-publish) or changing the framework itself (use omni-bench).
Publish a scored omni-bench result (ASR or text-generation) to a leaderboard platform (e.g. bench.bshk.app) via its write API. Use when asked to publish, upload, submit, or "send a report" for an omni-bench result.json or parity-report.json — sharing ASR WER/RTFx numbers or text-generation TTFT/tok-per-s/prompt-cache numbers. Covers the one modality-agnostic `omni-bench publish` command and the MANDATORY secret handling: the api-key is injected from a secrets manager (1Password `op run` / AgentVault `av run`) at runtime, never read into context, never hardcoded.
Develop the omni-bench benchmark framework (ASR/STT + text generation) built on a producer/scorer split with an open JSON spec as SSOT. Use when working in an omni-bench checkout — changing the JSON schemas, the prepare/producer/scorer/diff pipeline, the adapter seams (Transcriber / Generator), datasets, fixtures, or the Swift producer SDK; or when running and validating benchmark artifacts. Encodes the schema-evolution rules, determinism invariants, commands, and repo gotchas that are easy to get wrong.
Use when generating/managing the offline root signing key or signing & publishing Zamok product keysets from the terminal (the Swift CLI; the ZamokApp GUI is the co-equal interface). Triggers — "generate root key", "rotate root", "publish keyset", "sign keyset", "escrow root key", "zamokctl", "trusted-roots.json", Tish/Zamok license signature setup.
Use when auditing websites or apps for Canadian accessibility law compliance, checking AODA (Ontario) or Accessible Canada Act (federal) requirements, or advising on CAN/ASC-EN 301 549 obligations.
Use when auditing digital products or services for European Accessibility Act (EAA) compliance, checking EN 301 549 conformance, or advising on EU Web Accessibility Directive obligations.
| name | ios-design-workflow |
| description | Orchestrates complete iOS app design workflow from idea to implementation. Use when starting a new iOS feature, planning iOS app architecture, or need end-to-end iOS design process. |
| version | 1.0.0 |
End-to-end orchestrator for iOS app design, from initial idea to GitHub/Gitea issues.
Invoke: superpowers:brainstorming
Explore the idea through collaborative dialogue:
Invoke: sc:research
Deep research on:
Invoke: sc:business-panel then sc:spec-panel
Create comprehensive specification:
Save to: docs/specs/{feature-name}-spec.md
Invoke: sc:workflow or sc:spawn
Break specification into actionable tasks:
Invoke: sc:design + ios-swiftui-generator
For each task:
Validate with: ios-design-review
Actions:
docs/ directoryUser: I want to build an iOS expense tracker app
Claude: [Invokes superpowers:brainstorming]
- What's the primary use case?
- Target audience?
- Key features needed?
...continues through all phases...
| Phase | Output |
|---|---|
| 1 | docs/plans/YYYY-MM-DD-{feature}-requirements.md |
| 2 | Research findings in conversation |
| 3 | docs/specs/{feature}-spec.md |
| 4 | Task breakdown with estimates |
| 5 | Architecture docs + code scaffolding |
| 6 | GitHub/Gitea issues created |
ios-swiftui-generator — Generate SwiftUI componentsios-design-review — Validate HIG complianceios-hig-reference — Apple HIG quick reference