AC ios-mac-app-dev
iOS/macOS 应用全生命周期开发技能包。覆盖从需求分析到上架发布的完整流程，包括：工程工作流（需求澄清、PRD生成、任务拆解、Swift TDD、Bug诊断、架构改进）、政策合规监控与动态学习、智能代码生成（Swift/SwiftUI/UIKit）、UI设计系统与美学规范（12大设计法则、631配色、8点网格）、多语言国际化（50+语言）、深色模式适配、架构模式库（MVVM/TCA/VIPER）、性能优化、无障碍、Apple Intelligence集成、App Store上架检查。 触发场景： - 用户问"在iOS/macOS做个App"、"帮我写个SwiftUI视图"、"创建Xcode项目" - 用户需要App Store上架检查、审核指南合规检查、出口合规声明 - 用户询问UI设计规范、配色方案、深色模式适配方案 - 用户需要国际化/本地化支持、多语言切换 - 用户需要代码生成、架构设计、性能优化建议 - 任何涉及Apple开发政策、审核指南、API废弃通知的问题 - 用户说"开发技能"、"应用开发skill"、"iOS开发"、"mac开发" - 用户说"需求分析"、"生成PRD"、"拆任务"、"TDD"、"诊断bug"、"架构改进"
iOS/macOS 应用全生命周期开发技能包。覆盖从需求分析到上架发布的完整流程，包括：工程工作流（需求澄清、PRD生成、任务拆解、Swift…
As a process C 53/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 20. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 53/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 100Tools and files. No external tools needed
- 100Steps. 28 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1170 tokens
- 100Running it twice. No mutating operations
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +5Description quotes 4 example trigger phrases
- +3Description length 532: enough signal without eating the budget
- +4Structure: 9 headings
- +3Step-by-step instructions: 28 items
- +4Has examples (2 code blocks)
- +4Reference files are cited in the instructions (16 of 16)
- +3All 2 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 84.