brainstorming
You MUST use this before any writing work - creating blog posts, technical documentation, reports, or any content. Explores topic intent, audience, and purpose before writing.
38,472 Skills
搜索范围为本次公开目录;榜单和数量均为记录时的数据。
You MUST use this before any writing work - creating blog posts, technical documentation, reports, or any content. Explores topic intent, audience, and purpose before writing.
Complete document writing workflow with four stages: brainstorming → planning → execution → review. Use when user wants to write articles, blog posts, technical docs, or any long-form content.
Executes approved article plan section by section with validation checkpoints. Batch writing mode with human review.
Multi-pass article review covering logic, evidence, flow, and polish. Systematic quality assurance before publication.
Use when you have an approved topic brief. Creates detailed article outline with section structure, key points, word counts, and research needs before writing.
Prepare iOS and Android app submissions. Use for store review, ASO, privacy forms, or rejection remediation. Read README.md for the guide map.
Playwright and Puppeteer automation for deterministic browser tests, debugging, downloads, screenshots, and browser lifecycle control. Use for browser automation work.
Chrome DevTools Protocol and Chromium development for remote debugging, profiles, protocol inspection, source builds, and browser-engine diagnosis. Use for Chrome or Chromium engineering.
Electron application engineering for process boundaries, preload APIs, IPC, sandboxing, packaging, updates, and desktop verification. Use for Electron app implementation or review.
Build Wails v2 desktop apps around Go backends: typed bindings, lifecycle, storage, native builds and package evidence. Use after Wails is explicitly selected.
Go specialist for modules, toolchains, vendoring and fork-in-tree freezes, cgo .so plugin ABI, project layout, and builds. Use for go.mod, replace directives, vendoring upstream repos, plugin crashes.
Prepare an app's Library, contracts, schema and bounded wave-plan handoff before implementation.
Scope and build an authorized desktop-app slice with an explicit native boundary and native verification.
Build the server side of a mobile product with accepted identity, API compatibility and unreliable-network contracts.
Recommend one backend language/runtime from workload, integration, operations and actual implementation coverage.
Choose one desktop architecture with native boundary, operating-system support, persistence, update and release evidence.
目录记录日期:2026-11-21