技術寫作

Complete Jira Cloud REST API documentation for v2 and v3 endpoints. Use when working with Jira APIs, making Jira API calls, troubleshooting Jira integrations, or needing endpoint details. DO NOT use for general Jira usage questions or Jira web UI help.

Write quality markdown content. Use when creating or editing .md files, documentation, READMEs, or any markdown-based content. Ensures proper syntax, structure, and accessibility.

Helps write rap lyrics with proper rhythm, flow, cadences, and structure. Teaches musical fundamentals (bars, beats, tempo, BPM) and lyric formatting. Use when writing rap lyrics, creating verses, understanding flow, structuring bars, improving cadence, learning rhythm patterns, or formatting rap lyrics.

Instructions for writing Go code following idiomatic Go practices and community standards

Generate structured markdown documents (PRDs, tasks, investigation plans) from templates based on workflow type. Creates directory structure and manages document lifecycle for feature, bug, and plan workflows.

Write quality content for HTML documents. Use when writing text content, prose, descriptions, or any human-readable content in HTML files. Ensures spelling and style quality.

Copywriting dla bloga portfolio Pawla Lipowczana (pawellipowczan.pl). Uzyj przy tworzeniu nowych artykulow na blog, generowaniu tresci SEO, pisaniu case studies. Zawiera styl pisania autora (bezposredni, praktyczny, osobisty), strukture artykulow (front matter YAML, hierarchia H1-H3), kategorie (Automatyzacja/No-Code/AI), wytyczne SEO, szablony artykulow. Skill generuje artykuly zgodne z tonem i formatem istniejacych publikacji na blogu.

TypeScript-first ORM patterns for PostgreSQL, MySQL, and SQLite. Use when writing database schemas, queries, migrations, relations, or transactions with Drizzle ORM.

Create onboarding, training, documentation, and enablement flows for admins, data teams, and business users of the InsightPulse Superset Data Lab.

Создание профессиональных юридических документов на русском языке — справки, заключения, аналитические записки, письма в трибуналы, отчёты. Использовать при запросах на создание юридических, аналитических или деловых документов на русском языке с профессиональным оформлением.

Basic practices and guidelines for writing typescript code using that Effect TypeScript libraries (`effect`, `@effect/platform`, `@effect/cli`, `@effect/ai`).

Expert agent architect that creates new skills and agents for unfamiliar technologies. Has unfettered documentation access. Auto-creates skills at threshold (2+ uses).TRIGGERS - Keywords: create skill, create agent, new skill, new agent, skill creation, agent creation, unfamiliar technology, unknown framework, no specialist, missing skill, need expert, technology specialist, extend capabilities.TRIGGERS - Phrases: "create a skill for", "make an agent for", "need a specialist", "don't have a skill for", "unfamiliar with this tech", "research and create", "add support for", "extend to handle".TRIGGERS - Automatic: New technology encountered 2+ times without existing skill, learning agent proposes new agent, repeated documentation lookups for same technology.

Architecture analysis, violation detection, and pattern validation.USE WHEN: reviewing code architecture, identifying violations,verifying patterns, updating technical documentation.Reference: docs/02-architecture/ARCHITECTURE.mdExamples:<example>Context: User wants to check if code follows architecture.user: "Analyze if the payment module follows our architecture"assistant: "I'll use architecture-analyzer to review against ARCHITECTURE.md."<commentary>Architectural review is architecture-analyzer specialty.</commentary></example><example>Context: Need to identify technical debt.user: "Find architectural violations in the services layer"assistant: "I'll use architecture-analyzer to scan for violations."<commentary>Violation detection is architecture-analyzer responsibility.</commentary></example>

Architecture and copywriting framework for high-converting landing pages. Use when building landing pages, sales pages, product pages, or lead capture pages. Follows a proven 8-section structure optimized for conversions.

Use when searching academic papers on arXiv, understanding research content, building literature reviews, or generating citations for academic writing

Fetch web content from URLs, extract specific topics using subagents, and save structured summaries as markdown. This skill should be used when other skills or workflows need to retrieve and analyze web documentation. Input is URL(s) and topic names, output is detailed markdown summaries saved to specified paths.

Validate documentation files for completeness, accuracy, and consistency with the codebase. Use when user mentions "check documentation", "validate docs", "is the README up to date?", requests documentation review, says "docs are wrong" or "fix the docs", or is working on documentation improvements. Covers README files, API docs, CHANGELOG, and any markdown documentation.

This skill should be used when users ask questions about pod network development, pod smart contract language, pod APIs, pod tooling, or pod-specific features. It provides semantic search over the pod network knowledge base to retrieve relevant documentation, code examples, and best practices.

Consolidate README content using language-aware exemplars, internal doc linkage, and reproducible evidence.

Use after brainstorming, before implementation. Breaks work into discrete, actionable tasks with clear verification points.