Content
88%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A strong, highly actionable reference: executable examples for every protocol, a verified workflow with an error-recovery loop, and a thorough mistakes/checklist section. Its main weakness is token efficiency and file split — several sections (initializer patterns, EntityQuery variants, iOS 26 additions) duplicate or could defer to the existing reference files.
Suggestions
Trim the inline '@Parameter' initializer pattern list to the 2-3 most common forms and defer the rest to references/appintents-advanced.md, which already documents "all initializer variants" — this removes duplication and shortens the body.
Move the full code for EntityQuery variants 3-4 (EnumerableEntityQuery, UniqueAppEntityQuery) into a reference file, keeping only a one-line summary of when to use each variant in the main body.
Consider relocating the IntentValueQuery (Visual Intelligence) implementation detail to a reference, keeping the decision guidance (bounded results, no camera capture inside the query) inline since it drives design choices.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense with non-obvious API facts Claude cannot be assumed to know ("Optional parameters are not requested automatically", "keep SnippetIntent.perform() side-effect-free because the system may rerun it"), but it includes trimmable material: six inline @Parameter initializer patterns immediately followed by "See references/appintents-advanced.md for all initializer variants" (duplication), and the Int-vs-String AppEnum contrast restates mistake #4. Minor over-explanation that could be trimmed, matching the anchor-4 example rather than the lean anchor-5 example. | 4 / 5 |
Actionability | Every protocol gets complete, executable Swift code (AppIntent, AppEntity, all four EntityQuery variants, AppEnum, AppShortcutsProvider, SnippetIntent, IntentValueQuery), plus 11 concrete mistakes with fixes and a 14-item review checklist. The examples are copy-paste ready and cover the common cases, matching the top anchor. | 5 / 5 |
Workflow Clarity | The Triage Workflow sequences four steps with an explicit Step 4 verification list and a genuine feedback loop ("If a step fails, reset the fixture, fix the smallest intent/entity/query boundary, and rerun the same action from the same surface before adding another action"), reinforced by a review checklist — exactly the validate/fix/retry pattern of the anchor-5 example. | 5 / 5 |
Progressive Disclosure | Two real, one-level-deep references (references/appintents-advanced.md, references/system-surfaces.md) are clearly signaled at point of need with a TOC and References section, and the reference files link only to external docs (no nested local references). However, the ~430-line body inlines content that could be split out — all four EntityQuery variants with full code, the iOS 26 additions, and initializer patterns that duplicate the advanced reference — so structure is good with minor organization gaps rather than the anchor-5 "content appropriately split". | 4 / 5 |
Total | 18 / 20 Passed |