Loading...
Loading...
Found 88 Skills
Generate clear, professional, and polished Japanese technical articles suitable for corporate blogs, official documentation, and technical publications. Use this skill when the user wants to create enterprise-level content with consistent polite tone (です/ます), logical structure, and authoritative voice. Triggers include requests like "polished article", "professional tone", "enterprise blog", "公式ドキュメント", "プロフェッショナルな記事", or when content needs formal technical writing.
Expert in creating practical technical articles, skilled in conveying core knowledge points with concise language without missing any key information
Use when creating, updating, or generating README and documentation files for projects and libraries
Use for PLANNING documentation with phased analysis (4 phases), gap identification, and structured knowledge modeling. Best for documentation audits, completeness analysis, and documentation strategy planning. NOT for writing actual docs (use tasks-documentation instead).
Writing technical articles and blog posts. Use when creating articles in docs/articles/ or blog content explaining patterns, techniques, or lessons learned.
Write documentation, help articles, specs, and user-facing text in the authentic Grove voice. Use when writing any text that users will read, updating help center content, or drafting specs. Ensures warmth, clarity, and avoidance of AI patterns.
Prowler documentation style guide and writing standards. Trigger: When writing documentation for Prowler features, tutorials, or guides.
Research a specific system and create or update its blueprints/ documentation
Automatically search, crawl, and rewrite technical content to generate Chinese popular science articles suitable for WeChat Official Accounts. It covers AI large models, GitHub open-source tools, and technical topics. Use this when users say 'Write an article about XXX', 'Help me research XXX', or 'Generate an official account article'.
Generate or sync a "Living Specification" (docs/spec.md) from source code to eliminate doc-code drift. Use when creating, updating, or reviewing architecture documentation for a directory or module. Triggers on requests like "generate spec", "create spec.md", "sync documentation", "update architecture docs", "/spec.doc", or when asked to document a codebase directory.
Elite technical writer for product documentation, guides, and internal content. Use for writing new docs, reviewing drafts, restructuring content, creating templates, or improving clarity. Triggers on doc requests, MDX files, content structure questions, or writing style discussions.
Write READMEs for software projects. The skill should be used when writing or revising a README or README.md file.