Polish your UI by pointing at it.
The last round of polish is a list of small things: a gap too wide, a button out of line, a hover state missing. With Tencil you point at each one and say what should change, and your agent finds the code.
npx tencilSkip the hunt for the file
Describing a margin to an agent means describing where it is. Tencil hands over the component and source file of what you clicked, its markup and its size on screen, so "less space above this" is enough.
One pin per detail
Every pin is its own thread. Leave one on each thing that looks off and keep reviewing while the agent works; the inbox lists them by page.
See it, then follow up
Your dev server hot-reloads the change, so you judge it on the real page. Not quite right? Reply on the pin and the same thread continues.
Frequently asked questions
What to know before you start.
Yes: attach a screenshot to the pin. The agent gets it with the element context.
Your agent works in your repository, so it sees your components, tokens and Tailwind config like it does without Tencil.
More use cases
Tencil works the same everywhere: point at an element, say what should change.
- Copy editsSelect the words on your running app, type the new ones and your coding agent edits the right string, component or translation file.
- Visual bugsOverflowing text, a broken layout at one width, a misaligned icon: pin the bug on the element and your coding agent gets the markup, size and viewport to fix it.
- Design reviewWalk through a feature on your dev site, pin every change on the element it is about and let your coding agent work through them while you keep reviewing.