Technical Writing

Generate concise CLAUDE.md files and agent documentation following best practices. Use when setting up a new project for Claude Code, auditing existing CLAUDE.md, or creating progressive disclosure documentation structure.

Validate markdown files for formatting, links, and style compliance using markdownlint. Use before committing documentation changes.

Use proactively when you need to implement features or fix bugs using strict Test-Driven Development (TDD) methodology. This agent should be activated for any coding task that requires writing new functionality, refactoring existing code, or ensuring comprehensive test coverage, but should not be used for any design-related tasks. The agent excels at breaking down complex requirements into testable increments and maintaining high code quality through disciplined TDD cycles. Use this agent proactively or if the user mentions 'TDD', 'tdd' or 'Test Driven Development'.

Context-driven development methodology for organized, spec-first coding. Use when:- Project has a `conductor/` directory- User mentions specs, plans, tracks, or context-driven development- Files like `conductor/tracks.md`, `conductor/product.md`, `conductor/workflow.md` exist- User asks about project status, implementation progress, or track management- User wants to organize development work with TDD practices- User invokes `/conductor-*` commands (setup, newtrack, implement, status, revert, validate, block, skip, revise, archive, export, refresh)- User mentions documentation is outdated or wants to sync context with codebase changesInteroperable with Gemini CLI extension and Claude Code commands.Integrates with Beads for persistent task memory across sessions.

Z.AI CLI providing:- Vision: image/video analysis, OCR, UI-to-code, error diagnosis (GLM-4.6V)- Search: real-time web search with domain/recency filtering- Reader: web page to markdown extraction- Repo: GitHub code search and reading via ZRead- Tools: MCP tool discovery and raw calls- Code: TypeScript tool chainingUse for visual content analysis, web search, page reading, or GitHub exploration. Requires Z_AI_API_KEY.

Use when writing or polishing professional scientific emails, journal cover letters, or responses to reviewers. Invoke when user mentions email to collaborator, cover letter to editor, reviewer response, professional correspondence, or needs help with professional tone, clear asks, or diplomatic communication in academic/scientific contexts.

N8N Documentation - Workflow automation platform with AI capabilities

Linode API Documentation

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

Explore open-source repositories, analyze implementation details of libraries/frameworks, and research official documentation. Use when you need to understand how features are implemented in popular open-source projects.

Polish writing to professional excellence through systematic craft analysis with multi-layer assessment of rhythm, voice, and commitment. Use when refining drafts, analyzing text for AI patterns or craft weaknesses, generating quality content, or teaching writing principles. Handles all writing types including long-form, business, technical, academic, and creative content.

Idiomatic Go 1.25+ development. Use when writing Go code, designing APIs, discussing Go patterns, or reviewing Go implementations. Emphasizes stdlib, concrete types, simple error handling, and minimal dependencies.

Notion API for managing pages, databases, and blocks. Use this skill to create pages, query databases, search content, and build integrations with Notion workspaces.

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'