Your recruiter message may be AI-written. Who owns what happens next?

More and more of my LinkedIn inbox feels less like people reaching out and more like automated workflows adding me to a sequence.

A tween that plays once, a scroll story that is actually a film, and a shader that fully appears in one browser are three different engineering problems. Generating the page did not solve any of them.

If “build me a beautiful UI” were a complete brief, this series would be a shorter list. The miss these repositories target is small: the wrong easing, a phone layout that still behaves like a desktop site, a landing page any company could publish, a color described in words and never stored as a value.

“Make it premium” is a mood. A product needs a direction someone can point at, a review with a result, and sometimes a component that already exists.

Claude is not for you. It’s a tool for developers, by developers.

A customer onboarding form can look finished in a screenshot and still fail the person filling it out. The type is confident. The error does not say which field failed. On a phone, the label scrolls away from its input. Tab order never reaches submit. Visual polish did not make the form usable, and a usable layout did not make it accessible.

A coding agent that produces a working API endpoint has completed one step. The endpoint still needs a contract, input validation, tests, a review against a spec, monitoring before it goes live, and a rollback path if the rollout fails. Those are not optional extras. They are the difference between a prototype and production software.

A project’s authentication module imports a JWT library, is called by three API endpoints, and was designed to satisfy a decision recorded in an architecture decision record from fourteen months ago. None of those files mentions the others by name. Reading each one individually does not tell you how they connect. A knowledge graph can.

This is the post that weakens the series thesis. Humanizer is a writing-quality skill. Its primary users are not engineers reviewing pull requests. The honest response to that is to say so, and then explain what it actually offers.

Ask a coding agent to produce an architecture diagram and the default output is a collection of rounded boxes connected by arrows. Every node the same size, every connection the same weight, no hierarchy, no focal point—nothing a reader could not have inferred from a well-organized table. Diagram Design is a skill built around the premise that output quality is a design problem, not a rendering one.

The default behavior of a coding agent given a feature request is to start coding. Superpowers is a methodology that makes stopping and asking the first mandatory step. It is a plugin maintained by Prime Radiant that installs across Claude Code, Codex, Cursor, and most other major coding agents—and the skills trigger automatically.