Technical Writing

Determines which MCP tools to use based on task type and complexity. Provides trigger conditions for Context7 (technical docs), Sequential Thinking (complex reasoning), Zen (multi-model consensus), Serena (code navigation), Recall (session memory), Tavily (web search), Chrome DevTools (browser automation). Use when determining which external tools apply to current task.

Write AI-scannable technical documentation.

Security best practices for Go applications. Use when writing security-sensitive code.

Generate production-ready Saloon-based API integrations for Laravel projects including connector classes, request classes, readonly DTOs, service layer methods with comprehensive error handling, and complete Pest test suites. Use this skill when integrating external APIs using Saloon, creating API request/response handlers, adding new API endpoints to existing services, building API client wrappers for third-party services, or setting up API communication with proper error handling and testing. This skill applies when working on files in app/Services/Api/, app/DataTransferObjects/Api/, creating Saloon connectors and requests, implementing API service methods, or writing API integration tests.

Professional security report generation, executive summaries, finding documentation, and remediation tracking

This skill should be used when the user asks about "Rails testing", "RSpec", "Minitest", "request specs", "system specs", "FactoryBot", "fixtures", "test coverage", "testing controllers", "testing models", "integration tests", or needs guidance on writing effective tests for Rails 7+ applications.

Gestion de la base de données Supabase pour MyGGV GPS. Utiliser pour les opérations SQL, migrations, tables et requêtes. NE PAS utiliser pour la documentation (utiliser archon-project).

Search COMSOL Multiphysics documentation. Use when asked about COMSOL, mesh refinement, boundary conditions, solvers, physics interfaces, FEM simulation, or COMSOL error messages.

Expert API research including discovery, evaluation, integration analysis, and documentation review

Co-create any professional writing through Socratic dialogue using established voice patterns

Write automated tests following a pragmatic, integration-focused philosophy. Use when writing tests for new features, writing tests for bug fixes, adding test coverage, or deciding what/how to test. Emphasizes confidence over coverage, real objects over mocks, integration over isolation, and simplicity over dogma.

Python testing framework for writing simple, scalable, and powerful tests

Complete end-of-session workflow for SheldonFS project. Handles code commits, quality checks, documentation updates, and merge process. Use when finishing a development session or feature branch.

Comprehensive writing guidance for professional documents across legal, academic, executive, and business contexts. Use when drafting, editing, or revising any document where quality prose matters: briefs, memos, law review articles, reports, client letters, contracts, executive summaries, presentations. Provides style selection, cognitive fluency techniques, structure frameworks, concision patterns, and revision checklists. Invoke when users ask to write, edit, revise, or improve documents.

Code complexity guidelines to keep cyclomatic complexity below 6 using strategy patterns or dispatch tables. Use when writing or refactoring functions with complex branching logic.

Guide for implementing MongoDB - a document database platform with CRUD operations, aggregation pipelines, indexing, replication, sharding, search capabilities, and comprehensive security. Use when working with MongoDB databases, designing schemas, writing queries, optimizing performance, configuring deployments (Atlas/self-managed/Kubernetes), implementing security, or integrating with applications through 15+ official drivers. (project)

This skill should be used when working with SLICOT (Subroutine Library In Control Theory) routines, translating Fortran 77 to C, parsing SLICOT HTML documentation, creating test cases from SLICOT examples, understanding SLICOT data formats, or planning translation priorities using dependency analysis tools.

Use when user requests automated documentation preparation. Triggers include:- Korean: "문서 준비해줘", "문서화 준비", "문서 요구사항 작성", "자동 문서화 준비"- English: "prepare documentation", "setup doc requirements", "prepare for automated docs"- Context: User wants to prepare all requirements for automated documentation generationThis skill discovers sources, defines structure, and saves complete requirements to filefor use with write-docs skill (automated generation).

CLI testing strategies and patterns for Node.js (Jest) and Python (pytest, Click.testing.CliRunner). Use when writing tests for CLI tools, testing command execution, validating exit codes, testing output, implementing CLI test suites, or when user mentions CLI testing, Jest CLI tests, pytest CLI, Click.testing.CliRunner, command testing, or exit code validation.

Testing patterns for litefs-py and litefs-django. Use when writing tests, setting up fixtures, understanding test organization, or configuring pytest marks. Triggers: test, pytest, unit test, integration test, property-based testing, hypothesis, fixtures, in-memory adapters.