본문으로 건너뛰기
cccskills
무료GitHub에 공개

update-browser-support

Review Storybook's minimum supported browser versions using Plausible documentation traffic data. The skill presents usage evidence and proposed versions for approval, then updates pinned settings and documentation and opens a pull request with the recorded decision.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

원문원문 설명 보기

Recomputes Storybook browser support floors from Plausible /docs usage, writes pinned versions, and opens a PR. Use only when a human explicitly applies this skill.

설치 방법 보기

이럴 때 유용합니다

  • Review minimum browser versions using documentation traffic
  • Compare browser version shares and approve support floors
  • Update browser settings and migration documentation together
  • Create a pull request with evidence and approval records

포함된 파일(1)

  • SKILL.md4.5 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

Update browser support

Auth

Need PLAUSIBLE_API_KEY in the environment. How the operator supplies the key is up to them. Do not print the key.

Query

POST https://plausible.io/api/v2/query

  • site_id: storybook.js.org
  • date_range: "30d"
  • filters: [["contains", "event:page", ["/docs"]]]
  • dimensions: ["visit:browser", "visit:browser_version"]
  • metrics: ["visitors", "percentage"]
  • include: { "total_rows": true }

Save the request, resolved date range, retrieval time, and complete response. Fetch all pages before rolling versions. Use the same fixed date range for every request in the run.

Plausible's Stats API reference defines percentage as the percentage of total visitors in each category. With the query above, the denominator is all unique visitors matching the /docs page filter during the selected period, across all browsers and versions. It is not the total for one browser or the sum of the returned version rows. In each result row, metrics[0] is visitors and metrics[1] is percentage. Use metrics[1] as the share for an unrolled category. The 0.5% cutoff means percentage >= 0.5, not 0.005.

Also query metrics: ["visitors"] with no dimensions and the same site, date range, and page filter to record the denominator. Do not add browser filters to this denominator query.

Heuristic

  1. Roll Chrome / Edge / Firefox / Opera to major. Roll Safari to major.minor.
  2. Share is visitors / total /docs visitors × 100. For a rolled version containing multiple raw versions, query metrics: ["visitors"] with no dimensions, the same site/date/page filter, and additional is filters for that browser and its matching raw versions. Divide this unique-visitor count by the recorded denominator and multiply by 100 to get the rolled share. Do not sum unique-visitor counts or percentages across raw versions; a visitor can appear in more than one row.
  3. Drop any rolled version under 0.5%.
  4. Floor = oldest version in the current cluster, not an isolated older island that itself clears 0.5%.
  5. Omit Opera unless one Opera version is ≥ 0.5%. Drop UC Browser.

Companions: android / and_chr = Chrome floor. ios_saf = Safari floor. Leave Node unchanged.

Approve the selection

The heuristic does not define a numerical boundary between the current cluster and an older island. Do not infer that boundary silently or write new floors without explicit operator approval.

Present the saved query evidence and a table for each browser containing:

  • All rolled versions and their shares, including versions below the cutoff.
  • The exact versions proposed as the current cluster and any excluded older islands.
  • The candidate floor and its share of all /docs visitors.
  • The rationale for the cluster boundary and for including or omitting Opera.

Record the operator's approval, identity, date, and selected versions with the evidence in the PR. The floor is the oldest qualifying version in that approved cluster. If the operator disputes the boundary or the evidence cannot distinguish clusters, stop and ask the Technical Architect to resolve the selection semantics. Do not change the policy to break a tie. Reuse of the saved evidence and approval must yield the same floors.

Write

Pin explicit versions (do not leave a live query):

  • code/core/src/shared/constants/environments-support.ts — BROWSER_TARGETS (chromeN, edgeN, firefoxN, safariN.N, iosN.N; Opera only if kept)
  • code/package.json — browserslist
  • docs/get-started/install.mdx — public list and older-browser fallback guidance, scoped to the same Storybook versions as MIGRATION.md; preserve the preview-only limitations
  • MIGRATION.md — next major From version X.x to Y.0.0 section. Create that section at the top if it does not exist.

If browserslist cannot resolve the new pins, bump caniuse-lite (root resolutions + lockfile). The repo has a 7-day npm age gate.

PR

Branch from origin/next. Open a PR that targets next and follows .github/PULL_REQUEST_TEMPLATE.md. Add labels ci:normal, qa:skip, and BREAKING CHANGE.

In What I did, keep it short: before → after versions, and the share of /docs visitors for each chosen floor.

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

canary

무료

Find a trial Storybook package for a specific branch, or trigger its publication when needed. Check release progress and obtain the package reference or commands for creating or upgrading a project with that build.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Find a trial package for a Storybook branch
  • Publish a trial build for a fork pull request
  • Check publication progress and installation commands
storybookjs/storybook9.1만2026년 10월 18일 업데이트

Look up a project's existing UI components in Storybook, including their props, or configuration inputs, and usage examples. Use the findings to answer questions and identify components to reuse before building duplicates.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Find existing UI components
  • Check component props and usage examples
  • Answer questions about component usage
storybookjs/storybook9.1만2026년 10월 18일 업데이트

Review, improve, rewrite, or draft Storybook documentation in /docs. Assess each page’s purpose, audience, structure, and examples, then make suitable edits or provide a content plan, with formatting checks after changes.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Improve the structure and examples of a documentation page
  • Draft documentation for a new feature
  • Plan page types and outlines
storybookjs/storybook9.1만2026년 10월 18일 업데이트

Check out a GitHub pull request, fix linting and TypeScript errors, and commit and push the changes. The workflow supports forked pull requests and repeats type checks to verify fixes while keeping changes focused on these errors.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Fix linting errors in a pull request
  • Resolve TypeScript errors in a pull request
  • Apply fixes to a pull request from a fork
storybookjs/storybook9.1만2026년 10월 18일 업데이트

Organize GitHub issues and pull requests found during quality assurance testing. Apply release tracking labels, classify bugs by four severity levels, and label multiple findings while keeping documentation issues and feature requests outside the severity scheme.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Group QA findings by release
  • Classify bugs by severity
  • Apply labels to multiple issues and pull requests
storybookjs/storybook9.1만2026년 10월 18일 업데이트

Work through unresolved GitHub pull request reviews one at a time. The skill explains each comment, proposes a fix, asks how to proceed, and handles chosen edits, replies, commits, and thread resolution.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Addressing unresolved pull request review comments
  • Choosing between a code fix, a reply, or skipping a comment
  • Handling duplicate review comments together
storybookjs/storybook9.1만2026년 10월 18일 업데이트

storybookjs의 스킬 모두 보기

이 스킬의 문제 신고