Menu

Make the agent cite the design-system component it reused, or admit it forked one
📰

Make the agent cite the design-system component it reused, or admit it forked one

DEV Community: frontend·Sherotree·3 days ago
#bIMyn6jQ
#devtofrontend#devto#dev#system#button
Reading 0:00
15s threshold

The PR adds a primary button. It looks like Button . It is a <button className="rounded-md bg-blue-600 px-4 py-2 text-white"> with a slightly different focus ring. The design system already has Button variant="primary" . The agent didn’t mention the fork.

I’ve started asking for a one-line citation in the PR body: which system component was reused, or an explicit “I didn’t use one, because….” Lookalike markup is not reuse.

Why forks sneak in

The agent wasn’t given the import path or the story URL

The system component’s API didn’t match the first prompt ( loading vs isPending )

The model “just needed a button” and patterned after a screenshot

A previous file in the repo already forked one, and the agent copied that

You cannot see the fork in the screenshot.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.