writing▌

Expert-level guidance for writing publication-ready papers targeting NeurIPS, ICML, ICLR, ACL, AAAI, COLM (ML/AI venues) and OSDI, NSDI, ASPLOS, SOSP (Systems venues). This skill combines writing philosophy from top researchers (Nanda, Farquhar, Karpathy, Lipton, Steinhardt) with practical tools: LaTeX templates, citation verification APIs, and conference checklists.

Purpose: This skill helps researchers improve the quality and naturalness of their own original ideas expressed through AI-assisted writing tools.

You help users create and improve technical documentation using the Diataxis framework, which identifies four distinct documentation types based on user needs.

Write comprehensive implementation plans assuming the engineer has zero context for our codebase and questionable taste. Document everything they need to know: which files to touch for each task, code, testing, docs they might need to check, how to test it. Give them the whole plan as bite-sized tasks. DRY. YAGNI. TDD. Frequent commits.

Writing skills IS Test-Driven Development applied to process documentation.

This skill enforces Sentry's blog writing standards across every post — whether you're helping an engineer write their first blog post or a marketer draft a product announcement.

Write clear, concise, user-centered interface copy (UX text/microcopy) for digital products and experiences. This skill provides frameworks, patterns, and best practices for creating text that helps users accomplish their goals.

Write user stories with clear acceptance criteria to guide development from the user's perspective. \n \n Provides a structured template covering user role, desired action, business value, and detailed acceptance criteria using Given-When-Then format \n Includes reference guides for story refinement, splitting, estimation, and acceptance criteria examples \n Emphasizes user-focused writing, testability, and small story sizing appropriate for single-sprint completion \n Covers best practices for

Write clear, concise, and helpful interface copy.

Structured task planning with clear breakdowns, dependencies, and verification criteria. \n \n Breaks work into small, focused tasks (2-5 minutes each) with one clear outcome and independent verification per task \n Emphasizes project-specific planning over templates, with dynamic content tailored to new projects, feature additions, bug fixes, or refactoring \n Saves plans as markdown files in the project root with slug-based naming (e.g., auth-feature.md ), never in hidden or temp folders \n Re