Taster

진단부품톤 고르기
부품 갤러리 / Button

Button

Primary actions are a solid fill in the accent token, secondary is an outline, tertiary is plain text. No glow, no gradient, no ghost primary. Grouped actions share one border.

내 사이트에서 가져오기

색을 고르면 아래 부품이 그 색으로 바뀝니다.

실제로 돌아가는 부품입니다. 눌러 보고 입력해 보세요.

내 앱에 넣기

  1. 아직 npm 패키지가 없어서 Taster 리포를 받아 그 안의 명령을 씁니다. 내 앱 폴더가 들어 있는 폴더에서 한 번만 받습니다.

    git clone https://github.com/makim-414/taster.git && npm ci --prefix taster/packages/engine
  2. 내 앱 폴더에서 이 부품을 넣습니다. 부품 파일과 토큰 파일이 src/components/taster 에 들어갑니다.

    node ../taster/packages/engine/cli.mjs add blocks/button --from https://taster-six.vercel.app --dir src/components/taster
  3. 부품은 Tailwind 클래스로 그리고, Taster 프리셋이 그 클래스를 토큰에 연결합니다. Tailwind CSS 를 설치하고, tokens.css 를 앱 루트에서 한 번 불러온 뒤, 앱 루트에 이 설정을 둡니다. 프리셋이 없으면 빌드는 되어도 부품이 스타일 없이 나옵니다.

    // tailwind.config.cjs
    module.exports = {
      presets: [require('./src/components/taster/tailwind-preset.cjs')],
      content: ['./index.html', './src/**/*.{ts,tsx}'],
    };

    Tailwind v3 는 이 파일을 그대로 읽습니다. v4 는 Tailwind 를 불러오는 src/ 의 스타일시트 맨 위에 이 두 줄을 넣습니다.

    @import "tailwindcss";
    @config "../tailwind.config.cjs";

    tokens.css 는 :root 에 --bg, --text, --border, --accent 를 정의합니다. 내 앱의 스타일시트가 같은 이름을 뒤에서 다시 정의하면 그쪽 색이 이깁니다. 새 Vite 앱의 스타터 CSS 처럼 그런 변수가 있으면 지우거나 이름을 바꾸세요.

언제 쓰나요

  • Flat solid buttonPrimary actions are a solid fill in the accent token, secondary is an outline, tertiary is plain text. No glow, no gradient, no ghost primary. Grouped actions share one border.
  • Asymmetric product heroLeft-weighted headline and a short sentence next to a real product screen or the actual result a visitor came for, instead of a centered title floating over a gradient.
  • Photo-led heroReal photography carries the hero: a full-bleed photo with a gentle bottom scrim, or a serif headline over two or three overlapping photos. Film grain and slightly muted tone replace the glossy AI photo look.
  • In-hero form flowThe first action is an input inside the hero, such as a link to analyze. Submitting slides the hero into a short form or a sample result on the same screen, so the page needs no heavy contact form further down.
  • Site headerTransparent at the top, solid hairline bar after scrolling, labels in normal case. Optional mega menu with text-led items and one short description each, or a minimal wordmark and one action for single-purpose pages.
  • Neutral call to action bandA flat band on a neutral surface with one sentence, one primary and at most one secondary button. No radial glow or gradient box.
  • Closing contact linkEnd the page with a single button that links to contact, or opens a short dialog, and put the mail link in the footer. No long inquiry form in the body.
  • Plan cardsOne card per real plan with aligned slots for name, price, billing note and features. A monthly or yearly toggle updates every price. Recommended is a text label and a stronger border, not a scaled center card.
  • Specific action labelButton text names the result in the page language, for example a request for a quote, not a generic English phrase on a Korean page.
  • Onboarding wizardA short multi-step flow with back, progress and one question per screen, optionally with a spotlight tour that lights one area at a time.
  • Lead capture formOne email field and one button when a real list exists, or at most three fields with labels in normal case and one clear submit button. Never on every page ending.
  • Sign in formEmail and password fields with an optional provider button and a strength meter on sign up.
  • Error and locked stateA plain message for failure, missing permission or a locked feature with the reason, what to do and a retry or request button.
  • Editorial storefront homeA single still hero, category entries as worlds, best-seller rails with a four by five product grid and a consultation entry, in a light editorial tone.
  • Agent chat thread and composerOperator messages as bubbles, agent replies as plain text, tool steps and approval cards inline, jump to latest, and an input that grows with text with slash commands and send or stop.
  • Ask-human stepThe agent pauses with choices, a free-text field and a pager, or a review queue of keep or remove buttons.
  • Language playground in the site shellKeep the landing header, page column and light page on the playground of a language or developer tool site; make only the code card dark, let the code fill it and open the output under the code on the first Run.

대신 없애 주는 AI 티

  • Ghost button as the main call to action (AC-16)
  • Purple gradient (COL-01)
  • Large colored glow shadow (COL-07)
  • Touch target under 44px (RSP-06)
  • Drawn mockup instead of the real thing (AC-17)
  • Row of three big stats (CMP-06)
  • Fake terminal hero (CMP-07)
  • The centered hero formula (LAY-01)
  • Generated photo look (AC-19)
  • Aurora or mesh blob background (BG-01)
  • Near-black background with a neon glow (COL-03)
  • Heavy contact form in the middle of a landing page (AC-12)
  • A subscribe form at the end of every page (CMP-10)
  • All-caps label with wide letter spacing (AC-01)
  • Glass panels everywhere (CMP-05)
  • The same few stock icons on repeat (ICO-01)
  • Every gap is the same (LAY-06)
  • Same large radius and same soft shadow on everything (CMP-04)
  • Tinted pill badge (AC-04)
  • Flat gray card with a hairline border, everywhere (AC-14)
  • Three pricing tiers with the middle one raised (CMP-09)
  • Generated copy voice (CPY-01)
  • English button labels on a Korean page (KO-09)
  • Machine codes on screen (CPY-03)
  • The predictable section order (LAY-04)

정보

설치할 패키지
tailwindcss
라이선스
MIT
출처
shadcn/ui, MIT, https://ui.shadcn.com
코드 보기
import * as React from 'react'
import { cn } from './_cn'

// Button with solid, secondary, outline, ghost and destructive variants.
// API follows the shadcn/ui button (MIT). The solid variant uses the accent token so a theme can recolor it.
// Upstream license: MIT, Copyright (c) 2023 shadcn. Full text in THIRD_PARTY_NOTICES.md.

export type ButtonVariant = 'solid' | 'secondary' | 'outline' | 'ghost' | 'destructive'
export type ButtonSize = 'sm' | 'md' | 'lg'

export interface ButtonProps extends React.ButtonHTMLAttributes<HTMLButtonElement> {
  variant?: ButtonVariant
  size?: ButtonSize
}

const VARIANT: Record<ButtonVariant, string> = {
  solid: 'bg-accent text-accent-fg border border-transparent hover:opacity-90',
  secondary: 'bg-bg-elev text-text border border-border hover:border-text-subtle',
  outline: 'bg-transparent text-text border border-border hover:border-text-subtle',
  ghost: 'bg-transparent text-text-muted border border-transparent hover:text-text hover:bg-bg-elev',
  destructive: 'bg-transparent text-danger border border-border hover:border-danger',
}

const SIZE: Record<ButtonSize, string> = {
  sm: 'h-11 desk:h-8 px-3 text-sm rounded-md',
  md: 'h-11 desk:h-9 px-4 text-sm rounded-md',
  lg: 'h-11 px-6 text-title rounded-md',
}

export const Button = React.forwardRef<HTMLButtonElement, ButtonProps>(
  ({ variant = 'solid', size = 'md', className, ...props }, ref) => (
    <button
      ref={ref}
      className={cn(
        'inline-flex items-center justify-center gap-2 font-medium tracking-[-0.01em] outline-none',
        'transition-[colors,transform] duration-press ease-out active:scale-press',
        'focus-visible:ring-2 focus-visible:ring-ring disabled:opacity-50 disabled:pointer-events-none',
        VARIANT[variant],
        SIZE[size],
        className,
      )}
      {...props}
    />
  ),
)
Button.displayName = 'Button'