Technical Writing

Collaborative ideation for projects and writing. Ask clarifying questions, suggest angles, challenge assumptions, and help refine vague ideas into concrete requirements or topics. Use when exploring ideas before planning or drafting.

Apify JS SDK Documentation - Web scraping, crawling, and Actor development

Snap.as API Documentation

Vast.ai API Documentation - Affordable GPU Cloud Marketplace

Cron-Job.org Documentation

Regla 07: Pruebas. Use when writing tests, reviewing test coverage, or setting up testing.

INVOKE BEFORE writing new code to find existing implementations (DRY). Also for codebase exploration and production data search. Run: docker exec arsenal-semantic-search-cli code-search find 'query'

Handle user questions, feature requests, and bug reports for connectrpc-axum. This skill should be used when users ask questions about the library, request new features, or report bugs. It first attempts to answer using project documentation, verifies bugs with integration tests, and submits GitHub issues when needed.

Use when writing or reviewing NIH, NSF, or foundation grant proposals. Invoke when user mentions specific aims, R01, R21, K-series, significance, innovation, approach section, grant writing, proposal review, research strategy, or needs help with fundable hypothesis, reviewer-friendly structure, or compliance with grant guidelines.

Use when reviewing or editing research manuscripts, journal articles, reviews, or perspectives. Invoke when user mentions manuscript, paper draft, article, research writing, journal submission, reviewer feedback, or needs to improve scientific writing clarity, structure, or argumentation in their manuscript.

Use when starting technical work requiring structured approach - writing tests before code (TDD), planning data exploration (EDA), designing statistical analysis, clarifying modeling objectives (causal vs predictive), or validating results. Invoke when user mentions "write tests for", "explore this dataset", "analyze", "model", "validate", or when technical work needs systematic scaffolding before execution.

Generate voice call reports showing transcriptions, scores, and score deltas as markdown files

Research-driven essay and post creation with thematic synthesis, citation management, and voice calibration. Use when creating Substack/LinkedIn posts, long-form essays synthesizing multiple sources, or publication-grade writing requiring web search, narrative arc, and proper attribution. Triggers include "research and write about [topic]" or "dig into this idea and write."

Implements tasks from .plans/ directories by following implementation guidance, writing code and tests, and updating task status. Use when task file is in implementation/ directory and requires code implementation with comprehensive testing. Launches research agents when stuck.

Run all configured linters including mojo format, markdownlint, and pre-commit hooks. Use before committing code to ensure quality standards are met.

Testing TDD & BDD - Atoll Tourisme. Use when writing tests, reviewing test coverage, or setting up testing.

Generate comprehensive plan documentation following Template 1 format. Use when creating plan.md files for new components or subsections.

Rule 07: Testing. Use when writing tests, reviewing test coverage, or setting up testing.

Stratégie de Tests React. Use when writing tests, reviewing test coverage, or setting up testing.

Testing Flutter - Stratégie Complète. Use when writing tests, reviewing test coverage, or setting up testing.