# Craft, without another costume Canonical page: https://design.thorbis.com/research/bookmarks Curated by Chánh Đại: https://chanhdai.com/bookmarks Review date: 2026-09-06. All 26 curated entries on the bookmark page, not its navigation or every page behind each resource. Public text, code examples, and available syllabuses were reviewed. Interactive demonstrations were not independently exercised; paid lessons, downloads, and private libraries were not accessed. These are Thorbis applications and review exercises, not replacements for DESIGN.md, COMPONENTS.md, or the owning skill. Linear remains the operational baseline. External advice that conflicts with the constitution stays out. ## Coverage 26 entries accounted for: 16 public articles or references, 8 public previews, and 2 unavailable sources. Unavailable contents are not evidence for a promoted rule. Preview access does not include paid material. ## 1. shadcncraft Author: shadcncraft. Source: https://shadcncraft.com/ Review status: preview. Public product overview; commercial assets and downloads not reviewed. The offering connects React components, Figma assets, tokens, and agent-oriented resources. Its public presentation is useful for studying how a kit communicates implementation and design parity, not as evidence that every asset meets Thorbis requirements. **Thorbis application:** For a proposed component, record the upstream source, license review, token mapping, wrapper, states, and current adoption status together. A matching screenshot is not proof of matching behavior. **Not adopted:** No bulk import, new kit dependency, purchased asset redistribution, or claim of accessibility certification. ## 2. React Bits Pro Author: React Bits. Source: https://pro.reactbits.dev/ Review status: preview. Public catalog and product description; paid component source not reviewed. The catalog spans animated components, visual effects, page blocks, templates, and application interfaces. A large catalog offers reference directions; its existence does not establish a fit for a particular operational workflow. **Thorbis application:** Use an example only to formulate a specific Showcase hypothesis: what product behavior does this help explain? Evaluate a static alternative before proposing implementation. **Not adopted:** No shader, cursor effect, animated background, alternate app shell, or library adoption merely because it is available. ## 3. Copper Author: shadcn. Source: https://shadcn.com/copper Review status: public. Public product note; the native application was not installed. Copper describes a lightweight combination of capture, clipboard, and scratchpad for work across AI tools. Its own notes are local; that is a property of Copper, not a promise about other capture systems. **Thorbis application:** Keep inspiration intake focused on saving the reference and its context. Preserve the source URL, creator credit, and the reason it matters so the next review does not begin from an unexplained screenshot. **Not adopted:** Do not describe Thorbis Drop as local-only, change its authorization, or silently read the clipboard. ## 4. Invisible Details Author: Dmytro. Source: https://invisibledetails.com/ Review status: preview. Public landing page, syllabus, and visible examples; paid notes and practice not accessed. The public syllabus names predictability, states, feedback, forgiving input, memory, perceived speed, keyboard behavior, and wording. It treats small interaction decisions as something to investigate through practice. **Thorbis application:** Review an estimate form with incorrect input, a second submission, an interrupted request, and a return visit. Identify the exact moment a person could lose their place or misunderstand the result. **Not adopted:** No invented lesson summaries, copied paid exercises, or decorative polish substituted for error recovery. ## 5. Interactive SVG Animations Author: Nanda Syahrasyad. Source: https://www.svg.guide/ Review status: preview. Public course outline and page examples; paid lessons not accessed. The outline covers SVG coordinates, shapes, transforms and origins, path commands, and animation techniques. It also advertises masks, filters, and gradients; teaching a technique does not make that technique appropriate everywhere. **Thorbis application:** For a state glyph, keep a stable viewBox, a stable control footprint, and a meaningful accessible label. Route implementation through the existing icon and motion owners rather than a page-local illustration system. **Not adopted:** No ornamental filter, gradient, blur, or new animation engine in operational UI; no claim to have completed the course. ## 6. Design Engineer Principles Author: Vercel. Source: https://vercel.com/design/engineer Review status: public. Public principles page. The principles join usefulness, end-to-end ownership, constraints, inclusion, focused scope, and feedback. They explicitly include states, edge cases, language, documentation, and support in the experience a design engineer owns. **Thorbis application:** Frame a change around one trade task and its real constraint. The deliverable includes the difficult state, its explanation, and the evidence that the person can finish or recover. **Not adopted:** No screenshot-only acceptance, unlimited scope, or tool choice presented as an outcome. ## 7. Interfaces Author: Jakub Krehel. Source: https://interfaces.dev/ Review status: preview. Public magazine overview and examples; subscriber issues not accessed. The current site presents Interfaces as a design-engineering magazine, although the bookmark categorizes it as a course. Its public examples use typography, spacing, and small interface details to explain craft. **Thorbis application:** Keep source type and access scope accurate. Evaluate the separately linked public details article as evidence; do not imply that the entire subscription has been studied. **Not adopted:** No subscriber-content reconstruction or adoption of the magazine's visual identity. ## 8. Interface Craft Author: Josh Puckett. Source: https://www.interfacecraft.dev/ Review status: preview. Public library description; member collections and skills not accessed. The public page describes a working library of articles, examples, playgrounds, and references for deliberate interface craft. It emphasizes refining work rather than merely accumulating techniques. **Thorbis application:** Give each reference a concrete question and a small reconstruction exercise using Thorbis infrastructure. Record what changed in the result instead of collecting another unexplained link. **Not adopted:** No extraction of member skills, copying a separate design grammar, or generic instructions to make everything premium. ## 9. Making Software Author: Dan Hollick. Source: https://www.makingsoftware.com/ Review status: unavailable. Bookmark metadata verified; direct source returned HTTP 403 during this review. The requested book is identified by the bookmark, but its contents were not available to this review. No book-level findings are asserted. **Thorbis application:** Keep a follow-up reference only. Review an authorized public excerpt or supplied copy before extracting a claim. **Not adopted:** Do not substitute a different book with the same title or invent technical lessons from the title. ## 10. A Clock That Doesn't Snap Author: Ethan Niser. Source: https://ethanniser.dev/blog/a-clock-that-doesnt-snap/ Review status: unavailable. Bookmark metadata verified; the .dev address redirected to .com, which could not be retrieved. The article's implementation was not available to this review. The title alone does not establish its algorithm, timing model, or motion technique. **Thorbis application:** Retain the original URL and the retrieval limitation. Any future continuity example needs independently reviewed implementation evidence. **Not adopted:** No guessed rotation algorithm or attribution of an unverified technique to the author. ## 11. Details that make interfaces feel better Author: Jakub Krehel. Source: https://interfaces.dev/magazine/issues/details-that-make-interfaces-feel-better Review status: public. Public article and explanatory examples; interactive behavior not independently tested. The article discusses wrapping, concentric geometry, changing icons, tabular numerals, interruption, entrances and exits, optical alignment, and edge treatment. Some visual recommendations conflict with Thorbis's stricter surface rules. **Thorbis application:** Use stable numeric columns, purposeful wrapping, and optical inspection as review exercises. Test interrupted interactions in the approved primitive rather than only inspecting the resting frame. **Not adopted:** D-017 keeps real control rims. D-021 rejects ornamental blur. Do not stagger frequent work rows or replace Thorbis tokens with example values. ## 12. Component Architecture for React Server Components Author: Aurora Scharff. Source: https://aurorascharff.no/posts/component-architecture-for-react-server-components Review status: public. Public architecture article; examples were read, not executed in Thorbis. The article connects component boundaries to data ownership, parallel work, loading boundaries, and the order in which useful content appears. It is specifically about React Server Components, not a universal framework prescription. **Thorbis application:** Apply the ownership question to this Astro site: render useful document content on the server, keep optional interaction isolated, and reserve the geometry of asynchronous evidence. Evaluate the actual stack before choosing an implementation. **Not adopted:** No Next.js or RSC migration, framework-specific API transplant, or assumption that a skeleton alone fixes a waterfall. ## 13. Agents with Taste Author: Emil Kowalski. Source: https://emilkowal.ski/ui/agents-with-taste Review status: public. Public essay and example instructions; linked external skills not installed. The essay argues for expressing the reasons behind craft decisions as scoped instructions an agent can follow. Its numeric motion examples and blur advice are the author's choices, not Thorbis standards. **Thorbis application:** A review note names the defect, its owning rule, a permitted correction, and how to verify it. Feed the smallest owning skill instead of a large bundle of inconsistent taste instructions. **Not adopted:** No remote skill installation, copied timing constants, blur to hide defects, or agent-approved design exception. ## 14. React handbook Author: Rauno. Source: https://devouringdetails.com/resources/react-handbook Review status: public. Public handbook page; the separate paid manual was not accessed. The handbook discusses contextual names, derived behavior, explicit variants, compound composition, and choosing state boundaries deliberately. It also distinguishes high-frequency visual updates from ordinary component rendering. **Thorbis application:** Model request state explicitly and avoid independent booleans that permit contradictory states. Compose a transaction from approved trigger, body, and action primitives while leaving the domain operation outside the primitive. **Not adopted:** No arbitrary color escape hatch, unreviewed imperative DOM rewrite, or loss of keyboard and focus behavior while copying an example. ## 15. Devouring Details Author: Rauno. Source: https://devouringdetails.com/ Review status: preview. Public introduction and platform description; paid chapters and prototypes not accessed. The introduction describes a nonlinear interaction reference built around prototypes and learning through iteration. It distinguishes using and revisiting examples from passively following a course. **Thorbis application:** Pair a design reference with a task to try on the real device. Record what the interaction makes easier and where its behavior becomes unsuitable for field work. **Not adopted:** No reconstruction of paid chapters or claim that desktop interaction details automatically transfer to a phone. ## 16. Train Your Judgement Author: Emil Kowalski. Source: https://emilkowal.ski/ui/train-your-judgement Review status: public. Public exercise instructions and scenarios; comparison demos not independently exercised. The exercise asks readers to compare alternatives, make a choice, and explain it before reading the author's breakdown. Scenarios include frequency, interruption, scale, popovers, and layered motion. **Thorbis application:** Compare the current and proposed control under the same task, content, and input method. Write the reason for a preference before recording the final decision and repeat the test without motion. **Not adopted:** No claim that subjective preference is a measured conversion improvement, and no declaring a demo tested from its transcript. ## 17. Philosophy Author: Resend. Source: https://resend.com/philosophy Review status: public. Public philosophy page. Resend treats documentation as part of the product, reliability as a foundation, and predictable contracts and speed as ongoing work. Craft extends beyond an attractive interface to the behavior people rely on. **Thorbis application:** Keep visible guidance, downloaded skills, and machine-readable documentation aligned. Describe pending, failed, and confirmed results consistently instead of letting attractive feedback make a stronger promise than the system can keep. **Not adopted:** No invented uptime guarantee, backward-compatibility claim, or success state for an unconfirmed business outcome. ## 18. How we think about design Author: Resend. Source: https://resend.com/handbook/design/how-we-think-about-design Review status: public. Public handbook page, displaying an August 27, 2026 update. The handbook connects design to using the product, customer contact, support feedback, and work in the final medium. It treats the codebase, rather than detached design files, as the source of truth. **Thorbis application:** Use real trade vocabulary and representative records in the implementation. A repeated support problem becomes a focused change to a canonical component or pattern, with the relevant documentation changed alongside it. **Not adopted:** No untested Figma-only definition of done, fabricated customer research, or separate production grammar for a polished mockup. ## 19. 7 Principles of Rich Web Applications Author: Guillermo Rauch. Source: https://rauchg.com/2014/7-principles-of-rich-web-applications Review status: public. Public 2014 essay; historical implementation advice evaluated in context. The essay argues for useful pre-rendered content, immediate feedback, controlled data exchange, preserved history, and live updates. It explicitly distinguishes actions suitable for optimistic feedback from sensitive outcomes such as payments. **Thorbis application:** A payment may acknowledge submission immediately while remaining pending until confirmed. A list should preserve its place when a person opens a record and returns. Recovery must account for network failure. **Not adopted:** No blanket optimistic success, overwriting active drafts with pushed data, or transplanting historical SPDY and server-push advice into the current stack. ## 20. components.build Author: Hayden Bleasel and shadcn. Source: https://www.components.build/ Review status: public. Public specification overview and topic structure; not an audit of every implementation example. The specification organizes reusable components around composition, accessibility, tokens, state, types, documentation, and distribution. It presents a vocabulary for building components, not a requirement to adopt a particular kit. **Thorbis application:** Use the existing component contract as the place to connect purpose, state model, accessible behavior, source provenance, tokens, and usage examples. Adoption requires evidence beyond rendering the happy path. **Not adopted:** No second primitive library, unregistered component, or automatic claim that copied source is accessible. ## 21. animations.dev Author: Emil Kowalski. Source: https://animations.dev/ Review status: preview. Public course outline and descriptions; paid lessons, interviews, and skill files not accessed. The public outline connects motion techniques with iteration, orchestration, accessibility, and performance. Demonstration walkthroughs are described as a process of reasoning and refinement, not simply applying a preset. **Thorbis application:** A motion proposal includes its purpose, input method, frequency, interruption behavior, and nonanimated alternative. Use the existing Thorbis motion owner to choose implementation details. **Not adopted:** No copied paid skills, imported spring presets, or decoration made mandatory for completing work. ## 22. You Don't Need Animations Author: Emil Kowalski. Source: https://emilkowal.ski/ui/you-dont-need-animations Review status: public. Public essay and explanatory examples; interactive demos not independently tested. The essay evaluates animation by purpose and frequency. It separates an explanatory marketing sequence from repeated operational actions and argues against delayed keyboard-driven selection and recurring motion that gets in the way. **Thorbis application:** Keep command navigation and high-frequency dispatch selection immediate. A rare Showcase explanation can use motion only when it clarifies the product and has a useful static alternative. **Not adopted:** No routine row stagger, delayed keyboard highlight, recurring celebration, or copied duration that overrides a stricter Thorbis profile. ## 23. 7 Practical Animation Tips Author: Emil Kowalski. Source: https://emilkowal.ski/ui/7-practical-animation-tips Review status: public. Public article and code examples; examples were not run in Thorbis. The article connects immediate feedback, modest scale changes, tooltip timing, origin-aware motion, and interruption to an interface that stays connected to input. It supplies concrete examples rather than a universal motion system. **Thorbis application:** Test rapid open-close-open, movement across tooltip peers, and repeated activation. The state mark may change without moving the label or restarting from a disconnected visual position. **Not adopted:** No raw scale or duration values copied into feature code, and no blur used to conceal a broken transition. ## 24. Web Interface Guidelines Author: Vercel. Source: https://vercel.com/design/guidelines Review status: public. Public guideline document; external examples and libraries were not audited. The guidelines cover keyboard and focus behavior, input resilience, loading labels, URL state, recovery, motion, content, and performance. Some suggestions require reconciliation with stricter local requirements rather than literal copying. **Thorbis application:** Keep the original action label during loading, preserve input through hydration, allow paste and zoom, and provide visible focus and safe recovery. Verify the behavior in the Thorbis component, not merely its markup. **Not adopted:** Never disable zoom. Do not delay completed work to satisfy a suggested spinner duration or assume a loading primitive provides every timing guarantee automatically. ## 25. Developing Taste Author: Emil Kowalski. Source: https://emilkowal.ski/ui/developing-taste Review status: public. Public essay. The essay treats taste as a trained ability developed by exposure to strong work and by articulating why a particular choice succeeds. It distinguishes that practice from an unexplained personal preference. **Thorbis application:** Annotate inspiration with the problem, the useful decision, the Thorbis translation, and what will not transfer. Revisit the result after building it instead of treating a saved screenshot as an instruction. **Not adopted:** No copying a brand's costume, popularity as proof, or undirected requests to make a page feel premium. ## 26. Design Engineering at Vercel Author: Vercel. Source: https://vercel.com/blog/design-engineering-at-vercel Review status: public. Public team article; linked production examples not separately audited. The article describes collaboration across design, production code, performance, copy, and accessibility. It favors outcomes and continued refinement over a fixed toolset or a claim that the first release is perfect. **Thorbis application:** Scope a useful slice, review it in its actual medium, and turn repeated feedback into the system's defaults. Marketing experiments remain separate from operational workbench behavior. **Not adopted:** No shaders or 3D because another team uses them, no perfection claim, and no expansion of scope merely to demonstrate craft. ## Thorbis applications The following examples are original translations into Thorbis tasks. They reinforce existing owners and are not implementation or test-result claims. ### Make the task easier, not the screen busier Owning skill: [product](https://design.thorbis.com/skills/product). A feature can look complete while the dispatcher still has to reconstruct context or wait for unrelated content. Start from one person, interruption, and completed task. Keep the current job and its next action usable while optional evidence arrives. Treat the real constraint as part of the brief, not something polished away afterward. **Thorbis example:** For assigning a tech, show the job, relevant availability, and the consequence of the assignment. Do not make the dispatcher traverse a marketing-style sequence or a new shell to finish a routine task. **Verify:** Walk through the task with representative long and missing records. Check that the essential action remains understandable when optional content is slow or unavailable. Record the result rather than claiming a performance improvement without measurement. **Do not import:** No additional shell, feature hero, framework migration, or new dependency. Keep the approved surface role. Evidence: [Design Engineer Principles](https://vercel.com/design/engineer); [How we think about design](https://resend.com/handbook/design/how-we-think-about-design); [Component Architecture for React Server Components](https://aurorascharff.no/posts/component-architecture-for-react-server-components). [Source access limits](https://design.thorbis.com/research/bookmarks#application-product). ### Immediate acknowledgment is not confirmed success Owning skill: [resilience](https://design.thorbis.com/skills/resilience). A fast animation can falsely tell a person that money moved, a message arrived, or an assignment was saved. Distinguish initiation, pending work, confirmed outcome, failure, and uncertain outcome. Show what is known. A repeated request needs a deliberate recovery path, not a second untracked business action. **Thorbis example:** Collect payment keeps its label while the request is pending. A timeout says the result is not yet known and provides a way to check it; it does not invite an unconditional second charge. Confirmation names the actual result. **Verify:** Review pending, explicit rejection, timeout after submission, reconnect, and repeat activation. Confirm that copy does not claim settlement from mere request acceptance and that a recoverable draft is preserved. **Do not import:** No optimistic completion for consequential work, invented delivery guarantee, or success decoration that hides uncertainty. Evidence: [7 Principles of Rich Web Applications](https://rauchg.com/2014/7-principles-of-rich-web-applications); [Philosophy](https://resend.com/philosophy); [Web Interface Guidelines](https://vercel.com/design/guidelines). [Source access limits](https://design.thorbis.com/research/bookmarks#application-resilience). ### Preserve the place as the collection grows Owning skill: [ecosystem](https://design.thorbis.com/skills/ecosystem). Large customer, property, and inspiration collections become expensive to navigate when every inspection loses the current place. Treat filters, selected records, scroll, and Back behavior as part of the task. Loading a child or optional panel should not reset the whole collection. A saved reference includes enough context to be useful when revisited. **Thorbis example:** Open a property from a filtered customer list and return to the same filter and position. On the inspiration wall, reserve the media footprint and retain source credit even when the preview is unavailable. **Verify:** Try refresh, Back and Forward, a direct record link, an empty result, a failed preview, and a long collection. Check that late data does not overwrite a draft or move the action under the pointer. **Do not import:** No unbounded eager media, private information in shareable URLs, or a local-only storage promise borrowed from Copper. Evidence: [7 Principles of Rich Web Applications](https://rauchg.com/2014/7-principles-of-rich-web-applications); [Component Architecture for React Server Components](https://aurorascharff.no/posts/component-architecture-for-react-server-components); [Philosophy](https://resend.com/philosophy); [Copper](https://shadcn.com/copper). [Source access limits](https://design.thorbis.com/research/bookmarks#application-ecosystem). ### A control keeps its meaning through every state Owning skill: [ui](https://design.thorbis.com/skills/ui). A button that changes width, a field that loses input, or a dialog that loses focus breaks the task even when the resting design looks precise. Review the approved primitive as a sequence: resting, focused, activated, pending, resolved, and recovered. Keep the action label and footprint stable, associate errors with their fields, and preserve a visible keyboard path. **Thorbis example:** Save estimate remains Save estimate while its state mark changes. A validation error keeps the entered values, explains the repair beside the field, and moves focus only when the interaction calls for it. **Verify:** Test Tab, Shift-Tab, Enter, Escape where applicable, paste, invalid input, rapid activation, and a slow response. Repeat at 390px, in both themes, with zoom and reduced motion. **Do not import:** No hand-built duplicate primitive, hidden label, disabled browser zoom, or borrowed shadow-only outer edge that violates D-017. Evidence: [Web Interface Guidelines](https://vercel.com/design/guidelines); [Invisible Details](https://invisibledetails.com/); [components.build](https://www.components.build/); [Details that make interfaces feel better](https://interfaces.dev/magazine/issues/details-that-make-interfaces-feel-better). [Source access limits](https://design.thorbis.com/research/bookmarks#application-ui). ### Transfer the intent, not the desktop gesture Owning skill: [native](https://design.thorbis.com/skills/native). An interaction that works with a precise pointer or modifier key may be unusable for a tech holding a phone. Preserve the record and task while adapting the visible action path to the device. Use the existing native owner for target sizing, safe areas, focus, and host behavior; no critical action relies only on hover or a hidden gesture. **Thorbis example:** A field photo remains attached to the same job when the tech changes orientation or returns from another app. The visible capture action and retry path remain available without discovering a desktop shortcut. **Verify:** Check one-handed use, software keyboard opening, text enlargement, orientation, focus visibility, and reduced motion on the relevant device. Keep permission refusal and return-from-interruption states in the review. **Do not import:** No desktop hover contract on a phone, blocked zoom, silent clipboard access, or unverified claim that a web imitation is native behavior. Evidence: [Web Interface Guidelines](https://vercel.com/design/guidelines); [Design Engineer Principles](https://vercel.com/design/engineer); [Devouring Details](https://devouringdetails.com/). [Source access limits](https://design.thorbis.com/research/bookmarks#application-native). ### Motion explains the product; it does not become the product Owning skill: [cinematic](https://design.thorbis.com/skills/cinematic). An impressive effect can consume attention without helping a contractor understand what Thorbis does. Name the product idea a Showcase scene explains. Use representative trade content, keep the next action clear, and compare against a static explanation. Make animation optional to comprehension and task completion. **Thorbis example:** A single scene can explain how a completed job becomes an invoice. It should not hide the invoice behind a long sequence, invent product capabilities, or turn routine billing into a celebratory animation. **Verify:** Check the initial viewport, static and reduced-motion alternatives, readable copy, reserved media geometry, and the real cost of any proposed asset. Record license and dependency review before reuse. **Do not import:** No effect collection imported as a style system, no shaders in the workbench, and no made-up conversion or performance evidence. Evidence: [You Don't Need Animations](https://emilkowal.ski/ui/you-dont-need-animations); [React Bits Pro](https://pro.reactbits.dev/); [Design Engineering at Vercel](https://vercel.com/blog/design-engineering-at-vercel); [animations.dev](https://animations.dev/). [Source access limits](https://design.thorbis.com/research/bookmarks#application-cinematic). ### Frequent work stays immediate; allowed motion can be interrupted Owning skill: [motion](https://design.thorbis.com/skills/motion). A small delay repeated through a working day becomes friction, and a transition that restarts from the wrong position disconnects feedback from input. Apply the existing profile first: Workbench is press-only, Evidence has no motion, and other profiles remain constrained by their owner. Where a transition is already permitted, preserve continuity and the state footprint when input interrupts it. **Thorbis example:** Command-menu selection follows the key immediately. A permitted popover opens from its trigger and survives open-close-open without snapping, losing focus, or changing the action label. **Verify:** Repeat the interaction rapidly, switch between input methods, and test reduced motion. Compare with the nonanimated version at ordinary task speed. Use existing tokens rather than copying durations or curves from an article. **Do not import:** No row stagger in routine work, delayed keyboard highlights, ornamental blur, minimum success delay, or automatic spring-library adoption. Evidence: [You Don't Need Animations](https://emilkowal.ski/ui/you-dont-need-animations); [7 Practical Animation Tips](https://emilkowal.ski/ui/7-practical-animation-tips); [Train Your Judgement](https://emilkowal.ski/ui/train-your-judgement); [Details that make interfaces feel better](https://interfaces.dev/magazine/issues/details-that-make-interfaces-feel-better). [Source access limits](https://design.thorbis.com/research/bookmarks#application-motion). ### Use color to clarify state, not replace it Owning skill: [color](https://design.thorbis.com/skills/color). A borrowed visual trick can weaken contrast or make a state readable only by its color. Keep semantic roles and Thorbis tokens in charge. Inspect state words, marks, and control edges together in both themes. External suggestions for shadows, smoothing, and image outlines are evidence to evaluate, not a new palette. **Thorbis example:** A failed invoice action has an understandable error and a recovery action; it is not merely a red icon. A rounded input retains the real rim required by D-017 rather than losing its boundary on a similar-toned surface. **Verify:** Review focus, selected, disabled, pending, and error states in light, dark, and forced-colors conditions. Check contrast and meaning separately from whether the screenshot feels subtle. **Do not import:** No second accent, literal source colors, missing control rim, or ornamental gradient and blur imported from a reference. Evidence: [Web Interface Guidelines](https://vercel.com/design/guidelines); [Details that make interfaces feel better](https://interfaces.dev/magazine/issues/details-that-make-interfaces-feel-better); [components.build](https://www.components.build/). [Source access limits](https://design.thorbis.com/research/bookmarks#application-color). ### Keep operational text steady and unambiguous Owning skill: [type](https://design.thorbis.com/skills/type). Changing digits, shifting labels, and brittle wrapping make money and status harder to inspect. Evaluate numeric alignment where amounts are compared, stable action labels during requests, and wrapping with real content. Treat optical adjustments as controlled system decisions. Keep the existing font families and semantic type roles. **Thorbis example:** An invoice comparison aligns changing amounts without hiding their currency or precision. A long property name wraps without displacing the next action. Save remains the action; the adjacent status explains what happened. **Verify:** Try zero, negative and large amounts, long names, missing values, fallback fonts, text expansion, and browser zoom. Compare readability at actual size rather than approving a magnified specimen alone. **Do not import:** No blanket balanced wrapping on data rows, copied display face, custom page-local type scale, or status copy that claims more than the system knows. Evidence: [Details that make interfaces feel better](https://interfaces.dev/magazine/issues/details-that-make-interfaces-feel-better); [Web Interface Guidelines](https://vercel.com/design/guidelines); [Invisible Details](https://invisibledetails.com/). [Source access limits](https://design.thorbis.com/research/bookmarks#application-type). ### Make invalid combinations difficult to express Owning skill: [composition](https://design.thorbis.com/skills/composition). Independent loading, success, and error flags can contradict each other; presentation and business logic become tangled as a component grows. Choose an explicit state model and a semantic composition API. Reuse the approved primitives, keep domain operations outside them, and locate loading boundaries according to the work they protect. Documentation names which variants actually ship. **Thorbis example:** A payment dialog composes an approved trigger, content, fields, and actions around a domain-owned operation. The button receives one coherent request state, not several competing booleans and a private set of colors. **Verify:** Exercise each valid state and transition, keyboard and focus behavior, controlled and uncontrolled contracts where supported, server-rendered output, and slow or missing data. Check provenance and license before source adoption. **Do not import:** No arbitrary color escape hatch, duplicate component kit, unregistered dependency, or migration from Astro merely because a source uses RSC. Evidence: [React handbook](https://devouringdetails.com/resources/react-handbook); [components.build](https://www.components.build/); [Component Architecture for React Server Components](https://aurorascharff.no/posts/component-architecture-for-react-server-components); [shadcncraft](https://shadcncraft.com/). [Source access limits](https://design.thorbis.com/research/bookmarks#application-composition). ### Close the loop with evidence, not the word polished Owning skill: [tracking](https://design.thorbis.com/skills/tracking). Vague design requests produce repeated subjective revisions and hide which parts of the result were actually checked. A review records the person and task, the observed defect, the owning rule, the smallest correction, and its verification. Preserve source access limits. Turn repeated feedback into a better existing default rather than another detached instruction file. **Thorbis example:** Instead of make the button premium, record that its pending state moves the label, identify the UI owner, compare the corrected state under the same content, and attach the relevant checks and remaining uncertainty. **Verify:** Separate a source that was read from a demo that was exercised. Separate a passing content test from a browser check, and a committed branch from a deployed release. Report failed and skipped checks explicitly. **Do not import:** No fabricated research, inferred paid lesson content, unmeasured uplift claim, or declaring work live because a commit exists. Evidence: [Agents with Taste](https://emilkowal.ski/ui/agents-with-taste); [Train Your Judgement](https://emilkowal.ski/ui/train-your-judgement); [Developing Taste](https://emilkowal.ski/ui/developing-taste); [How we think about design](https://resend.com/handbook/design/how-we-think-about-design); [Design Engineer Principles](https://vercel.com/design/engineer). [Source access limits](https://design.thorbis.com/research/bookmarks#application-tracking).