Loading...
Loading...
Found 68 Skills
Tutorial patterns for documentation - learning-oriented guides that teach through guided doing
AI-powered comprehensive codebase documentation generator. Analyzes project structure, identifies architecture patterns, creates C4 model diagrams, and generates professional technical documentation. Use when users need to document codebases, understand software architecture, create technical specs, or generate developer guides. Supports all programming languages. Alternative to Litho/deepwiki-rs that uses Claude Code subscription without external API costs.
How-To guide patterns for documentation - task-oriented guides for users with specific goals
Explanation documentation patterns for understanding-oriented content - conceptual guides that explain why things work the way they do
Create comprehensive user guides, tutorials, how-to documentation, and step-by-step instructions with screenshots and examples. Use when writing user documentation, tutorials, or getting started guides.
Write comprehensive technical documentation including user guides, how-to articles, system architecture docs, onboarding materials, and knowledge base articles. Creates clear, structured documentation for technical and non-technical audiences. Use when users need technical writing, documentation, tutorials, or knowledge base content.
Generate a personalized learning document (FOR[yourname].md) that explains a project in plain, engaging Taiwan Traditional Chinese. Covers technical architecture, codebase structure, technologies, design decisions, and lessons learned. Use when user wants to understand a codebase deeply or create project documentation for learning purposes.
Behavior Guidelines for Information Visualization Presentation. Automatically activated when the model's response contains structured information such as comparisons, steps, configurations, architectures, etc., ensuring priority use of visual formats like tables, code blocks, lists, tree structures, instead of pure text accumulation. Trigger words: "Use a table", "Draw a diagram", "Make a list", "Structure it", "Don't just use text", "Visualize", "Compare". Even without trigger words, the rules of this Skill should take effect as long as the response contains structured information suitable for visualization. It also applies to scenarios such as "Too much text to read", "Can it be more intuitive?", "Organize into a table".
Write content that sounds natural, conversational, and authentically human - avoiding AI-generated patterns, corporate speak, and generic phrasing
Expert in documentation structure, cohesion, flow, audience targeting, and information architecture. Use PROACTIVELY for documentation quality issues, content organization, duplication, navigation problems, or readability concerns. Detects documentation anti-patterns and optimizes for user experience.
Reference documentation patterns for API and symbol documentation. Use when writing reference docs, API docs, parameter tables, or technical specifications. Triggers on reference docs, API reference, function reference, parameters table, symbol documentation.
Prowler documentation style guide and writing standards. Trigger: When writing documentation for Prowler features, tutorials, or guides.