Documentation

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.

Comprehensive Supabase expert with access to 2,616 official documentation files covering PostgreSQL database, authentication, real-time subscriptions, storage, edge functions, vector embeddings, and all platform features. Invoke when user mentions Supabase, PostgreSQL, database, auth, real-time, storage, edge functions, backend-as-a-service, or pgvector.

FIRST STEP - Assess task complexity (0-20 score) and output orchestration level (0-3). Use for ANY non-trivial task BEFORE execution. Scores across scope, time, agents, dependencies, documentation. Level 0 (0-2 direct), Level 1 (3-7 single agent), Level 2 (8-14 multi-agent), Level 3 (15-20 epic). Outputs recommendation then exits. NOT for execution or agent selection (use agent-selector after).

Use the Svelte MCP server tools for Svelte 5 and SvelteKit documentation, code analysis, and playground links

Generate initial project planning documents (PVS, ADR, Tech Spec, Roadmap) from a project concept description. Use when starting a new project, when docs/planning/ contains placeholder files, or when user requests project planning document generation.

Deep code review with web research. USE WHEN user says 'double check against latest', 'verify versions', 'check security'. Complements automatic quality hook with ecosystem verification.

Enterprise Notion integration with MCP server architecture, database operations, and content management

Quick reference for common SQL patterns, CTEs, window functions, and indexing strategies. Triggers on: sql patterns, cte example, window functions, sql join, index strategy, pagination sql.

Comprehensive architectural analysis and evaluation framework for system architecture assessment. Use for architecture pattern identification, SOLID principles evaluation, coupling/cohesion analysis, scalability assessment, performance characteristics, security architecture, data architecture, microservices vs monolith, technical debt quantification, and ADRs. Includes C4 model, 4+1 views, QAW, ATAM, architectural fitness functions, and visualization tools.

Synchronize knowledge base documentation with current codebase implementation. Performs full, incremental, or targeted audits of source code and updates code maps, PRDs, patterns, SOPs, and user-facing docs to match reality. Use when: - After major refactors - Periodic maintenance (monthly) - Before starting new phase of work - When docs feel stale - User says "update kb", "sync docs", "audit docs"

Use when requesting or receiving code reviews - covers dispatching review subagent, handling feedback with technical rigor, and avoiding performative agreement

Anti-premature-coding protocol. MANDATORY pre-coding checkpoint: execute BEFORE writing ANY code (new features, bug fixes, refactoring, optimization, tests). Use when user requests: "implement/add/fix/refactor/optimize/create feature". Prevents "coding without reading" blindspot that causes most bugs, duplicated work, and broken architectures. Forces systematic investigation via Stop→Trace→Orient→Plan before touching keyboard.

Transform SEO micro-audits into high-converting cold emails with zero jargon. Generates 2-3 email variations (customer perspective, competitor comparison, benefit-first) for e-commerce, local service, or B2B prospects. Translates technical SEO findings into business language, includes specific numbers and competitor comparisons, and positions Riflebird Agency as lean team of experts. Use when you have a completed SEO audit and need to create personalized cold outreach emails.

Generate comprehensive specification documents including requirements, technical design, and detailed task breakdown from any feature request. Use when the user asks to create specs, requirements docs, design docs, or needs to break down a feature into implementation tasks. Perfect for planning new features, understanding system architecture, or preparing work for AI coding agents.