Documentation

Content Collections TypeScript-first build tool for Markdown/MDX content. Use for blogs, docs, content sites with Vite + React, MDX components, type-safe Zod schemas, Contentlayer migration, or encountering TypeScript import errors, path alias issues, collection validation errors.

Creates professional API documentation using OpenAPI specifications with endpoints, authentication, and interactive examples. Use when documenting REST APIs, creating SDK references, or building developer portals.

Use when asked to document architecture, understand system structure, create diagrams, or analyze component relationships. Focuses on interfaces and high-level design. Triggers on: "use architecture mode", "architecture", "system design", "how is this structured", "document the system", "create a diagram", "high-level overview", "component diagram". Read-only mode for analysis, can create documentation files.

Comprehensive skill for Product Managers to create organize and manage Product Teams, Strategy, PRDs, release plans, user stories, and standalone issues with high-quality acceptance criteria. Supports both full documentation workflows (PRD → Plan → Stories) and quick issue creation (standalone stories, tasks, bugs). All documentation follows design-driven development principles with functional, testable acceptance criteria based on visual designs and user flows.

Identify and resolve technical debt with focus on finding and cataloging issues. Use when asked to find code smells, audit TODOs, identify complexity, improve code quality, or assess technical debt. Triggers on: "use tech-debt mode", "tech debt", "find TODOs", "code smells", "technical debt audit", "find complexity", "code quality audit". Full access mode - can modify files and run tests.

Expert guidance for writing clear, comprehensive documentation including READMEs, API docs, docstrings, and technical guides. Use when creating or improving documentation.

Generate planning docs (IMPLEMENTATION_PHASES.md, DATABASE_SCHEMA.md, API_ENDPOINTS.md, ARCHITECTURE.md) for web projects. Use for new projects, major features, or phased development with Cloudflare Workers + Vite + React.

Expert guidance for writing Python tests with pytest and unittest. Use when writing tests, debugging test failures, or improving test coverage for Python projects.

Type-safe ORM for Cloudflare D1 databases using Drizzle. Use when: building D1 database schemas, writing type-safe SQL queries, managing migrations with Drizzle Kit, defining table relations, implementing prepared statements, using D1 batch API, or encountering D1_ERROR, transaction errors, foreign key constraint failures, or schema inference issues.Keywords: drizzle orm, drizzle d1, type-safe sql, drizzle schema, drizzle migrations,drizzle kit, orm cloudflare, d1 orm, drizzle typescript, drizzle relations, drizzle transactions,drizzle query builder, schema definition, prepared statements, drizzle batch, migration management,relational queries, drizzle joins, D1_ERROR, BEGIN TRANSACTION d1, foreign key constraint,migration failed, schema not found, d1 binding error, schema design, database indexes, soft deletes,uuid primary keys, enum constraints, performance optimization, naming conventions, schema testing

将 DOC/DOCX/PDF/PPT/PPTX 文档转换为 Markdown 格式。自动检测 PDF 类型（电子版/扫描版），提取图片到独立目录。当管理员入库非 Markdown 文档时使用此 Skill。触发条件：入库 DOC/DOCX/PDF/PPT/PPTX 格式文件。

Guide for writing and improving Claude Code skills. Use when creating new skills, debugging why skills aren't activating, or improving skill descriptions and structure.

This skill should be used when the user wants to create a new looplia workflow, generatea workflow definition file, or compose workflow steps from skill recommendations. Use whensomeone says "create a looplia workflow", "generate workflow.md", "compose workflow steps","build me an automation pipeline", or "/build" (final step).Final step in looplia workflow building: transforms skill recommendations into valid v0.6.3workflow YAML/Markdown files. Each step uses skill: + mission: syntax, following the oneworkflow step → one skill-executor → multiple skills architecture.v0.6.3: Supports input-less workflows using input-less capable skills (e.g., search).

为大文件生成目录概要。当入库的 Markdown 文件超过阈值（默认30KB）时，提取标题结构创建导航文件。触发条件：Markdown 文件大小 >= 30KB。

Provides templates, standards, and best practices for writing clear, comprehensive technical documentation

自媒体写作交互式助手。帮助完成从选题到发布的完整流程。适用于：开始写新文章、检查草稿质量、诊断发布后数据不佳的原因。

Generate comprehensive plan documentation following Template 1 format. Use when creating plan.md files for new components or subsections.

Generate, validate, and maintain API documentation (REST/OpenAPI and GraphQL) with reproducible structure and evidence-backed confidence.

Use when ranking backlogs, deciding what to do first based on effort vs impact (quick wins vs big bets), prioritizing feature roadmaps, triaging bugs or technical debt, allocating resources across initiatives, identifying low-hanging fruit, evaluating strategic options with 2x2 matrix, or when user mentions prioritization, quick wins, effort-impact matrix, high-impact low-effort, big bets, or asks "what should we do first?".

Use when content must be translated between audiences with different expertise, context, or goals while preserving accuracy but adapting presentation. Invoke when technical content needs business framing (engineering decisions → executive summary), strategic vision needs tactical translation (board presentation → team OKRs), expert knowledge needs simplification (academic paper → blog post, medical diagnosis → patient explanation), formal content needs casual tone (annual report → social media post), long-form needs summarization (50-page doc → 1-page brief), internal content needs external framing (roadmap → public updates, bug tracking → known issues), cross-cultural adaptation (US idioms → international clarity, Gen Z → Boomer messaging), medium shifts (written report → presentation script, detailed spec → action checklist), or when user mentions "explain to", "reframe for", "translate this for [audience]", "make this more [accessible/formal/technical]", "adapt for [executives/engineers/customers]", "simpl

Rule 07: Testing. Use when writing tests, reviewing test coverage, or setting up testing.