Create speaker guide documents for AI Builders Meetup. Use when asked to create or generate a speaker guide, speaker 가이드, 스피커 가이드, or when preparing materials for meetup speakers. Ensures no essential sections are missed through a structured 3-phase workflow.
Creative writing skill for capturing story brainstorming. Use when the user is exploring narrative ideas, discussing characters, planning episodes, or thinking through story possibilities. Creates minimal working notes that preserve creative freedom by recording only what was stated and marking sources.
Capture learnings after tasks. Triggers on task completion, repeated mistakes, retrospective requests, or "what did I learn".
Apply structured, reflective problem-solving for complex tasks requiring multi-step analysis, revision capability, and hypothesis verification. Use for complex problem decomposition, adaptive planning, analysis needing course correction, problems with unclear scope, multi-step solutions, and hypothesis-driven work.
Deep market analysis that downloads an entire industry into your brain. Searches forums, Reddit, industry sites, events, and platforms to uncover pain points, language, opportunities, and the perfect software solution to sell them.
Creates detailed technical specifications for software projects covering requirements, architecture, APIs, and testing strategies. Use when planning features, documenting system design, or creating architecture decision records.
This skill conducts discovery conversations to understand user intent and agree on approach before taking action. It should be used when the user explicitly calls /interview, asks for recommendations, needs brainstorming, wants to clarify, or when the request could be misunderstood. Prevents building the wrong thing by uncovering WHY behind WHAT.
SEO keyword clustering with topic organization, content hub architecture, internal linking strategies. Use for content strategy, keyword research, pillar page structures, or encountering cluster organization, hub architecture, internal linking errors.
Write clear, unambiguous system requirements using the EARS (Easy Approach to Requirements Syntax) methodology. Use this skill when writing system requirements, creating technical specifications, validating requirements, or converting natural language to structured EARS format requirements for systems engineering, safety-critical systems, or formal specifications.
创建符合 CAC 评测系统规范的标准化测试题目。当用户需要添加新题目、创建测试题、或提到"创建题目"、"新建题目"、"添加题目"、"add question"、"create question"时使用此 Skill。支持代码、数理、逻辑、综合四类题库。
Format and validate Obsidian wiki links with proper filename, section, and folder conventions. Verify links exist before creation and fix broken links. Use when creating or checking wiki links in markdown files.
A technical writer who crafts clear, comprehensive documentation. Specializes in README files, API docs, architecture docs, and user guides.
Generate configuration reference documentation from conclaude-schema.json using src/bin/generate-docs.rs. USE WHEN the schema file changes, configuration options are added/modified, or documentation needs to be regenerated for the website.
Generates documentation for Terraform modules using terraform-docs tool to auto-generate README files with input/output tables, usage examples, and requirements. This skill should be used when users need to document Terraform modules, create or update README files, or maintain consistent module documentation.
引導文件結構、內容需求和專案文件最佳實踐。 使用時機：建立 README、文件、docs 目錄、專案設定、技術文件。 關鍵字：README, docs, documentation, CONTRIBUTING, CHANGELOG, ARCHITECTURE, API docs, 文件, 說明文件, 技術文件.
設計一致的錯誤碼，遵循 PREFIX_CATEGORY_NUMBER 格式。 使用時機：定義錯誤碼、建立錯誤處理、設計 API。 關鍵字：error code, error handling, error format, API errors, 錯誤碼, 錯誤處理。
将现有代码反向工程成 SDD 规格文档。 使用时机：分析旧有代码、为未文档化的系统撰写文档、从现有实作提取规格。 关键字：reverse engineering, legacy code, documentation, spec extraction, code archaeology, 反向工程, 旧有代码, 规格提取。
Generates API documentation from code including OpenAPI specs, JSDoc, and Python docstrings. Use when documenting APIs, REST endpoints, or library functions.
Reverse engineer existing code into SDD specification documents. Use when: analyzing legacy code, documenting undocumented systems, creating specs from existing implementations. Keywords: reverse engineering, legacy code, documentation, spec extraction, code archaeology, 反向工程, 舊有程式碼, 規格提取.
Guide documentation structure, content requirements, and project documentation best practices. Use when: creating README, documentation, docs folder, project setup, technical docs. Keywords: README, docs, documentation, CONTRIBUTING, CHANGELOG, ARCHITECTURE, API docs, 文件, 說明文件, 技術文件.
引導文件结构、内容需求和项目文件最佳实踐。 使用时机：建立 README、文件、docs 目录、项目设置、技術文件。 关鍵字：README, docs, documentation, CONTRIBUTING, CHANGELOG, ARCHITECTURE, API docs, 文件, 说明文件, 技術文件.
將現有程式碼反向工程成 SDD 規格文件。 使用時機：分析舊有程式碼、為未文件化的系統撰寫文件、從現有實作提取規格。 關鍵字：reverse engineering, legacy code, documentation, spec extraction, code archaeology, 反向工程, 舊有程式碼, 規格提取。
Design consistent error codes following the PREFIX_CATEGORY_NUMBER format. Use when: defining error codes, creating error handling, designing APIs. Keywords: error code, error handling, error format, API errors, 錯誤碼, 錯誤處理.
Your personal DSA & LeetCode mentor. Use for problem explanations, progressive hints, code reviews, mock interviews, pattern recognition, complexity analysis, and custom problem generation. Automatically adapts to your learning style and request type.
