Documentation

Rust coding standards (Japanese comments required, error handling, logging, naming conventions). Use when writing new code, adding error handling, logging, fixing errors, asking about coding style, thiserror, tracing, naming conventions, or code review.

Use when writing or reviewing technical documentation to follow Google's documentation style guide - https://developers.google.com/style

Write vanilla JavaScript for Web Components with functional core, imperative shell. Use when creating JavaScript files, building interactive components, or writing any client-side code.

Frappe server-side Python patterns for controllers, document events, whitelisted APIs, background jobs, and database operations. Use when writing controller logic, creating APIs, handling document events, or processing data on the server.

Expert knowledge for writing cutting-edge, idiomatic Rust code with Rust Edition 2024, strict clippy compliance, and functional-but-pragmatic philosophy. Use when writing any Rust code, fixing clippy warnings, structuring modules or crates, reviewing or refactoring Rust code, or questions about Rust 2024 features, async patterns, documentation standards, or performance optimization.

Develop with Analogjs 2.x file-based routing, markdown content management, and SSR/SSG configuration. Use when creating *.page.ts files, contentFilesResource, routeMeta, and prerender settings.

Generates comprehensive documentation and API references

Use when receiving feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

Extract API request/response schema from Korean Public Data Portal (data.go.kr) documentation pages and generate structured JSON representation

Technical analysis with TA-Lib - Moving averages, RSI, MACD, Bollinger Bands, Stochastic, ATR, candlestick patterns, and strategy signals using OpenAlgo market data

Load when creating tutorials, explaining technical concepts, writing documentation,or any content that involves code, data, or technical procedures. Containsguidelines for clear, effective technical communication based on Google'stechnical writing principles.

Technical workflow for implementing accessible React user interfaces with shadcn/ui, Tailwind CSS, and TanStack Query. Includes 6-phase process with mandatory Style Guide compliance, Context7 best practices consultation, Chrome DevTools validation, and WCAG 2.1 AA accessibility standards. Use after Test Agent, Implementer, and Supabase agents complete their work.

Infrastructure operations - 1Password secrets, Coolify deployments, Postman tests, Hetzner/Hostinger servers

This skill should be used when the user asks to 'create an article', 'add a blog post', 'modify frontmatter', 'add a category', or 'update content schema'. Provides guidance for MDX articles, content-collections, and static content data in content/articles/*.mdx, content/data/*.ts, content-collections.ts.

Transforms workflow to use Manus-style persistent markdown files for planning, progress tracking, and knowledge storage. Use when starting complex tasks, multi-step projects, research tasks, or when the user mentions planning, organizing work, tracking progress, or wants structured output.

Technical leadership guidance for architecture decisions, team scaling, tech debt, and engineering strategy. Use PROACTIVELY for technology evaluation, engineering metrics, team structure, or strategic technical decisions.

Format, beautify, and optimize report content.LOAD THIS SKILL WHEN: User says "整理報告", "格式化", "美化報告", "polish report" | after report generation | need professional formatting.CAPABILITIES: Markdown formatting, grammar check, structure optimization, emoji/table/code block styling.

Expert guidance for writing proper Svelte 5 code with runes-based reactivity. Use when writing Svelte 5 components, migrating from Svelte 4, or troubleshooting Svelte 5 syntax. Covers $state, $derived, $effect, $props, $bindable, event handling, snippets, TypeScript integration, and common pitfalls.

Comprehensive SaaS planning system for solo developers using Next.js + Supabase + Stripe stack. Converts ideas into shippable subscription products with scope control, feature prioritization, billing architecture, technical roadmap, and anti-feature-creep mechanisms. Generates PRDs with subscription models, pricing strategies, and Claude Code starter prompts. Use when planning SaaS products, subscription apps, or when user mentions billing, payments, recurring revenue, or subscription models.

Write focused tests for core user flows and critical paths using Pest framework, with minimal tests during development and strategic coverage at completion points. Use this skill when creating or editing test files in tests/Feature/ or tests/Unit/ directories, when writing Pest tests with descriptive names, when testing critical user workflows and business logic, when mocking external dependencies, when implementing fast unit tests, when testing behavior rather than implementation details, or when deciding what needs test coverage at feature completion.