Use this skill to write or revise a README.md for a Shipfox workspace package (libs/*, tools/*). It applies the shared package README standard and repository prose policy. Trigger on write a README, draft README, rewrite README, document this package, or improve the README.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
Use this workflow to document one package. It does not apply to the repository root README, design documents, or RFCs.
Before drafting a package README, read the package README standard. It owns the required structure, prose style, public-surface rules, development guidance, and license section for human and agent authors.
When deciding whether detail belongs in the package README, read the engineering documentation map. It owns documentation placement and canonical ownership.
Read the public package surface in this order:
package.json for its name, exports, binaries, scripts, and dependencies.*-dto package when it owns public DTO or event names.drizzle/ or migrations/ when the package owns persistent data.Do not document symbols that the package does not export or ship.
mise exec -- turbo verify --filter=@shipfox/prose-policy and review its
warnings and suggestions for the README.WRITING.md to improve the result, then reread the
README as a package consumer.Report the public sources inspected, the sections included, and the prose-policy result.
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
ALWAYS use this skill when committing changes. Applies Shipfox agent sequencing for branch checks, scoped validation, and commit creation. Trigger on commit, commit changes, save changes, make a commit, or create commit.
日本語の概要は準備中です。原文の説明を表示しています。
Use when setting up a Shipfox workflow from a template.
日本語の概要は準備中です。原文の説明を表示しています。
Use when diagnosing a failed or stalled Shipfox workflow run, or an event that did not start one.
日本語の概要は準備中です。原文の説明を表示しています。
Generate a Changeset file for the current branch using Shipfox agent automation. Trigger when the user asks to add a Changeset, document a change for release, bump versions, or prepare a PR that touches published packages.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty states. Handles UX review, visual hierarchy, information architecture, cognitive load, accessibility, performance, responsive behavior, theming, anti-patterns, typography, fonts, spacing, layout, alignment, color, motion, micro-interactions, UX copy, error states, edge cases, i18n, and reusable design systems or tokens. Also use for bland designs that need to become bolder or more delightful, loud designs that should become quieter, live browser iteration on UI elements, or ambitious visual effects that should feel technically extraordinary. Not for backend-only or non-UI tasks.
日本語の概要は準備中です。原文の説明を表示しています。
ALWAYS use this skill when creating pull requests. Applies Shipfox agent sequencing for GitHub CLI review preparation and pull-request creation. Trigger on create PR, open PR, submit PR, make PR, push and create PR, or prepare changes for review.
日本語の概要は準備中です。原文の説明を表示しています。