Loading...
Loading...
Found 1,410 Skills
Analyzes changes since last release and updates CHANGELOG.md ONLY. Does NOT trigger releases.
Use when changes are ready to ship and you need to communicate what changed, who it affects, and any required actions without exposing internal-only details.
MDX 语法预检查工具。**推荐**：先使用 eslint-mdx 和 prettier 进行基础检查， 再使用本 skill 进行 Fumadocs 特定问题的专项检查（图片文件名、翻译完整性）。 在 article-translator 翻译后、pnpm build 前使用。
Provides spec writing guidelines with 6 core areas and boundary system. Use when writing SPEC.md, defining requirements, creating project specifications, 요구사항 정의, or 스펙 작성.
Use this skill when you need to keep a repository's README.md file updated with project metadata, installation instructions, usage examples, and more. It automates synchronization by analyzing codebase patterns and dependencies.
Create or update repository README.md files with concise, human-skimmable structure and verified metadata. Use when writing or refreshing README content, adding or correcting badges, documenting stack and deployment/services, and explicitly reporting testing coverage (unit, integration, e2e api, e2e web) plus CI execution status.
Use when creating or developing, before writing code or implementation plans - refines rough ideas into fully-formed designs through collaborative questioning, alternative exploration, and incremental validation. Don't use during clear 'mechanical' processes
Create Astro/Starlight MDX content pages. Use when the user says "write a new article", "add a blog post", "create content in Tech/Life category", or "add an MDX page".
Close a PRD that is already implemented or no longer needed
Update PRD based on design decisions and strategic changes made during conversations
Systematic codebase investigation to extract architectural patterns and implementation details from an existing project, with findings persisted for long-term reuse. Use when the user wants to explore an open-source or existing codebase to understand how it works and inform the development of a new project. Triggers include: "explore this codebase", "investigate this repo", "how does X implement Y", "I want to build X, study how Y does it", "deep dive into this project", "understand how this works".
Use when capturing screenshots of local projects, documenting web app UI, taking screenshots of localhost dev servers, or generating images for READMEs and docs. Use when asked to "screenshot my app", "capture the UI", "take a screenshot of localhost", "generate screenshots for docs", "batch screenshot my pages", or "set up shot-scraper".