メニュー
Use when preparing, reviewing, or suggesting git commit messages or pull request titles, or before creating a commit.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/baptisteArno/typebot.io --skill commitコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
SKILL.md を表示中
Use this skill when you need to write any frontend components. It explains project's UI best practices
Design and implement web animations that feel natural and purposeful. Use this skill proactively whenever the user asks questions about animations, motion, easing, timing, duration, springs, transitions, or animation performance. This includes questions about how to animate specific UI elements, which easing to use, animation best practices, or accessibility considerations for motion. Triggers on: easing, ease-out, ease-in, ease-in-out, cubic-bezier, bounce, spring physics, keyframes, transform, opacity, fade, slide, scale, hover effects, microinteractions, Framer Motion, React Spring, GSAP, CSS transitions, entrance/exit animations, page transitions, stagger, will-change, GPU acceleration, prefers-reduced-motion, modal/dropdown/tooltip/popover/drawer animations, gesture animations, drag interactions, button press feel, feels janky, make it smooth.
Use this skill when you need to update the AI models on the project.
SOC 職業分類に基づく
| name | commit |
| description | Use when preparing, reviewing, or suggesting git commit messages or pull request titles, or before creating a commit. |
Commit messages and PR titles must be prefixed with exactly one emoji that describes the primary intent of the change.
Prefer the most user-visible category when a commit spans multiple areas.
🐛 Fix a bug.✨ New user-facing feature. Use this only for a meaningful feature users would actively want to try. Use it sparingly. If the change is incremental rather than substantial, prefer 👌. Use only when there is a frontend change.👌 New user-facing addition to an existing feature, such as a new option or small capability. Use only when there is a frontend change.🔧 New internal implementation. Use when the change is mostly internal and not directly noticeable by end users.♻️ Refactoring. Use when behavior stays effectively the same and the main goal is code cleanup or restructuring.💅 UI or UX update. Use when the main value is visual polish, interaction quality, or layout improvements.📝 Blog or documentation update.Always check the diff and remove debug logs, temporary files, commented-out experiments, and other temporary artifacts before creating a commit.
Never amend commits that are already part of an opened PR. Push follow-up fixes as new commits so review history and existing comments remain stable.
Use a concise imperative or descriptive title after the emoji:
🐛 Fix workspace invite redirect
🔧 Add billing sync worker
♻️ Simplify block schema helpers