Look twice
Read the actual words, the empty states, and the small labels before planning the flourish.
A software craft atelier
Make interfaces
with a hand
in the code.
Tavepuro is a working studio for people who want to build clear, considerate digital tools. We borrow the patience of a loom: choose the right thread, test the tension, and leave a useful edge for whoever works next.
The loom is not a metaphor for speed. It is a way to notice every crossing.
CURRENT BENCH
Thread status
HTML warp: open CSS weft: on bench JS shuttle: testing Product edge: in critique
01 / thread-picker
Four strands. Pull one forward.
A curriculum is not a queue of lessons. It is a set of threads you can return to when the work asks a different question.
01
curriculum strand
HTML: the structural warp
Start with document structure that can carry meaning before any decoration arrives. We work from landmarks, headings, labels, links, and content order—the dependable threads of an interface.
- 01Mark the page landmarks before choosing containers.
- 02Write one focused heading hierarchy for the task.
- 03Connect inputs, labels, instructions, and errors in plain markup.
02 / material tray
Learning habits with grain.
Tools matter, but habits decide whether they stay useful. These are the small, repeatable gestures we put in reach before a working session.
Cut kindly
Remove a step when it asks for more effort than the decision deserves.
Test the edge
Visit the narrow screen, the long name, and the keyboard before calling the piece finished.
Leave a note
Record the constraint and the choice so the next maker can pull the same thread.
03 / pattern-cutting studio
Bring the interface to a worktable.
Every table gives a vague software concern a practical shape. No result is promised; the point is to make the next experiment smaller and more legible.
Content cut
Turn a dense request into a page order that says what matters, who it is for, and what can wait.
State fitting
Lay out loading, empty, selected, error, and success states before the ideal path gets all the attention.
Responsive hem
Find the point where a component must reflow, not merely shrink, and give it room to breathe.
Handoff seam
Pair implementation notes with the question behind them so a product decision does not vanish in a ticket.
04 / weave-checker
Inspect a tiny interface problem.
Three quick choices for a fictional appointment page. There is no score, no profile, and no record beyond this browser tab—just a chance to notice the next useful thread.
Problem 1 of 3
A person lands on a repair appointment page. What belongs beside the first available time?
Choose a thread to see the reasoning.
Problem 2 of 3
The appointment form needs an address. Which label has the cleanest grain?
Choose a thread to see the reasoning.
Problem 3 of 3
A requested time is taken while the form is open. What is the calmest response?
Choose a thread to see the reasoning.
Check complete
The useful pattern is usually modest: name the situation, protect the person’s work, and make the next move visible.
05 / horizontal swatch wall
Practice patterns to pull across the bench.
Short exercises are not templates. Each is a prompt for noticing how a decision changes when the context changes.
20 minutesName the cards
Give a stack of blank controls labels that still make sense when they are separated from the visual design.
25 minutesChange the tension
Take one information panel and make it work for a narrow screen without hiding the important sentence.
15 minutesFind the seam
Mark the moment where a product requirement becomes an interface choice and write a note for a teammate.
30 minutesMake a state set
Sketch a before, during, and after state for one simple request without relying on vague status words.
35 minutesPin the order
Rearrange a task page until someone can tell what is happening before they decide what to do.
40 minutesTrade the pattern
Explain one small choice to a partner using the user situation, not only the component name.
06 / atelier critique slot
“
Bring a screen, a stubborn flow, or a question that keeps returning.
Critique at Tavepuro is a working conversation, not a verdict. We name the user situation, trace the path through the screen, and look for the one adjustment that would make the interface more honest or more useful. The piece stays yours; the discussion gives it a better next move.
Useful preparation: a screenshot or rough sketch, the job it needs to do, and one thing you are uncertain about.
07 / finish-and-fold board
Fold the practice into a small, complete piece.
These boards suggest a finish line without pretending the work is finished forever. Each ends with a useful artifact and a note about what should be checked next.
Project fold 01Service request page
Make a request flow with visible expectations, clear fields, and an acknowledgement that does not overpromise.
Project fold 02Personal workspace
Shape a calm dashboard around the few things someone needs to resume a task with confidence.
Project fold 03Decision record
Pair one interface pattern with a concise decision record that another maker can use and question.
08 / late-studio handoff
Leave the bench ready for tomorrow.
Late studio is for the small handoff that saves a future hour: a note beside the component, a question kept open, a test case named before the context fades. The craft is not only what appears on screen; it is what stays understandable after the room goes quiet.
Decision notesOpen questionsNext testNo urgency theatre
09 / studio FAQ
Questions at the door.
A little context about how the loom is meant to be used.
Tavepuro is presented as a studio practice rather than a fixed credential or a one-size-fits-all service. The material is organized around practical interface questions, and the tables, critique slot, and practice patterns can support individual study or a team’s internal conversation. Any working arrangement begins with a specific request and a shared understanding of what is useful.
A concise description is enough to start: who is trying to do what, where the current experience becomes uncertain, and what constraints are real. A link, screenshot, rough sketch, or sample wording can help, but polished materials are not required. It is especially useful to name the question you do not yet know how to ask, because that often reveals the right worktable.
The language is a way to slow down and inspect relationships. A web interface has structure, visible treatment, behavior, and an edge where it meets a wider product. Thinking in threads helps us see that a decision in one layer can change the tension in another. It does not replace technical precision; it gives the technical choices a memorable, human frame.
No. The weave-checker runs entirely in the page and keeps no score. The pattern request form provides a browser-only confirmation so you can test the interaction, but it does not transmit, store, or submit information. If you want to make contact, use the plainly marked email link in the footer or the Contact link in the header and include only the details you are comfortable sharing.
10 / pattern request
What needs a better seam?
Use this form to compose a draft request. It stays in your browser and displays a local acknowledgement only. For actual correspondence, use the normal unfilled Contact email link in the footer.