# Teach Vibely your way of building

> Turn playbooks and house style into reusable skills for your Vibely projects. Use the built-in design and build skills, or write your own or upload a SKILL.md.

Canonical: https://vibely.sh/skills
Last updated: 2026-11-18

Turn your playbooks, checklists and house style into reusable skills, so Vibely applies them automatically — in every project, every time.

[How the Vibely agent uses skills](https://vibely.sh/features/agent) · [Reuse another project with Add context](https://vibely.sh/features/add-context) · [Pair skills with connectors](https://vibely.sh/connectors)

## Expert output, every time

### The same result on the same kind of task

A skill tells Vibely exactly how you want a launch checklist run, a changelog written or a page reviewed — so the tenth time looks like the first.

### Capture what your team knows

Package your playbooks, review routines and house style once. Everyone in the workspace gets them in every project, from their first build.

### One skill, every project

Workspace skills apply across every web and mobile project in the workspace. No copying instructions into each chat.

### Loaded only when it matters

Vibely reads each skill’s description and pulls the full instructions in only when a task calls for it — keep many focused skills without slowing every message.

## How teams use skills

Vibely comes with built-in skills for design and build work. Add your team’s playbooks, or write your own from scratch.

### Built-in skills

Add built-in skills to your workspace from Customize — starting with design, with more on the way.

- Landing pages and dashboards that don’t read as templated, with the design skill
- Named art directions with real colour, type and layout values
- Your own skills from Customize load right beside the built-ins

### Workspace skills

Package your team’s way of working so every project follows it.

- Pre-ship launch checklists and release-readiness reviews
- Release notes, changelog entries and support replies in your format
- Tone of voice and formatting rules for one kind of content

### Your own shortcuts

Call a skill by name, or let Vibely pick it for you.

- Type /skill-name in the prompt box to use one on demand
- Add trigger phrases so a skill loads the moment you mention them
- Turn automatic use off for skills you only want when you ask

### Skills vs. knowledge

Knowledge is read on every message. Skills load only when a task calls for them. Here’s when to use which. [Read more](https://docs.vibely.sh/features/context/knowledge)

### Bring a skill from Claude

Vibely reads the same SKILL.md shape as Claude and other Agent Skills tools, so an existing skill file imports as-is. [Read more](https://docs.vibely.sh/features/context/skills)

## Create your own

### Write one in Vibely

Name it, say when it applies, and write the instructions in Markdown. It’s live across the workspace the moment you click Create.

### Upload a SKILL.md

Skills are Markdown with a little frontmatter. Add trigger phrases and Vibely loads the skill the moment you mention one. Skills from Claude import as they are. [Read the docs](https://docs.vibely.sh/features/context/skills)

```markdown
---
name: weekly-status-report
description: Use when asked for a status update,
  standup note, or weekly summary.
when_to_use: When the user asks what changed this
  week or wants a progress summary.
triggers:
  - "status report"
  - "weekly update"
  - "standup"
---

Summarize the last seven days of work in three
sections: wins, blockers, and next steps.

- Lead with shipped work, newest first
- One line per blocker, with an owner
- Next steps are verbs, not topics
```

## 64 built-in skills, added from Customize

- `/design` (Web) **Design**: Art direction for the whole app: eight named directions with real colour, type and layout values, real imagery, motion rules and a final slop check.
- `/frontend-design` (Web) **Frontend design**: A design lead’s process for redesigns and design-led pages: ground the look in the subject, plan and review before coding, and spend boldness in one place. Adapted from Anthropic’s open-source skill.
- `/accessibility` (Web) **Accessibility**: Audits and improves accessibility against WCAG 2.2: screen reader support, keyboard navigation and contrast.
- `/animate` (Web) **Animate**: Builds an animation from scratch, deciding in order whether it should move at all, then its purpose, tool, properties, curve, duration and exit.
- `/animation-performance` (Web) **Animation performance**: Keeps animations inside the frame budget: composite-only properties, motion off a busy main thread, and the cause when frames drop.
- `/animation-vocabulary` (Web) **Animation vocabulary**: Turns a vague description of a motion effect into its exact name, so you can ask for it precisely.
- `/apple-design` (Web) **Apple design**: Apple’s approach to interface design and fluid, physical motion, translated for the web.
- `/ask-sonner` (Web) **Sonner toasts**: A guide to Sonner, the React toast library: setup, the right toast() call, promise toasts, styling and the usual reasons toasts misbehave.
- `/baseline-ui` (Web) **Baseline UI**: A fast cleanup pass that fixes spacing, hierarchy, typography and small layout issues.
- `/better-accessibility` (Web) **Better accessibility**: Reviews and fixes keyboard and focus behaviour, ARIA, accessible names, forms, announcements, motion and zoom against WCAG 2.2.
- `/better-colors` (Web) **Better colours**: Builds and checks a colour system: palettes, semantic tokens, format conversion and contrast.
- `/better-interface` (Web) **Better interface**: One review across accessibility, layout, writing, typography, colour and UI polish, combining every better-* skill.
- `/better-layout` (Web) **Better layout**: Grouping, alignment, reading order and responsive structure, so a layout holds up when it is resized, translated or mirrored.
- `/better-typography` (Web) **Better typography**: Sets and reviews how text renders, from the type scale and spacing to font features, wrapping, truncation and punctuation.
- `/better-ui` (Web) **Better UI**: Polishes surfaces, icons and motion with exact values for radius, optical alignment, shadows, icon states and animation.
- `/better-writing` (Web) **Better writing**: Writes and reviews interface copy, from labels and errors to empty states and confirmations, in your product’s voice.
- `/break-ui` (Web) **Break UI**: Stress-tests a component with worst-case data — long names, missing fields, huge counts, emoji — and reports each break with its fix.
- `/copywriting` (Web) **Copywriting**: Writes and rewrites marketing copy for homepages, landing pages, pricing pages and feature pages.
- `/core-web-vitals` (Web) **Core Web Vitals**: Improves LCP, INP and CLS using field and lab evidence.
- `/dataviz-principles` (Web) **Dataviz principles**: Chart design decisions that hold in any tool: what to plot, which chart, what colour means, titles, layout and accessibility.
- `/design-taste-frontend` (Web) **Design taste (classic)**: The original single-file, dial-driven taste skill, kept for projects that depend on its exact behaviour. Runs only when called by name.
- `/emil-design-eng` (Web) **Design engineering**: Emil Kowalski’s approach to UI polish, component design, animation decisions and the invisible details that make software feel great.
- `/find-animation-opportunities` (Web) **Find animation opportunities**: Finds the places in a UI that should animate, rejects the ones that shouldn’t, and proposes motion with exact values. Read-only.
- `/fixing-accessibility` (Web) **Fixing accessibility**: Audits and fixes HTML accessibility: ARIA labels, keyboard navigation, focus management, colour contrast and form errors.
- `/fixing-motion-performance` (Web) **Fixing motion performance**: Audits and fixes animation jank: layout thrashing, compositor properties, scroll-linked motion and blur.
- `/hallmark` (Web) **Hallmark**: Anti-slop design for new pages, audits, redesigns and extracting a design from a URL or screenshot, with structural variety, not just visual.
- `/high-end-visual-design` (Web) **High-end visual design**: A classic style that runs only when called by name: a calm, polished look with soft contrast, generous whitespace and spring motion.
- `/impeccable` (Web) **Impeccable**: Designs, critiques, polishes and hardens a frontend interface, from hierarchy and layout to copy, accessibility and edge cases.
- `/improve-animations` (Web) **Improve animations**: Audits an app’s motion code and writes prioritised, self-contained plans to fix it. Read-only.
- `/improve-ui` (Web) **Improve UI**: Audits an existing surface against its own design evidence and writes implementation plans for the UI problems it verifies. Read-only.
- `/industrial-brutalist-ui` (Web) **Industrial brutalist UI**: A classic style that runs only when called by name: Swiss type, rigid grids, extreme scale contrast and utilitarian colour.
- `/interface-design` (Web) **Interface design**: Craft-first design for dashboards, admin panels, SaaS apps and tools: hierarchy, tokens, states and design-system consistency.
- `/interface-review` (Web) **Interface review**: Reviews a branch or change for the interface problems it introduced, across accessibility, layout, writing, typography, colour and UI.
- `/minimalist-ui` (Web) **Minimalist UI**: A classic style that runs only when called by name: editorial product UI with a warm monochrome palette, typographic contrast and flat bento grids.
- `/mobile-native` (Web) **Native feel on mobile**: The CSS and meta-tag fixes that make a web app feel installed on a phone: the 100vh bug, laggy taps, zooming inputs, the notch and more.
- `/motion-design` (Web) **Motion design**: Timing, easing, choreography and Disney’s animation principles adapted for UI, in whatever animation library you use.
- `/performance` (Web) **Performance**: Audits and speeds up page loading for a faster site and a better experience.
- `/pick-ui-library` (Web) **Pick a UI library**: Picks the right library for a frontend task from a curated, opinionated list. Runs only when called by name.
- `/prototype` (Web) **Prototype**: Builds several genuinely different versions of a UI piece behind a live picker, so you can flip through them and keep the best. Runs only when called by name.
- `/rams` (Web) **Rams**: A design engineer’s review of your code for WCAG 2.2 accessibility issues and visual design problems.
- `/review-animations` (Web) **Review animations**: Reviews motion code against a high craft bar drawn from Emil Kowalski’s design engineering. Approval is earned.
- `/router-core` (Web) **TanStack Router**: The core of TanStack Router: route trees, createRouter and createRoute, route matching and file naming conventions.
- `/seo` (Web) **SEO**: Improves search visibility: meta tags, structured data and sitemaps.
- `/shadcn` (Web) **shadcn/ui**: Adds, searches, fixes, styles and composes shadcn/ui components, with project context and component docs.
- `/start-core` (Web) **TanStack Start**: The core of TanStack Start: the Vite plugin, router factory, root document shell, client and server entries and configuration.
- `/stripe-best-practices` (Web) **Stripe best practices**: Stripe integration decisions: sandboxes, Checkout Sessions or PaymentIntents, Connect, subscriptions, tax and more.
- `/supabase` (Web) **Supabase**: Everything Supabase: database, auth, Edge Functions, Realtime, storage, the client libraries, RLS and migrations.
- `/supabase-postgres-best-practices` (Web) **Supabase Postgres best practices**: Postgres best practices maintained by Supabase: schema and column types, migrations, RLS policies, indexes, functions and jobs.
- `/ux-writing` (Web) **UX writing**: User-centred, accessible microcopy for buttons, labels, errors, notifications, forms, onboarding and empty states.
- `/vercel-composition-patterns` (Web) **React composition patterns**: React composition patterns that scale, from Vercel: compound components, render props and context providers, including React 19 changes.
- `/vercel-react-best-practices` (Web) **React best practices**: React and Next.js performance guidelines from Vercel Engineering for components, pages, data fetching and bundles.
- `/web-dataviz` (Web) **Web dataviz**: Interactive HTML visualisations with D3, ECharts or Observable Plot, from analytical charts to scrollytelling.
- `/web-design-guidelines` (Web) **Web interface guidelines**: Reviews UI code against Vercel’s Web Interface Guidelines: accessibility, focus, forms, animation, typography, performance and more.
- `/web-page-checklist` (Web) **Web page checklist**: The working checklist for a new page or app: which file each piece goes in, per-page search fields, avoiding hydration mismatches and the order to debug in.
- `/mobile-expo-animation` (Mobile) **Expo animation**: Builds animations in React Native and Expo with Reanimated, Gesture Handler and haptics, deciding the thread, properties and spring or timing in order.
- `/mobile-expo-data-fetching` (Mobile) **Expo data fetching**: Network requests in Expo: fetch, React Query, SWR, caching, offline support, loading and error states, and Expo Router loaders.
- `/mobile-expo-design-system` (Mobile) **Expo design system**: Builds and maintains a design system in an Expo app: tokens, component variants and when to extract a shared component.
- `/mobile-expo-native-ui` (Mobile) **Expo native UI**: Native-feeling Expo screens: Apple HIG styling, semantic colours, native controls, SF Symbols, visual effects and responsive layout.
- `/mobile-expo-router` (Mobile) **Expo Router**: Navigation with Expo Router: file-based and dynamic routes, native stacks and tabs, modals, sheets, headers and search bars.
- `/mobile-impeccable` (Mobile) **Impeccable**: Designs, critiques, polishes and hardens native iOS and Android screens, from hierarchy and layout to copy, accessibility and edge cases.
- `/mobile-react-native-best-practices` (Mobile) **React Native best practices**: React Native performance: frame rate, startup time, bundle size, memory leaks, re-renders and jank.
- `/mobile-supabase` (Mobile) **Supabase**: Everything Supabase for a mobile app: database, auth, Edge Functions, Realtime, storage, RLS and migrations.
- `/mobile-supabase-postgres-best-practices` (Mobile) **Supabase Postgres best practices**: Postgres best practices maintained by Supabase: schema and column types, migrations, RLS policies, indexes, functions and jobs.
- `/mobile-vercel-react-native-skills` (Mobile) **React Native skills**: React Native and Expo best practices from Vercel for fast apps: components, list performance, animations and native modules.

## More resources

- [Define reusable instructions with skills](https://docs.vibely.sh/features/context/skills) (Docs)
- [Knowledge: rules Vibely follows on every message](https://docs.vibely.sh/features/context/knowledge) (Docs)
- [Prompting best practices: get the build you pictured](https://docs.vibely.sh/prompting/best-practices) (Guide)
