文件

Use when Go concurrency with goroutines, channels, and sync patterns. Use when writing concurrent Go code.

Use when writing technical documentation, READMEs, or project documentation in markdown. Covers structure, conventions, and best practices.

Use when writing effective BDD scenarios including acceptance criteria, edge cases, and scenario organization. Use when defining behavior specifications.

Manage Navigator task documentation - create implementation plans, archive completed tasks, update task index. Use when user starts new feature, completes work, or says "document this feature".

Load Navigator documentation navigator when starting development session, resuming work, or beginning new feature. Use when user mentions starting work, beginning session, resuming after break, or checking project status.

Initialize Navigator documentation structure in a project. Auto-invokes when user says "Initialize Navigator", "Set up Navigator", "Create Navigator structure", or "Bootstrap Navigator".

Sets up and manages alerts for critical SEO and GEO metrics including ranking drops, traffic changes, technical issues, and competitor movements. Enables proactive monitoring and quick response to issues.

Performs technical SEO audits covering site speed, crawlability, indexability, mobile-friendliness, security, and structured data. Identifies technical issues preventing optimal search performance.

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

Generate a structured learning guide for building a feature using the Pólya problem-solving method. Creates a self-contained Markdown document that guides the user through understanding, planning, executing, and reflecting on the implementation. Triggers on phrases like "create a solveit guide", "make a learning guide for", "solveit for", "guided problem-solving for", or when the user wants a documented curriculum for building a feature rather than real-time teaching.

Frontend-specific technical decision criteria, anti-patterns, debugging techniques, and quality check workflow. Use when making frontend technical decisions or performing quality assurance.

Essay writing skill. Triggers on: essay, draft, write, outline

Frontend testing rules with Vitest, React Testing Library, and MSW. Includes coverage requirements, test design principles, and quality criteria. Use when writing frontend tests or reviewing test quality.

Language-agnostic testing principles including TDD, test quality, coverage standards, and test design patterns. Use when writing tests, designing test strategies, or reviewing test quality.

Technical decision criteria, anti-pattern detection, debugging techniques, and quality check workflow. Use when making technical decisions, detecting code smells, or performing quality assurance.

Documentation creation criteria including PRD, ADR, Design Doc, and Work Plan requirements with templates. Use when creating or reviewing technical documents, or determining which documents are required.

Use when writing or changing tests, adding mocks, or tempted to add test-only methods to production code - prevents testing mock behavior, production pollution with test-only methods, and mocking without understanding dependencies

Guide requirement writing, user story creation, and feature specification.Use when: writing requirements, user stories, issues, feature planning.Keywords: requirement, user story, issue, feature, specification, 需求, 功能規劃, 規格.

Semantic versioning and changelog formatting for software releases.Use when: preparing releases, updating version numbers, writing changelogs.Keywords: version, release, changelog, semver, major, minor, patch, 版本, 發布, 變更日誌.

Guide documentation structure, README content, and project documentation best practices.Use when: creating README, documentation, docs folder, project setup.Keywords: README, docs, documentation, CONTRIBUTING, CHANGELOG, 文件, 說明文件.