Claude Skills

Guide users step-by-step through manually testing whatever is currently being worked on. Use when asked to "test this", "verify it works", "let's test", "manual testing", "QA this", "check if it works", or after implementing a feature that needs verification before proceeding.

Analyzes git changes and creates a new branch with an appropriate name following naming conventions. Use when creating new branches from current changes.

Expert guidance for Next.js Cache Components and Partial Prerendering (PPR). **PROACTIVE ACTIVATION**: Use this skill automatically when working in Next.js projects that have `cacheComponents: true` in their next.config.ts/next.config.js. When this config is detected, proactively apply Cache Components patterns and best practices to all React Server Component implementations. **DETECTION**: At the start of a session in a Next.js project, check for `cacheComponents: true` in next.config. If enabled, this skill's patterns should guide all component authoring, data fetching, and caching decisions. **USE CASES**: Implementing 'use cache' directive, configuring cache lifetimes with cacheLife(), tagging cached data with cacheTag(), invalidating caches with updateTag()/revalidateTag(), optimizing static vs dynamic content boundaries, debugging cache issues, and reviewing Cache Component implementations.

Best practices for creating custom slash commands with frontmatter, arguments, bash execution, and file references. Use when creating slash commands.

Search and retrieve official Microsoft documentation, code samples, and technical information. Use PROACTIVELY when researching Azure AI Search, Copilot Studio, Azure Cognitive Services, Azure App Service, Microsoft 365, Power Platform, Power Automate, or Power Apps. Trigger on: "how do I implement", "what is the difference", "how does this feature work", "Azure", "Microsoft", "Copilot", "Power Platform", or when official docs links and code examples are needed. Always include source URLs from Microsoft Learn.

This skill should be used when the user asks to "understand context", "explain context windows", "design agent architecture", "debug context issues", "optimize context usage", or discusses context components, attention mechanics, progressive disclosure, or context budgeting. Provides foundational understanding of context engineering for AI agent systems.

Leave notes on files for other agents to see in future sessions. Use after making non-obvious changes, fixing tricky bugs, or when code looks wrong but is intentional.

Expert guidance for Next.js Cache Components and Partial Prerendering (PPR). **PROACTIVE ACTIVATION**: Use this skill automatically when working in Next.js projects that have `cacheComponents: true` in their next.config.ts/next.config.js. When this config is detected, proactively apply Cache Components patterns and best practices to all React Server Component implementations. **DETECTION**: At the start of a session in a Next.js project, check for `cacheComponents: true` in next.config. If enabled, this skill's patterns should guide all component authoring, data fetching, and caching decisions. **USE CASES**: Implementing 'use cache' directive, configuring cache lifetimes with cacheLife(), tagging cached data with cacheTag(), invalidating caches with updateTag()/revalidateTag(), optimizing static vs dynamic content boundaries, debugging cache issues, and reviewing Cache Component implementations.

JPA/Hibernate patterns for entity design, relationships, query optimization, transactions, auditing, indexing, pagination, and pooling in Spring Boot.

Board meeting preparation: agenda, metrics, narrative, follow-ups. Use when preparing for a board meeting.

Get the current Neovim context as JSON (cursor position, current file, visual selection and diagnostics) to help answer questions about code at the current cursor position, visual selections and diagnostics. Use when users ask about "this line", "current file", "selection" or need context about their Neovim editor state.

This skill should be used when the user asks to "generate tasks from a spec", "break down a spec", "create tasks from a PRD", "decompose requirements", "generate a task list from a design document", or mentions working from specification documents. Provides guidance for transforming specifications into structured, actionable task lists organized under missions.

故事創作：小說寫作、漫畫腳本、影片企劃、敘事結構、角色塑造

Creates isolated git worktree environments for parallel development. Fetches latest from default branch, creates worktree in .git-worktrees/, copies .env and .serena files. Branch '/' is converted to '-'. Use when starting new features or switching context.

Create GitHub pull requests with standardized title format and draft status. Use when the user requests to create a PR. This skill uses gh command to create PRs with specific title format '[base-branch] type: description' and generates concise bullet-point descriptions from git changes.

Provides best practices and guidelines for creating Claude Code skills. Use when you need help with skill structure, naming conventions, writing effective descriptions, progressive disclosure patterns, and evaluation methods.

PocketFlow framework for building LLM applications with graph-based abstractions, design patterns, and agentic coding workflows

Stakeholder briefs for board, investors, or exec team: status, decisions, asks. Use when creating a brief for board, investors, or exec team.

Process call notes or transcripts into structured summaries, action items, and follow-up emails. Works standalone with pasted notes or transcript; supercharged when you connect ~~conversation intelligence~~, ~~CRM~~, ~~email~~, or ~~calendar~~. Trigger with "summarize this call", "extract action items from this transcript", or use the /summarize-call command.