technical▌

Generates comprehensive technical documentation tailored to any audience and documentation type. \n \n Supports nine documentation formats: user guides, API docs, system architecture, tutorials, troubleshooting guides, READMEs, release notes, onboarding materials, and knowledge base articles \n Automatically identifies audience level (beginner, intermediate, expert) and adjusts technical depth, terminology, and examples accordingly \n Structures content with clear headings, step-by-step instruct

This skill enables comprehensive technical analysis of weekly price charts. Analyze chart images to identify trends, support and resistance levels, moving average relationships, volume patterns, and develop probabilistic scenarios for future price movement. All analysis is conducted objectively using only chart data, without influence from news, fundamentals, or market sentiment.

Classical and quantitative technical analysis combining price action, patterns, and validated indicators. \n \n Covers Wyckoff/Dow theory, candlestick patterns, and multi-timeframe confluence with emphasis on statistical validation over subjective interpretation \n Analyzes volume profile, market structure, Fibonacci applications, and failed patterns as reversal signals \n Prioritizes price action and volume confirmation over lagging indicators; treats support/resistance as probability zones, no

Structured technical blog writing for developers with templates, code examples, and distribution guidance. \n \n Covers five post types: tutorials, deep dives, postmortems, benchmarks, and architecture posts, each with specific structure and word count targets \n Includes detailed rules for developer-friendly voice, code formatting, explanation depth, and what to avoid (filler language, dismissive tone, broken examples) \n Provides templates for ideal post structure, diagram generation via CLI,

Create comprehensive technical specifications that define system requirements, architecture, implementation details, and acceptance criteria for software projects.

Time-boxed technical spike documents for researching critical development decisions before implementation. \n \n Generates structured markdown spike files with clear objectives, research questions, investigation plans, and decision frameworks \n Supports six spike categories: API Integration, Architecture & Design, Performance & Scalability, Platform & Infrastructure, Security & Compliance, and User Experience \n Includes built-in checklists for research tasks, success criter

You are an expert software developer creating technical content for other developers. Your task is to produce clear, in-depth tutorials that provide practical, implementable knowledge.

As of 2025-2026, AI companies actively crawl the web to train models and power AI search. Managing these crawlers via robots.txt is a critical technical SEO consideration.

Generates clear, user-centered documentation for APIs, READMEs, guides, and technical content. \n \n Covers five core writing principles: user-centered approach, clarity-first language, practical examples, progressive disclosure from simple to complex, and scannable formatting \n Provides ready-to-use templates for project READMEs, API documentation, and tutorials with consistent structure and formatting conventions \n Includes style guidance for voice, tone, code examples, and common patterns l

Create clear, comprehensive technical documentation for specs, architecture, runbooks, and APIs. \n \n Provides templates and step-by-step guidance for five document types: technical specifications, architecture documents, runbooks, API documentation, and changelogs \n Includes audience-specific writing strategies for developers, operations teams, managers, and end users with tailored content focus \n Offers visual aid support via Mermaid diagrams, flowcharts, tables, and code examples with synt