Documentation

Shared resource library for Google integration skills. DO NOT load directly - provides common references (setup, API docs, error handling, authentication) and scripts used by gmail, google-docs, google-sheets, google-calendar, and future Google skills.

Use when deploying MkDocs documentation to GitHub Pages with GitHub Actions - covers Python-Markdown gotchas (indentation, footnotes, grid tables), workflow configuration, and systematic markdown fixing

Use when writing tests or implementing code. Defines RED-GREEN-REFACTOR cycle and test execution workflow.

Implements database integration patterns for Rust backends using SQLx and SeaORM. Use when setting up database connections, writing queries, defining entities, managing migrations, or configuring connection pools. Covers compile-time checked SQL, ORM patterns, and N+1 prevention.

Guide experienced developers on test structure, patterns, assertions, and test doubles for effective test-driven development

Use when you need to plan technical solutions that are scalable, secure, and maintainable.

Microsoft Pragmatic Rust FFI Guidelines. Use when working with C/C++ interop, creating cdylib, writing unsafe FFI code, or multi-DLL Rust projects.

Create professional API documentation using Hugo static site generator or Postman. Use when users need to generate API docs from OpenAPI specs, create developer portals, build interactive API explorers, or publish Postman collections. Supports multiple documentation themes and formats.

Create and maintain TYPO3 extension documentation following official TYPO3 13.x standards. Use when creating/editing Documentation/*.rst files or README.md, using TYPO3 directives (confval, versionadded, card-grid), rendering docs locally, or deploying to docs.typo3.org. By Netresearch.

Analyze feature documentation (PDF, markdown, or requirements) and create comprehensive implementation plans for DevPortfolio Portfolio app features. Use when asked to create implementation plans, analyze feature requirements, plan new sections, or design features for apps/portfolio/. Generates detailed phase-by-phase plans with entity design, core layer, components, hooks, styling, i18n, and testing checklists.

Operate the local Scribe MCP for any ~/projects/* repo; use when registering the server, setting projects, drafting ARCH/PHASE/CHECKLIST via manage_docs, or logging work with append_entry/get_project safeguards.

Comprehensive guidance for building and deploying static websites with the Astro framework.This skill should be used when asked to "create astro site", "deploy astro to firebase","set up content collections", "add mermaid diagrams to astro", "configure astro i18n","build static blog", or "astro markdown setup". Covers SSG fundamentals, Content Collections,Markdown/MDX, partial hydration, islands architecture, and deployment to Netlify, Vercel,GitHub Pages, or GCP/Firebase.

Comprehensive change tracking and audit logging system that monitors file modifications, code changes, and project evolution. Use when tracking project history, maintaining audit trails, analyzing development patterns, or when detailed change documentation is required for compliance and team collaboration.

Research topics, verify facts, check historical accuracy, and validate technical details. Use when writing non-fiction, historical fiction, or any content requiring factual accuracy.

Automatically applies when reviewing code. Ensures structured review checklist covering correctness, security, performance, maintainability, testing, and documentation.

outline.yamlなどの下書きを、テンプレートと過去の申請書を参考にして正式な文書（Markdown）に変換するスキル。「下書きを正式文書にして」「outline.yamlを正式文書にして」などの指示で発動。docxスキルを使用して過去の申請書（samples/配下）を読み込み、文体や表現を参考にする。

Test Midnight smart contracts using simulators and unit tests. Use when setting up test environments, writing contract tests, or debugging circuit behavior. Triggers on testing, simulator, unit test, or test framework questions.

Soracom testing standards (unit/contract/E2E, Root vs SAM users, 80% coverage). Use when writing tests or creating test plans.

MANDATORY for ANY questions about Acme Corp internal product codes, employee IDs, server names, project codes, or internal systems. Contains proprietary company data NOT available in public documentation.

Fix markdown linting errors in documentation files