UseCase implementation pattern — DI, Result handling, error types, decorators, CMS repositories, entry mappers, and schema-based permissions.
SkillScore96Maintained
Automatic
◆Coding pack
Last verified 8/12/2026
What it changes
Passed 23 of 24 test cases with the skill, and 6 of 24 without it.
Without skill25%
With skill96%
Checks it passed that the model alone missed
Retrieves successful result using result.value.
Uses isFail() method to check for result errors.
Checks execution failures using result.isFail().
and 26 more in the full report
18 fixed5 passed either way0 still failing1 broke
Pass-rate lift
+71 pp
Tokens
+108%
Agent turns
0%
Response time
-56%
Model gemini-3.6-flashMeasured 8/12/2026v223 of 24 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 18 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 18
Prompt
Before calling `UpdateInventoryUseCase` from another service, what step must a developer take regarding type definitions according to Webiny UseCase architectural standards?
What was checked, without and with the skill
Checked
Without skill
With skill
Reads the abstraction source file to verify method signatures and types.
Missed
Passed
case-22 · gemini-3.6-flash · 8/12/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md443 linessingle file
UseCase Pattern
What It Is
A UseCase is a single-method orchestrator that encapsulates one business operation (e.g., CreateTenantUseCase, PublishEntryUseCase). Each UseCase is a DI abstraction with an execute method that returns Result<T, E>.