Total 53,761 skills, Documentation & Writing has 1520 skills
Showing 12 of 1520 skills
Paragraph-level structural blueprint for 10-12 page systems papers targeting OSDI, SOSP, ASPLOS, NSDI, and EuroSys. Provides page allocation, paragraph templates, and writing patterns. Use when user says "写系统论文", "systems paper structure", "OSDI paper", "SOSP paper", or wants fine-grained structural guidance for a systems conference submission.
One-stop skill for the project architecture center — draft new architecture documents, refresh existing ones, or conduct an architecture health check. Automatically determine the mode based on user input: `new` (draft)/ `update` (refresh to latest code status)/ `check` (review without modification, generate issue list). The `check` mode has three sub-objectives: consistency within a single feature design, alignment between design and code, and consistency among multiple documents under `codestable/architecture/`. Single-target rule — only modify one document or check one target at a time. Trigger scenarios: User says "fill in an architecture doc", "draft an architecture document", "refresh the architecture directory", "write down this module structure", "conduct an architecture check", "is the design internally consistent?", "does the plan match the code?", "are there conflicts among several documents in the architecture folder?", or when an architecture action is required before proceeding during the feature-design / feature-acceptance / implement phases.
Explain code as a scannable blog post
Generate comprehensive documentation for content authors taking over an AEM Edge Delivery Services project. Analyzes the project structure and produces a complete authoring guide with blocks, templates, configurations, and publishing workflows.
Use when initializing, bootstrapping, creating, or scaffolding the minimum docs-driven workflow layout for a repository before roadmap planning, specs, or implementation tasks exist.
Creates an Architecture Decision Record following the Nygard format to document significant technical decisions, their context, and consequences. Use when making technical choices that affect system architecture, technology selection, or development patterns.
Use this skill for "write a literature review", "synthesize papers", "review the literature", "summarize research findings", "identify research trends", "gap analysis", "thematic review", "systematic review", "scoping review", "narrative review", "compare studies", "research synthesis", or when the user wants to synthesize multiple papers into a cohesive literature review.
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.
Skill for optimizing article style to remove AI flavor. Used to identify and rewrite issues such as AI traces, template tone, material-like style, translationese, empty buzzwords, excessive golden sentences, overuse of em dashes, bullet stacking, and random bolding in articles, official account drafts, self-media drafts, oral broadcast scripts, speech scripts, course scripts, and product copy; activated when users say phrases like "remove AI flavor", "eliminate AI traces", "not written by AI", "more human-written", "more natural", "less robotic", "remove template feel", "polish to official account final draft". Not applicable for fact-checking, zero-based topic planning, converting papers to official account articles, pure title generation, or pursuing AI detector pass rates.
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.
Strategic thought-leadership book collaborator for founders, experts, and operators turning voice notes, fragments, and positioning into structured first-person chapters.
McKinsey-style storyline framework for building presentation decks. Use when users need to structure presentations, pitch decks, or strategic communications. Creates logical flow where each storyline becomes a slide title, progressing from problem to solution.