Technical Writing

Comprehensive text editing and improvement assistant with multiple specialized modes. Use when editing, improving, proofreading, polishing, reviewing, rewriting, or cleaning up written content. Supports fixing typos and grammar errors, checking grammar, correcting mistakes, improving flow and readability, adding punctuation, restructuring with headings, adding examples, citing sources, fact-checking, and preserving detail. Handles spelling, grammar, structure, citations, accuracy improvements, and formatting. Works with documentation, articles, markdown files, and any written content.

Complete REST API development workflow coordinating backend, database, testing, documentation, and DevOps agents. 2-week timeline with TDD approach.

Creates comprehensive implementation plans with exact file paths, complete code examples, and verification steps for engineers with zero codebase context. Assumes skilled developers who need domain-specific guidance, following DRY, YAGNI, and TDD principles. Use after brainstorming/design is complete when handing off to another developer or planning complex multi-step work. Do NOT use for simple tasks, quick fixes, or when you're implementing yourself and already understand the codebase - just start coding instead.

NicheCompass 本地文档（en/latest）

Write structured notes from source materials following academic standards.LOAD THIS SKILL WHEN: User says "寫筆記", "write notes", "摘要", "summarize", "整理重點" | has source content to summarize | creating reading notes.CAPABILITIES: Structured summaries, key point extraction, citation formatting, template-based writing.

TypeScript 5.x development with type system, generics, utility types, and strict mode patterns. Use when writing TypeScript code or adding types to JavaScript projects.

Generate comprehensive Jest tests for React Native components, hooks, and services. Use when writing tests, improving coverage, or test-driven development.

Enforce TypeScript strict mode practices and type safety in Tetris codebase. Use when writing game logic, handling errors, improving type safety, or fixing type errors. Auto-triggers on phrases like "fix type errors", "improve type safety", "handle this error", or "make this type-safe". Focuses on Result<T,E> pattern, proper type guards, and avoiding type assertions.

ユーザーメモリ、プロジェクトメモリ、READMEを再読み込み。「コンテキストを再読み込み」「設定をリロード」「CLAUDE.mdを読み直して」と言われた時、またはclear後にコンテキストを復元したい時に使用

Codex MCP tool reference. Supplemental parameter docs for codex tool (tuannvm/codex-mcp-server).

Setup project repositories with industry-standard structure, configuration, and documentation for Rust, Python, or TypeScript/Vite/Astro projects. Use when users explicitly request to orchestrate, setup, or initialize a project with proper tooling, Docker configs, pre-commit hooks, linting, and README documentation. Creates complete project scaffolding with appropriate directory structure, configuration files, and deployment setup.

This skill provides production-ready AI chat UI components built on shadcn/ui for conversational AI interfaces. Use when building ChatGPT-style chat interfaces with streaming responses, tool/function call displays, reasoning visualization, or source citations. Provides 30+ components including Message, Conversation, Response, CodeBlock, Reasoning, Tool, Actions, Sources optimized for Vercel AI SDK v5.Prevents common setup errors with Next.js App Router, Tailwind v4, shadcn/ui integration, AI SDK v5 migration, component composition patterns, voice input browser compatibility, responsive design issues, and streaming optimization.Keywords: ai-elements, vercel-ai-sdk, shadcn, chatbot, conversational-ai, streaming-ui, chat-interface, ai-chat, message-components, conversation-ui, tool-calling, reasoning-display, source-citations, markdown-streaming, function-calling, ai-responses, prompt-input, code-highlighting, web-preview, branch-navigation, thinking-display, perplexity-style, claude-artifacts

Track content through weekly writing pipeline stages (capture/cluster/outline/draft/revise/review/publish). Shows status, suggests next actions, generates pipeline dashboard. Use when user asks about "pipeline status", "writing progress", "what to work on", or "weekly review".

Ensures interactive learning experiences follow Brilliant's challenge-first, scaffolded pedagogy. Use when designing interactions, writing UI copy, evaluating feedback loops, sequencing learning moments, or making any decision about how users discover concepts. Triggers on questions about "how should this work pedagogically", "what should users see first", "how do we handle wrong answers", or "when should the formula appear".

Company-specific procedures, standards, templates, and best practices for engineering documentation, project management, and professional communication in building energy consulting

Use when working with Vue.js 3 projects - provides patterns for Composition API, reactivity, components, and best practices from official Vue.js documentation

Compensates for Claude's January 2025 knowledge cutoff by actively searching Apple's official iOS 26 documentation before making claims about iOS 26 APIs, frameworks, or features. This skill should be used when about to make statements about iOS 26 features, suggesting iOS 26-specific APIs, implementing iOS 26 functionality, or answering questions about iOS 26 capabilities. The skill provides multi-tier search workflows using Apple RAG, Sosumi, and web search tools with proper verification tagging.

Create detailed lesson plans, instructional materials, learning activities, and differentiation strategies aligned to learning objectives. Use when developing instructional content, writing lesson plans, or creating learning activities. Activates on "create lesson plan", "develop content for [objective]", "write instructional materials", or "design learning activities".

Documentation-first task execution with quality checks and progress tracking. Use when working with task lists, implementing features, or executing multi-step work to ensure systematic completion with proper documentation review.

Create structured use case documentation with sequence diagrams for backend systems. Use when documenting API endpoints, service interactions, event flows, or system behaviors. Triggers on requests like "document this use case", "create use case for X endpoint", "write flow documentation", or "explain how X feature works".