post-anvil-feature
Generate a Twitter/X post highlighting a Anvil feature. Use when the user asks to write a tweet, create a Twitter post, or promote a AnvilCode feature on social media. The post always accompanies an attached video demonstrating the feature.
- License 许可
- Apache-2.0
- 所属仓库
- KaiavN/anvilcode
- 最近更新
- 2026-07-07
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- post-anvil-feature
- description
- Generate a Twitter/X post highlighting a Anvil feature. Use when the user asks to write a tweet, create a Twitter post, or promote a AnvilCode feature on social media. The post always accompanies an attached video demonstrating the feature.
02 资源文件 1
- 参考文档references/style-guide.md2.7 KB
03 SKILL.md 正文
Post AnvilCode Feature
Generate a punchy, developer-friendly Twitter/X post for a AnvilCode feature. The post always accompanies a video, so no need to describe every detail; the video does the showing.
Workflow
-
Understand the feature: use tools to read the relevant source code, docs, or changelogs. Answer:
- What does it do?
- When would a developer reach for it?
- What pain does it remove?
-
Craft the post: follow the constraints in
references/style-guide.md. -
Present for approval: show the post and ask if the user wants tweaks before finalizing.
Key Constraints
- 2-3 sentences max (fits ~280 chars).
- No filler phrases ("excited to announce", "game changer", "introducing").
- Always refer to the product as "AnvilCode", never "Anvil" alone.
- No em dashes anywhere in the post.
- Lead with the developer benefit or the problem solved, not the feature name.
- The video is attached. Do not say "watch the video" or describe what is in it.
- End with a relevant hashtag line (see style guide for approved tags).
Reference Files
references/style-guide.md: tone, vocabulary, approved hashtags, and example posts. Read this before drafting.
04 同仓库更多 Skills
github-pr-description
Generate and create pull request descriptions automatically using GitHub CLI. Use when the user asks to create a PR, generate a PR description, make a pull request, or submit changes for review. Analyzes git diff and commit history to create comprehensive, meaningful PR descriptions that explain what changed, why it matters, and how to test it.
execute-plan
Execute structured task plans with status tracking. Use when the user provides a plan file path in the format `plans/{current-date}-{task-name}-{version}.md` or explicitly asks you to execute a plan file.
create-skill
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends your capabilities with specialized knowledge, workflows, or tool integrations.
test-skill
A test skill with resources
minimal-skill
A minimal skill with no resources
write-release-notes
Generate engaging, high-energy release notes for a given version tag. Fetches the release from GitHub, retrieves every linked PR's title and description, then synthesizes all changes into a polished, user-facing release note with an enthusiastic tone. Use when the user asks to write, generate, or create release notes for a version (e.g. "write release notes for v1.32.0", "generate release notes for the latest release", "create changelog for v2.0").