tonkotsuboy

content/posts/ に新しい記事ファイルを作成する。正しいフロントマターを付与し、Velite のスキーマに合わせた Markdown ファイルを生成する。

フルの品質チェックを実行する。CSS Module 型生成 → Velite コンテンツビルド → ESLint → Stylelint → Markuplint → Vitest の順に実行し、すべてパスすることを確認する。

Upload local images to a GitHub PR and embed them in the description or comments. Use when asked to "attach screenshots to PR", "add images to PR", "upload test results to PR", "embed screenshots in PR description", "add before/after images to PR", "attach UI screenshots", "show test results in PR", "add visual evidence to PR", or any request involving images and PRs. Always use this skill when the user wants to visually document changes in a pull request, even if they don't use the word "upload" — phrases like "put the screenshot in the PR" or "show the image in the PR" should trigger this skill. Prefers Chrome DevTools MCP (most stable) as the browser automation backend, falling back to Playwright MCP or agent-browser only when Chrome DevTools MCP is unavailable.

Analyze X (Twitter) posts for viral potential using the actual recommendation algorithm. Use when user wants to: (1) Check if a post will go viral, (2) Optimize a tweet for engagement, (3) Improve post performance. Triggers: "Check if this will go viral", "Make this post buzz", "Will this tweet perform well?", "Optimize my tweet", "How can I make this viral?", "バズるかチェックして", "Xでバズる投稿にして", "伸びるかチェックして", "この投稿を伸ばして", "投稿を改善して", "ツイートを最適化して"