メニュー
Create, import, edit, or review posts for the official Flutter blog at flutter.dev/blog, including metadata, media, authors, and publication checks.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/flutter/website --skill contribute-blogコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
SKILL.md を表示中
Write or review clear, consistent, and accessible prose for Dart and Flutter developer documentation. Use for tutorials, API references, UI text, error messages, code comments, and terminology or style reviews.
Write or edit well-structured Markdown and MDX. Use for front matter, headings, lists, code fences, links, tables, other Markdown mechanics, and site-specific extensions. Pair with the write-technical-docs skill when changing prose.
Write, review, or refactor correct, idiomatic Dart code. Use for Dart source, packages, snippets, tests, public APIs, documentation examples, and modern language features. Pair with the write-flutter skill for Flutter-specific concerns.
| name | contribute-blog |
| description | Create, import, edit, or review posts for the official Flutter blog at flutter.dev/blog, including metadata, media, authors, and publication checks. |
Preserve the author's voice, intent, and requested scope. First person, contractions, anecdotes, humor, enthusiasm, and future-facing announcements can all be appropriate. Don't rewrite them merely to match documentation conventions.
Apply write-technical-docs and format-markdown selectively for clarity,
accuracy, accessibility, links, code formatting, and sound structure.
Their documentation-specific preferences aren't blanket blog requirements:
semantic line breaks and an 80-character limit aren't required,
especially when importing or lightly editing an existing post.
Fix or flag substantive issues with source fidelity, technical accuracy, accessibility, metadata, or rendering. Treat preference-only rewrites as suggestions unless copyediting was requested.
A small prose-only correction might need no reference.
Consult sites/www/content/blog/data.yaml,
sites/www/content/blog/authors.yaml, comparable recent posts,
or implementation source when a convention is unclear.
write-dart and write-flutter as relevant.
Validate complete examples when practical and
label intentional omissions or pseudocode clearly.TODO, TBD, or placeholder notes.
Report intentional markers or blockers instead of silently removing them.For a new post or a change to metadata or content, run the build and link-reference checks:
dart run dash_site --site=www build
dart run dash_site --site=www check-link-references
When layout, media, metadata, or content significantly changes, consider previewing the site locally:
dart run dash_site --site=www serve
For a prose-only edit that doesn't change links, direct inspection of the content can be enough.