Technical Writing

Iteration 6 of Multiplicity Cascade - Documentation that modifies itself when read

Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.

Manage Confluence documentation with downloads, uploads, conversions, and diagrams. Use when asked to "download Confluence pages", "upload to Confluence", "convert Wiki Markup", "sync markdown to Confluence", "create Confluence page", or "handle Confluence images".

Validate topic uniqueness and identify unique angles before writing. Prevents generic content and helps find your specific value.Trigger phrases: "topic research", "validate topic", "should I write", "is this unique", "research topic", "check topic"

Apply consistent CSS styling methodologies using project conventions such as Tailwind CSS utility classes, BEM naming, CSS Modules, or styled-components while maintaining design system consistency. Use this skill when writing or modifying styles in component files, CSS files, Tailwind classes, styled-components, CSS-in-JS solutions, or design token configurations. Use this skill when working with CSS frameworks, establishing design tokens for colors and spacing, optimizing CSS for production builds, or ensuring consistent styling patterns across the application. Use this skill when working with .css, .scss, .module.css files, or when adding className attributes to components with utility classes.

Use when editing Observable notebooks (docs/index.html), creating charts with Plot, adding SQL cells, loading data with FileAttachment, or working with DuckDB. Triggers on notebook editing, visualization, data loading.

Conduct comprehensive codebase research by spawning parallel agents to document and explain code as it exists. Use this skill when needing to understand how a codebase works, where specific functionality lives, or what patterns exist. This skill orchestrates specialized agents (codebase-locator, codebase-analyzer, codebase-pattern-finder) and synthesizes findings into structured documentation.

Generate structured reports from collected data.LOAD THIS SKILL WHEN: User says "寫報告", "產出報告", "撰寫報告", "generate report" | after research/analysis | need structured documentation.CAPABILITIES: Research/Technical/Project reports, Markdown format, auto date stamps, structured sections (abstract, methods, results, discussion).

Git convention for branch naming, commit messages, and issue labels based on GitFlow and Conventional Commits. Use when creating branches, writing commit messages, or setting up issue labels.

Helps write conventional commit messages, create atomic commits, and follow git best practices. Use when the agent needs to help with git commits, commit message writing, or git workflow guidance.

Comprehensive guide for modern front-end testing with Playwright (2025). This skill should be used when writing end-to-end tests, component tests, or visual regression tests for web applications using Playwright. Covers Page Object Model patterns, TypeScript integration, modern SPA testing strategies, accessibility testing, and CI/CD automation with GitHub Actions.

Find places where an entity is mentioned but not wikilinked. Triggers on "unlinked mentions", "where is X mentioned", "link X everywhere", "mentions of X".

Guide for writing clear, comprehensive technical documentation including README files, API docs, guides, and inline documentation

Transform academic course assignment PDFs into structured, actionable markdown checklists with dates, unique IDs, and custom tags. Asks when the user will start, assigns tasks only to weekdays (Monday-Friday), respects weekends automatically, and calculates forum deadlines 3 days before due date. Use this skill when the user uploads academic PDFs or asks to create a task plan from course assignments.

Generate comprehensive tests for Zustand stores with nested immutable updates, async actions, and persistence. Use when creating or modifying stores, writing tests, or debugging state issues. Keywords: zustand, store, testing, state, vitest, mock.

claude-plugin 프로젝트 개발 가이드라인, 레퍼런스 패턴, 프로젝트 구조 조회. Use when Claude needs to (1) Look up development principles (P1-P4, DRY, KISS, YAGNI, SOLID), (2) Find reference patterns for Hooks/Agents/Commands creation, (3) Understand project structure and file locations, (4) Learn how to create Skills/Hooks/Agents/Commands, or (5) Delegate to claude-code-guide for official Claude Code documentation

Create and manage MDX blog posts, projects, and pages with proper frontmatter and locale support. Use when writing new blog posts, creating project pages, adding pages, or working with MDX content rendering.

Generate JSDoc configuration and documentation templates for JavaScript/TypeScript projects. Triggers on "create jsdoc config", "generate jsdoc template", "documentation setup", "jsdoc configuration".

Operate Linear effectively for issue tracking, project management, and team coordination. Provides workflows for common operations using Linear MCP tools and references official documentation.

根据用户给出的excel文件内容，从中分析kpi指标的情况，并按照分工的列表，分别生成markdown格式的报告