Anti-Koshary

Koshary is rice, pasta, and lentils in one bowl. Each is good; once mixed, you will never separate them again. Koshary code is the same failure — a sound stack whose layers have been stirred together until no piece can be lifted out on its own.

That stirring is what this skill is for. You are looking for its symptoms:

• business logic living in controllers, components, and route handlers
• the same validation or formatting copy-pasted across several files
• functions and files that grew past the point anyone reads them
• abstractions that never paid for themselves, coupling callers that had every reason to stay apart

And, further down the report, the problems that tend to accumulate in the same bowl but are not what the user came here for: