文件

Your approach to handling readme. Use this skill when working on files where readme comes into play.

文档审核与修订工程师 (Documentation Reviewer & Fixer)。审核 ASDD 层文档的 SoT 合规性，发现问题并提供修订方案。何时使用: 当需要检查文档与 SoT 的一致性、修复文档问题、或审计文档质量时。

日本語技術文書の作成・修正を支援し、textlintによる自動校正と手動での改善提案を行います。文章を執筆した際は必ずこのスキルを使って文章をレビューして改善します。必要に応じてユーザに改善案を提案します

Enforce elite code quality standards for F3 Workout Builder. Use when writing code, reviewing changes, fixing bugs, or creating new features. Keywords: code quality, TypeScript, testing, coverage, lint, types.

Enterprise Nextra documentation framework with Next.js

Deep search mode - parallel multi-source search across codebase, docs, and web

Bitcoin trading simulation with technical analysis (EMA/RSI/Bollinger), Monte Carlo projections, and Telegram alerts. Cambodian market focus (USD/KHR 4050).TRIGGERS: BTC backtesting, indicator calculations, Fear & Greed integration, crypto strategy development, CoinGecko/Alternative.me APIs, portfolio simulation, trailing stop optimization, Sharpe/drawdown metrics.ENTRY POINTS: btc_trader.py (365d backtest), btc_simulation.py (60d Monte Carlo), backtest_runner.py (advanced metrics).

Complete implementation guide for the DocsSidebar v2 (React Complex Tree + Convex + Liveblocks + AI).

Guide for authoring, creating, writing, building, reviewing, or improving slash commands that delegate to agents or skills. Use when designing /commands for user shortcuts, fixing existing commands, or learning command best practices. Helps design simple command files, choose delegation targets, handle arguments, and decide when to use commands vs skills. Also triggers when asking how to create commands, whether to use a command vs skill, or understanding command patterns. Expert in command patterns, best practices, and keeping commands focused.

Analyze argument structure, identify logical gaps, suggest evidence needs, generate counterarguments, apply claim-evidence-warrant framework. Use when strengthening arguments, analyzing persuasive writing, checking logical validity, or when user asks to improve reasoning or logic.

Documentation generation and maintenance patterns including README structure, CHANGELOG management, API documentation, wiki synchronization, and badge updates. Use when creating package docs, updat...

Creates high-quality content (blog posts, tweets, newsletters, documentation) that matches the user's writing style and voice. Performs web research to find citations and supporting evidence. Use when user requests blog posts, marketing content, newsletters, tweets, or any written content that should sound authentic and be well-researched.

Use when making technical decisions, choosing technologies, or documenting architectural choices. Creates ADRs (Architecture Decision Records).

Use when writing async/await code, enabling strict concurrency, fixing Sendable errors, migrating from completion handlers, managing shared state with actors, or using Task/TaskGroup for concurrency.

Create properly formatted references to paths (files or folders) in a git repository. Use when writing docs that need to link to any path in the repo.

Systematically explore unfamiliar codebases and document findings using Julie's code intelligence, Sherpa's exploration workflow, and Goldfish's documentation. Activates when learning new code with semantic search, architecture mapping, and persistent documentation.

Use when working with Notion databases, creating/updating pages, querying data, syncing between systems, or building knowledge management workflows

Guide for implementing Google Gemini API document processing - analyze PDFs with native vision to extract text, images, diagrams, charts, and tables. Use when processing documents, extracting structured data, summarizing PDFs, answering questions about document content, or converting documents to structured formats. (project)

Reads, creates, and updates Confluence pages via MCP. Use when working with wiki pages, documentation, knowledge bases, CQL searches, or page hierarchies in Confluence. For Jira issues, use managing-jira instead.

Use when creating or editing skills, before deployment, to verify they work under pressure and resist rationalization - applies RED-GREEN-REFACTOR cycle to process documentation by running baseline without skill, writing to address failures, iterating to close loopholes