Loading...
Loading...
Found 37 Skills
Extract a DDD-style ubiquitous language glossary from the current conversation, flagging ambiguities and proposing canonical terms. Saves to UBIQUITOUS_LANGUAGE.md. Use when user wants to define domain terms, build a glossary, harden terminology, create a ubiquitous language, or mentions "domain model" or "DDD".
Technical blog post writing with structure, code examples, and developer audience conventions. Covers post types, code formatting, explanation depth, and developer-specific engagement patterns. Use for: engineering blogs, dev tutorials, technical writing, developer content, documentation posts. Triggers: technical blog, dev blog, engineering blog, technical writing, developer tutorial, tech post, code tutorial, programming blog, developer content, technical article, engineering post, coding tutorial, technical content
Write clear, emotionally resonant, and well-structured content that readers remember and act upon. Use when writing or editing any text—Twitter posts, articles, documentation, emails, comments, updates—for maximum clarity, engagement, and impact.
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
Write and revamp product documentation to a high editorial standard using Mintlify, with strong information architecture, precise titles/descriptions, parameter-level clarity, cross-linking, and maintainable examples. Use when creating new docs pages, refactoring existing docs, improving docs structure/navigation, or standardizing docs quality across a repository.
Write a handoff document summarizing the current conversation so a fresh agent can continue the work without losing context.
Create audience-aware standalone application release notes and actionable migration guides from version-control changes, contracts, schemas, configuration, tests, and deployment evidence. Use for release-visible behavior, breaking changes, upgrades, deprecations, rollout steps, or rollback guidance.
Use when writing any React documentation. Provides voice, tone, and style rules for all doc types.
Create release notes that summarize features, fixes, and migration guidance for software releases.
Guidelines for writing and editing Plain package READMEs. Use this when creating or updating README files.
Эксперт по README файлам. Используй для создания документации проектов, badges, installation guides и usage examples.
Text formatting conventions for markdown and prose files. Use when writing or editing any .md, .txt, .adoc, or .rst file, including AGENTS.md, SKILL.md files, and documentation in docs/.