Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →nwave-ai/nw-sar-critique-dimensions
Architecture quality critique dimensions for peer review. Load when performing architecture document reviews.
Passed 20 of 22 test cases with the skill, and 10 of 22 without it.
and 15 more in the full report
12 fixed8 passed either way0 still failing2 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 12 test cases the skill fixed. Same model, same prompt, with and without the skill.
In the YAML review output structure for `docs/product/architecture/brief.md`, what integer values are valid for the `iteration` key?
| Checked | Without skill | With skill |
|---|---|---|
| Restricts the iteration field to either 1 or 2. | Missed | Passed |
The instructions your model reads when the skill loads.
Pattern: tech chosen by preference, not requirements. Detection: ADR lacks comparison matrix, choice not mapped to requirements, justified only as "best practice." Severity: HIGH.
Pattern: complex/trendy tech without requirement justification. Examples: microservices for 3-person team, Kafka for 100 req/day, service mesh without complexity. Detection: complexity exceeds team size/requirements, tech adds resume value not solves problem. Severity: CRITICAL.
Pattern: unproven tech (<6 months, small community) for production. Detection: check maturity, community, LTS, fallback plan. Severity: HIGH.
ADR lacks business problem, technical constraints, or quality attribute requirements. Future maintainers cannot validate. Severity: HIGH.
No alternatives (min 2 required). Each must be evaluated against requirements with rejection rationale. Severity: HIGH.
Omits positive/negative consequences and trade-offs. Quality attribute impact not analyzed. Severity: MEDIUM.
Architecture doesn't address required attributes. Verify: performance (latency, throughput) | scalability | security (auth, data protection) | maintainability (modularity, testability) | reliability (fault tolerance, recovery) | observability (logging, monitoring, alerting). Severity: CRITICAL.
Performance requirements exist but no optimization strategy (caching, indexing, rate limiting, CDN). Severity: CRITICAL.
Requires expertise team lacks. Verify learning curve reasonable, training plan exists. Severity: HIGH.
Infrastructure costs exceed budget. Verify cost estimate exists and aligns. Severity: HIGH.
test cases passed, vs 10 / 22 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.