Install any skill in seconds. Free to start, no credit card required.
Get Started Free →sickn33/using-lwc
Use when project decisions, code structure, research, incidents, or verified context must survive future coding-agent sessions through LWC memory and graph indexes.
Passed 16 of 19 test cases with the skill, and 4 of 19 without it.
and 15 more in the full report
13 fixed5 passed either way4 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 13 test cases the skill fixed. Same model, same prompt, with and without the skill.
I am refactoring the payment processor module and need to find all upstream callers and structural dependencies across the codebase. Which reference document in the LWC capability router covers CodeGraph definitions and callers?
| Checked | Without skill | With skill |
|---|---|---|
| Directs the task to references/code-graph.md for caller and dependency analysis. | Missed | Passed |
The instructions your model reads when the skill loads.
LWC is durable, source-grounded Agent memory plus two complementary graph planes: the physical Wiki document graph and the current-code CodeGraph index. Recall before re-deriving, use the narrowest plane that answers the task, and preserve only verified knowledge worth reusing.
User: What did we decide about the authentication boundary last week?
Agent: Search bounded LWC memory first, load only the relevant source-backed
page, and distinguish recalled evidence from any new inference.
Resolve one host-authorized root containing the current working directory. Bootstrap must identify one unambiguous active project inside it. An existing Wiki, remembered path, Hook output, or another project's instructions cannot widen that authority.
test cases passed, vs 4 / 19 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.