Loading...
Loading...
Found 25 Skills
You are a **Technical Writer**, a documentation specialist who bridges the gap between engineers who build things and developers who need to use them. You write with precision, empathy for the read...
Expert technical writer specializing in developer documentation, API references, README files, and tutorials. Transforms complex engineering concepts into clear, accurate, and engaging docs that developers actually read and use.
Research developer documentation audiences by mapping user goals, learning objectives, business goals, developer traits, user questions, personas, user stories, journey maps, and friction logs. Use when planning docs for APIs, SDKs, platforms, CLIs, developer tools, onboarding guides, SaaS docs, or support-heavy docs before writing or restructuring content.
Gather, classify, prioritize, respond to, and act on developer documentation feedback from page feedback, support issues, community forums, field notes, sentiment, surveys, user councils, bug reports, and user follow-up. Use when setting up docs feedback channels, triaging docs issues, responding to frustrated users, prioritizing doc fixes, or converting feedback into actionable documentation work.
Guides the agent through connecting an MCP client to the hosted, unofficial Capacitor MCP server by Capawesome, which serves the official Capacitor documentation for v8, v7, v6 and next, the official and community plugin list, and the Capacitor posts from the Ionic blog. Covers client detection, setup for Claude Code, Claude Desktop, Cursor, VS Code, Windsurf, Zed and stdio-only clients, documentation version selection, verification, and troubleshooting. Do not use for installing or configuring Capacitor plugins, upgrading or migrating apps and plugins to a newer version, Ionic Framework UI components, Capawesome Cloud, or MCP servers other than the Capacitor one.
Answer "how does this work / how is this structured / what does this change" with a drawn figure and a narration that follows it — a module map from the code's own imports, a walked request, a state machine, an algorithm step by step, the change map of a branch — produced with `vlmkit-anim`, checked against the facts it draws, and delivered as an SVG / GIF next to the prose. Use whenever the user asks to explain, walk through, show the structure of, or illustrate code, a repository, a flow, a protocol, a PR, or a bug, and a picture with four or more things and their relations would carry the answer better than a paragraph. The explanation is the deliverable; the picture is its evidence. Scene mechanics are in `explanatory-animation`.
Use when creating or editing persistent or reader-facing prose such as documentation, ADRs, Issues, Pull Requests, commit messages, code comments, and review comments. Converts working context into reader-oriented text through explicit selection, composition, and rereading instead of serializing conversation or execution context.
Base44 platform concepts for a web app: entities, backend functions or server code, workflows, pages and layouts, the project file structure, authentication (platform login vs the custom-auth boilerplate), user invites and the GitHub features. Read first when starting work on a Base44 web app.
Use when writing or reviewing working text: a repository page, a code comment, a description or help text, a PR, an issue, a CI comment, a Notion page, or a diagram that a colleague will scan to get work done, or when a change moves code across the layers an architecture page declares. Not for a paper, an essay, or any text read start to finish.
Deliver a complete, self-contained quickstart guide with runnable examples for a library, framework, or developer tool, with implementation depth matched to the learner's goal.
新規参入者が会話履歴や個人環境に依存せずprojectを理解・起動・検証・開発開始・作業復旧できるdocumentationを初期化・更新する時に使用する。
Use when writing, reviewing, restoring, trimming, or auditing prose in the deepseek-harness repo, including deciding where documentation or comments are required across Markdown, JSDoc, code and test comments, prompts, descriptions, diagnostics, and CLI or UI strings.