writing▌

For straightforward questions about a single table:

Write narrative fiction following your project's established style and conventions.

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

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 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.

Decision tree and templates for building agent skills that agents actually follow. \n \n Provides three architecture tiers based on skill complexity: Tier 1 for simple single-file skills, Tier 2 for multi-concept skills, and Tier 3 for large platforms \n Includes specialized guides for improving existing skills: modularization, anti-rationalization (preventing agent rule-ignoring), and CSO (search optimization for LLM discovery) \n Offers four skill templates covering technique, reference, disci

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