Technical Writing

Work with MongoDB (document database, BSON documents, aggregation pipelines, Atlas cloud) and PostgreSQL (relational database, SQL queries, psql CLI, pgAdmin). Use when designing database schemas, writing queries and aggregations, optimizing indexes for performance, performing database migrations, configuring replication and sharding, implementing backup and restore strategies, managing database users and permissions, analyzing query performance, or administering production databases.

Expert in implementing Microsoft 365 Copilot agents with TypeSpec code (use AFTER project is created). Use when (1) Writing or editing .tsp files in an existing project, (2) Implementing agent instructions and behavior in TypeSpec, (3) Adding or configuring capabilities (WebSearch, OneDrive, etc.) with proper scoping, (4) Creating API plugin actions with @actions decorator, (5) Defining TypeSpec models and enums, (6) Adding @doc decorators and documentation, (7) Compiling TypeSpec with npm run compile, (8) Fixing TypeSpec compilation errors, (9) Working with @agent, @instructions, @conversationStarter decorators, or (10) Implementing TypeSpec syntax for @microsoft/typespec-m365-copilot library. This skill handles TYPESPEC CODE, not project scaffolding.

Comprehensive change tracking and audit logging system that monitors file modifications, code changes, and project evolution. Use when tracking project history, maintaining audit trails, analyzing development patterns, or when detailed change documentation is required for compliance and team collaboration.. Enhanced with Context7 MCP for up-to-date documentation.

Use when writing essays, explanations, or blog posts. Applies a Cartesian writing style - clear, methodical, building logically from foundations.

Generate all copywriting and asset specifications needed for iOS App Store submissions. Use when preparing an app for App Store Connect, creating app descriptions, keywords, screenshots specs, promotional text, release notes, or any App Store metadata. Covers iPhone/iPad/Watch screenshots, App Clips, iMessage apps, and review information.

Write and run JavaScript/TypeScript tests using Vitest or Jest with mocking, component testing, and coverage. Use when writing JS/TS tests, testing Svelte/React components, or setting up test configuration.

Best practices for developing zensical/Material for MkDocs static sites. Covers installation, virtual environments, project structure, responsive images, CSS, media embedding, and verification. Use for ANY Material for MkDocs project development beyond basic text editing.

Maintain character consistency by cross-referencing canonical character files. Use when writing scenes with established characters, updating character information, or checking for contradictions. Prevents invented physical details, possessions, backstory, and knowledge.

Structure and style guidance for law review articles

RESTful API design patterns, error handling, and documentation

This skill should be used when writing, reviewing, or refactoring documentation that will be consumed as AI context. Optimizes documentation for LLM comprehension using principles of completeness, efficiency, and zero fluff—replacing prose with structured data, enforcing heading hierarchy, detecting meta-commentary, and validating that examples serve a purpose.

Searching internet for technical documentation using llms.txt standard, GitHub repositories via Repomix, and parallel exploration. Use when user needs: (1) Latest documentation for libraries/frameworks, (2) Documentation in llms.txt format, (3) GitHub repository analysis, (4) Documentation without direct llms.txt support, (5) Multiple documentation sources in parallel

项目知识库管理器 - 将保险业务项目文档(数据分析、PPT报告、技术方案)转化为结构化、可迁移的知识资产。支持:(1)自动生成2类标准化模板(项目启动/技术方案);(2)从Markdown/代码仓库智能提取技术决策和可复用模式;(3)统一文档格式标准;(4)生成可跨项目复用的知识库。触发场景:用户要整理项目文档、创建知识库、生成项目模板、提取技术经验、标准化现有文档时使用。

Use this when running or adding tests (compile/lint/unit/E2E), updating test utilities, or working with Playwright/visual testing in markdowntown.

Search and retrieve information from indexed PDF documentation including IC datasheets, FPGA manuals, and technical specifications. Use this when the user asks about hardware specifications, pin configurations, register details, timing diagrams, or any technical information that might be in datasheets or technical documentation.

Use an AI agent with full access to a certain external repository to research. Useful when writing code involving a library to get code examples and information. Use when the user suggests to research how to do something with a certain library.

Clean Code principles adapted for C#/.NET including naming, variables, functions, SOLID, error handling, and async patterns. Use when: (1) reviewing C# code, (2) refactoring for clarity, (3) writing new code, (4) code review feedback.

Write self-documenting code with minimal, evergreen comments that explain why, not what. Use this skill when deciding whether to add comments or when reviewing existing comments. When writing docstrings, inline comments, or documentation blocks. When avoiding comments that describe recent changes, temporary fixes, or obvious code behavior.

When reviewing coding test solutions. This Skill reviews coding test solutions and provides feedback. it adds an evaluation section to the README.md file in the problem-solving folder, including areas for improvement, strengths, and other application ideas based on the provided template. Use this skill when user requests "코테 리뷰", "풀이 리뷰", "리뷰 작성", "리뷰를 작성해줘", "코드 리뷰", or any similar coding test review request.

Assists in writing high-quality content by conducting research, adding citations, improving hooks, iterating on outlines, and providing real-time feedback on each section. Transforms your writing process from solo effort to collaborative partnership.