Total 53,748 skills, Documentation & Writing has 1520 skills
Showing 12 of 1520 skills
Create structured technology trade-off analysis documents with scored comparison matrices. Use this skill whenever the user wants to compare technologies, evaluate architectural options, analyze build-vs-buy decisions, assess migration strategies, or produce any decision document that compares multiple approaches across weighted dimensions. Triggers on: 'trade-off analysis', 'tradeoff', 'comparison matrix', 'evaluate options', 'which technology should we use', 'compare approaches', 'pros and cons of', 'build vs buy', 'migration analysis', 'consolidation analysis', 'technology selection'. Also use when the user has completed technical research and wants to structure findings into a decision document.
Write PhD/Master's thesis — full chapter structure, literature review chapter, methodology chapter, results chapter, discussion chapter, and conclusion. Use when drafting thesis chapters, organizing thesis structure, or converting papers into thesis format.
Write, review, and restructure useful documentation with Diataxis, audience-specific README patterns, and AI-writing trope cleanup. Use when creating docs, improving READMEs, reorganizing documentation, or editing prose for clarity.
Crear o actualizar Architecture Decision Records (ADRs) en docs/adr/. Activar siempre que el usuario quiera documentar, registrar, actualizar o cambiar el estado de una decisión arquitectónica — incluso si no usa la palabra "ADR". Frases que activan este skill: "registrar decisión", "documentar por qué usamos X", "dejar constancia de esta elección técnica", "decision record", "cambiar ADR a Accepted", "marcar como Superseded", "crear ADR", "actualizar ADR", "nuevo ADR", "ADR-XXX". Usar también cuando el usuario describa una tensión arquitectónica que deba quedar documentada.
Read and comprehend story texts, summarize characters, relationships, and plots, and organize them into a coherent outline. Suitable for quickly grasping the core of a story and providing an outline foundation for script creation
General Chinese Creation and Revision Skill. Applicable to Zhihu answers, forum long posts, official account articles, blogs, comments, character stories, historical narratives, news and industry interpretations, popular science, tutorials, reviews, personal narratives, novels, stories, dialogues, oral broadcasts, and speeches. Defaults to writing in the voice of someone who has experienced things, checked materials, and is willing to explain the ins and outs clearly, focusing on retaining the authentic human touch and natural Chinese rhythm of long answers and posts on the Chinese internet, while avoiding empty institutional tones, slogan-style speech tones, marketing tones, and AI model tones. For non-fiction long articles, first check if the materials are sufficient; if not, conduct research, ask questions, or shorten the article, and never pad the word count with repetitive explanations. Verify facts, quotes, data, and user experiences for real-world content; for fictional content, characters, scenes, dialogues, psychology, and plots can be created. Colons, dashes, phrases like "not...but..." and similar counterargument structures are strictly prohibited in the final draft, and business jargon and AI model jargon should be removed. Do not create author profiles, personal rule libraries, or personal writing Skills.
Apply classical rhetoric — Ethos, Pathos, Logos — to analyze persuasive communication and craft effective arguments. Use this skill when the user needs to make a speech more persuasive, analyze why a piece of communication is effective, write a compelling proposal, or evaluate rhetorical strategies — even if they say 'make this more convincing', 'why is this speech so powerful', or 'how do I persuade the board'.
This skill should be used when a team wants to create or refine the technical guidelines document — for example "create the tech steering doc", "document our tech stack", "write the technical guidelines", "document our architecture decisions", "set up the tech steering", or "update the tech doc". Generates docs/steering/TECH.md as a living document capturing the stack, architecture patterns, constraints, commands, and ADRs. Generated once and refined — not regenerated from scratch.
Revise brand and corporate communications into clear, respectful, considered writing. Use when editing or drafting marketing copy, product descriptions, brand guidelines, corporate communications, emails, or any customer-facing content. Inspired by Aesop's philosophy: formality with warmth, clarity over cleverness, precision over excess.
Static site generators, documentation platforms, and deployment workflows for technical documentation
Conduct targeted code exploration on a repository, and document the process of "Asking Questions → Reading Code → Reaching Conclusions" as searchable evidence for direct reuse when similar questions arise next time. There are three types: question (investigate code around a specific problem and provide conclusions), module-overview (organize the structure, boundaries, entry points, and dependencies of a module), spike (conduct lightweight technical exploration of multiple possible directions without making final decisions). Trigger scenarios: When users say "Let's explore first", "How is X implemented in this repository", "Quickly get familiar with this module", "Archive the exploration results". For the distinction from learning / tricks / decisions, refer to the root skill `easysdd`.
Draft or update requirement documents under `easysdd/requirements/` for the project — describe a capability's "reason for existence, solution approach, and boundaries" using **user stories + plain language**, so non-technical readers can quickly grasp the key highlights of the system. Layered with architecture: requirement is the "problem space" (why this capability is needed), while architecture is the "solution space" (what structure is used to implement it). Two modes: new (draft a new requirement doc from scratch), update (refresh an existing doc based on new materials or implementation changes). Single-target rule — only modify one document at a time. Trigger scenarios: when the user says "fill in a requirement doc", "write down the requirements for this capability", "update the requirements directory", or when it is found during the feature-design phase that there is no corresponding requirement for the capability to be implemented this time.