Technical Writing

Guide technology selection workflow and ADR creation. Use when user asks about choosing a technology, comparing options, or needs to make a tech decision. Orchestrates discovery, evaluation, and documentation.

Write scientific manuscripts with proper structure (IMRAD), citations (APA/AMA/Vancouver), figures/tables, and reporting guidelines (CONSORT/STROBE/PRISMA). Use when drafting any manuscript section, improving writing clarity, or preparing for journal submission.

Provides reference documentation and examples for all of the available Flowbite TailwindCSS HTML UI Components plus the related Typography and Forms plugins.

Understand and apply the n8n community node tech stack including TypeScript strict mode, Node.js v22+, n8n-workflow package, and build tools. Use this skill when setting up new n8n node projects, configuring package.json, writing TypeScript with strict mode, running build or dev scripts, configuring ESLint with n8n rules, setting up Jest tests, or preparing packages for npm publishing. Apply when making decisions about runtime, dependencies, or tooling in n8n node development.

Run timed flashcard drills when user says "drill <category>" (e.g., "drill bitwise", "drill 1-bitwise", "drill arrays"). Reads all flashcards upfront, quizzes rapidly, logs results, drills missed cards, then updates README.

Search hippocampus knowledge base for documentation, conventions, patterns, and how-to guides (discovery: requirements-clarity). Evaluate at requirements-clarity when user asks "how do I...", "find my...", "what's my convention for...", "continue working on...", or wants to create/edit persistent documentation. All markdown files must go to hippocampus - none created elsewhere.

**AUTO-TRIGGER when user says:** "update progress", "track status", "what's our progress", "generate progress report", "update next steps", "update Notion memory", "create session page"Manages TogetherOS progress tracking, Notion memory updates, and status reporting. Updates module progress, manages next steps, syncs to Notion, and maintains session memory.Use proactively without asking permission when task matches skill purpose.

Look up Microsoft API references, find working code samples, and verify SDK code is correct. Use when working with Azure SDKs, .NET libraries, or Microsoft APIs—to find the right method, check parameters, get working examples, or troubleshoot errors. Catches hallucinated methods, wrong signatures, and deprecated patterns by querying official docs.

Use ONLY this skill when user mentions a domain (example.com, site.pl, docs.io), URL (https://...), or asks to read/fetch/check a website or webpage - MANDATORY, replaces WebFetch, crawl4ai, and curl

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.

Write purposeful code comments that explain the "why" behind technical decisions, complex logic, and non-obvious implementations using JSDoc for components and APIs. Use this skill when documenting component props, explaining complex algorithms, noting performance optimizations, documenting workarounds, or adding API documentation. When working on component prop interfaces requiring JSDoc documentation, complex business logic or algorithms, performance optimization rationale, browser compatibility workarounds or hacks, API route documentation with request/response formats, configuration file explanations, Content Collection schema documentation, or regex patterns and what they match.

Interpretive guidance for designing Claude Code slash commands. Helps you apply official documentation effectively and create high-quality commands. Use when creating or reviewing slash commands.

Apply the K.I.S.S principle (Keep It Simple, Stupid) to reduce complexity, improve maintainability, and solve problems elegantly. Use when designing systems, writing code, planning solutions, creating documentation, architecting features, or making decisions where simplicity drives quality and efficiency.

プロダクト要求定義書（PRD）を作成するスキル

Guidelines for writing effective git commit messages using conventional commits style

Create interface-first documentation using BRIEF system v3. Generate BRIEF.md files with inputs/outputs contracts, validate against spec, convert PRDs/specs to BRIEFs, and support multi-surface applications (Web/Mobile/API). Use when creating module documentation, establishing documentation standards, or documenting legacy code.

Convert UI/UX designs (mockups, wireframes, screenshots) into technical specs, component architectures, and implementation guides. Use for design analysis, design system extraction, component specifications, and frontend documentation.

Guide for understanding and writing Miden VM assembly (MASM) code. Use when:(1) Reading, analyzing, or explaining MASM code(2) Writing new MASM procedures or programs(3) Debugging MASM execution or stack state(4) Optimizing MASM code for cycle count(5) Working with Miden VM stack machine conceptsCovers instructions, code organization, core library, and common patterns.

Web research and literature search capabilities for external resources.LOAD THIS SKILL WHEN: User says "搜尋", "search", "找資料", "查詢", "檢索", "web search", "網路搜尋" | needs external documentation | research task | API reference lookup | technology comparison | wants latest information.CAPABILITIES: Technical docs (MDN, GitHub, Stack Overflow), academic papers (PubMed integration), API documentation, real-time web data via fetch_webpage, structured search results.

Handles the publication workflow for AndesRC blog articles. Creates markdown files, triggers builds, submits to Google Search Console, and initiates promotion. Use as the final step in the content pipeline.