I think that it's not a multiplier on skills.

It's a reducer of time.

For less experienced developers, it's an immediately reduction at the start of a project. But then they will almost certainly have problems later when their initial decisions come back to haunt them.

For senior devs, it's like having a junior or mid-level dev that will instantly do things within their capability, so long as it's explained to them well enough. This junior dev will do things fairly smartly, but any important decisions left to them will be wholly or subtly wrong. And the subtle ones are the worst ones, because they're so hard to detect.

But if that senior dev sets the guidelines well enough, and notices the problems, development is so, so, so much faster. It's wild.