Total 52,191 skills, Documentation & Writing has 1490 skills
Showing 12 of 1490 skills
Craft compelling query letters and track submissions to literary agents
Draft or update architecture documents under `easysdd/architecture/` — describe what a subsystem/module looks like currently, how it is divided, and how external interfaces operate, to provide pre-positioning input for subsequent feature-design. Information sources include code + user materials (oral accounts, scattered documents, compound deposits, existing decisions), and the output can be reverse-validated by anchoring to specific `file:line`. Two modes: new (draft a new architecture document from scratch), update (refresh an existing document based on the latest code status and new user materials). Single-target rule — only modify one document at a time. Trigger scenarios: user says "fill in an architecture doc", "draft an architecture document", "update the architecture directory", "write down the structure of this module", or when it is found that "something that should be in the architecture is missing" during the feature-design / feature-acceptance phase.
Draft patent claims for an invention. Use when user says "撰写权利要求", "draft claims", "写权利要求书", "claim drafting", or wants to create patent claims. The core skill of the patent pipeline.
Help a PhD student prepare, rehearse, and tighten a research presentation, lab meeting update, conference talk, thesis defense segment, or interview research talk. Use this skill whenever the user has slides, an outline, a talk deadline, a time limit, or wants to make a presentation clearer, shorter, more professional, or more audience-aware.
Content generation skill for the Orbitant engineering blog. Activates when creating a blog post from raw input (transcript, notes, or draft). Produces a structured, SEO-optimised article in Spanish that matches Orbitant's tone, editorial standards, and content cluster strategy. Use this skill whenever someone provides raw material and asks to turn it into a publishable blog post for the Orbitant blog.
Create standalone beginner tutorial packages from a topic or supplied references, with adaptive research, course-style outline design, chapter visuals, and Markdown/DOCX/PDF/HTML exports. Use for textbook-like tutorials, course guides, teaching documents, or long beginner guides; not for quick answers, link summaries, pure diagrams, or file conversion.
Analyse code changes since the last docs update and refresh the project's documentation files. Use when code has changed and documentation needs to be updated, after implementing new features, or before a milestone commit.
Write a new doc-site page (guide, tutorial, reference, concept) following the project's docs conventions. Use when user says 'write a doc', 'add a page to the docs site', 'create a guide for X', 'write a tutorial', 'document this concept', or 'add reference for our API'. Do NOT use for feature-specific end-user docs (use document-feature), ADRs (use document-decision), or CLAUDE.md updates (use create-or-audit-claude-md).
Create a ***plain import module that provides shared definitions, implementation reqs, and test reqs for other modules to import. Use when the user wants to create a new .plain file that contains only definitions, implementation reqs, and/or test reqs — no functional specs.
Use when responding to academic reviewers, planning revisions, writing rebuttals, mapping reviewer concerns, deciding concede/defend/reframe actions, or preparing camera-ready changes.
You must use this when critiquing academic manuscripts, evaluating methodological rigor, or providing structured reviewer feedback.
Prepare for PhD or Master's thesis defense. Use when preparing defense presentation, anticipating committee questions, practicing oral defense, or structuring defense slides.