# Thorbis Resources and Skills > The files and focused agent skills used to build Thorbis interfaces. Canonical page: https://design.thorbis.com/resources ## Root files - [DESIGN.md](https://design.thorbis.com/design.md) — the visual and interaction constitution. - [AGENTS.md](https://design.thorbis.com/agents.md) — how an agent inspects, chooses, builds, and verifies. - [COMPONENTS.md](https://design.thorbis.com/components.md) — component selection, adoption status, composition, and verification. - [SKILLS.md](https://design.thorbis.com/skills.md) — the complete skill bundle. - [thorbis.zip](https://design.thorbis.com/thorbis.zip) — the downloadable kit. ## Skills - [Product](https://design.thorbis.com/skills/product): Inventing a page, a tool, or a canvas - [Resilience](https://design.thorbis.com/skills/resilience): Consequential workflows, integrations, migrations, or incidents - [Ecosystem](https://design.thorbis.com/skills/ecosystem): Large collections, discovery, deep records, relationships, or cross-device continuity - [UI](https://design.thorbis.com/skills/ui): Any screen - [Motion](https://design.thorbis.com/skills/motion): Animation - [Composition](https://design.thorbis.com/skills/composition): A component growing flags - [Tracking](https://design.thorbis.com/skills/tracking): Filing or closing work - [Color](https://design.thorbis.com/skills/color): Color, theme, or theory - [Type](https://design.thorbis.com/skills/type): Type or copy - [Cinematic](https://design.thorbis.com/skills/cinematic): Marketing, first-run, or a video - [Native](https://design.thorbis.com/skills/native): Phone, Android, desktop ## Applied bookmark research Reviewed 2026-09-06. 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. These worked examples are not a claim that the product behaviors have been implemented or verified. ### 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). ### 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). [All 26 sources and review limits](https://design.thorbis.com/research/bookmarks).