AD interaction-design-sop
Frontend interaction resilience & defense SOP for engineering implementation. Covers 7-step pre-coding interaction checklist: user intent & task friction reduction, P0/P1/P2 information hierarchy triage, 4-state resilience (empty, loading, error, destructive confirmation), perceived performance (optimistic UI, skeletons), power user shortcuts, and layout resilience trade-offs. Use when: implementing UI views/forms/dashboards in code, designing component interaction logic, handling edge cases and states, or conducting frontend UX resilience reviews. Keywords: 交互细节, 状态设计, 边界情况, 异常处理, 交互审查, 骨架屏, 乐观更新, 防错设计, interaction design, edge cases, error state, empty state, loading state, UI review, UI resilience.
Frontend interaction resilience & defense SOP for engineering implementation.
As a process D 48/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- 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: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 48/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 5 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 100Steps. 18 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1424 tokens
- medium 2 test cases, all positive: not one "should refuse" or "should ask first"
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
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +2Single-language instructions
- +3Description length 710: enough signal without eating the budget
- +4Structure: 9 headings
- +3Step-by-step instructions: 18 items
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 81.