一键在 Manus 中运行任何 Skill

google-dev-docs

星标3

分支0

更新时间2026年3月8日 20:11

This skill should be used when the user asks about official Google developer documentation, including Android, Firebase, Google Cloud, Chrome Extensions, Flutter, Dart, TensorFlow, Google AI (Gemini), web.dev, Google Ads, or Google Maps Platform. Triggers on questions like "how do I use Jetpack Compose", "Firebase Auth setup", "Cloud Run deployment guide", "Firestore security rules", "Flutter state management", "Chrome extension manifest v3", "TensorFlow model serving", "Gemini API tutorial", or troubleshooting errors from Google services.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

gorban-dev

gorban-dev/gor-dev-plugins

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

Google Developer Knowledge

Real-time access to official Google developer documentation via the Developer Knowledge API.

Tool Catalog (3 tools)

Tool	Purpose	When to Use
`search_documents`	Search across all supported Google documentation domains	Finding relevant docs by topic, API name, error message, or concept
`get_document`	Retrieve full content of a specific document by name	Reading a known document after finding it via search
`batch_get_documents`	Retrieve multiple documents in a single request (up to 100)	Deep research requiring content from several related pages

Supported Domains

Domain	Topics
Android Developers	Jetpack, Compose, Architecture, Kotlin, NDK, Play
Firebase	Auth, Firestore, Realtime DB, Cloud Functions, Crashlytics, Remote Config
Google Cloud	GKE, Cloud Run, BigQuery, Pub/Sub, IAM, Terraform on GCP
Chrome Extensions	Manifest V3, APIs, Web Store, DevTools
Flutter	Widgets, State management, Platform channels, Packages
Dart	Language, Core libraries, Package ecosystem
TensorFlow	Keras, TFLite, TF Serving, TFX pipelines
Google AI (Gemini)	Gemini API, AI Studio, Model tuning, Embeddings
web.dev	Core Web Vitals, PWA, Performance, Accessibility
Google Ads	Google Ads API, Campaign management, Reporting
Google Maps Platform	Maps SDK, Places API, Routes API, Geocoding

Critical Patterns

Document Name Format

Documents returned by search_documents include a name field (e.g., documents/firebase--firestore--manage-data--add-data). Use this exact value with get_document and batch_get_documents.

Parent Field

The search_documents tool accepts an optional parent parameter to scope searches to a specific domain. Example: search_documents(query: "auth email link", parent: "firebase"). The documents/ prefix is not needed — pass the domain key directly (e.g., android, firebase, cloud, flutter).

Effective Queries

Use specific API/class names: "Jetpack Compose LazyColumn" not "list in Android"
Include product context: "Firebase Auth email link sign-in" not "email login"
For errors, include the error text: "PERMISSION_DENIED Cloud Storage rules"
Combine topic + action: "Flutter platform channel invoke method"

Batch Limits

batch_get_documents accepts up to 100 document names per request. Group related documents for efficient retrieval.

Workflows

See workflows.md for detailed workflow patterns:

Quick Lookup
Deep Research
Code-Aware Lookup
Error Troubleshooting
Migration Guide Research

同仓库更多 Skills

同仓库

brainstorm

gorban-dev/gor-dev-plugins

Research and design a solution before implementation. Analyzes context, asks questions, proposes 2-3 approaches with trade-offs, writes a specification. For non-trivial tasks that require thinking before coding. <example> Context: User wants to discuss an implementation approach user: "what's the best way to implement payment system integration?" assistant: "Using brainstorm skill to research approaches." </example> <example> Context: User wants to think through architecture user: "let's think about how to implement caching" assistant: "Running brainstorm to analyze caching options." </example> <example> Context: Complex feature with a non-obvious solution user: "need to add offline mode, where to start?" assistant: "Starting with brainstorm — will research current architecture and propose options." </example>

2026-04-173

debug

gorban-dev/gor-dev-plugins

Systematic debugging methodology with 4 phases: root cause investigation, pattern analysis, hypothesis testing, and targeted fix. Prevents shotgun debugging and ensures fixes address causes, not symptoms. Use when something is broken, a bug is reported, an error occurs, or after 2+ failed fix attempts. This skill should be used when the user says "debug", "it's broken", "there's a bug", "not working", "error", "fix this", "why is this failing", or when multiple fix attempts have failed. <example> Context: User reports a crash user: "the app crashes when I open the profile screen" assistant: "I'll use the systematic debugging skill to investigate the root cause." <commentary> Bug report — systematic debugging prevents guessing. </commentary> </example> <example> Context: Multiple fix attempts have failed user: "I've tried fixing this three times and it still doesn't work" assistant: "Multiple attempts failed — I'll use the systematic debugging approach to find the root cause." <commentary> 3+ failed attempt

2026-04-173

implement

gorban-dev/gor-dev-plugins

Android feature implementation: creating from scratch, extending existing features, or refactoring to match the architectural standard. Automatically determines the working mode based on context. Use for any tasks involving writing/modifying Android code. <example> Context: User wants to create a new screen user: "create an authorization screen with email and password" assistant: "Using implement skill in create mode to build the auth feature." </example> <example> Context: User wants to add functionality to an existing screen user: "add pagination to the catalog screen" assistant: "Using implement skill in modify mode to extend the catalog feature." </example> <example> Context: User wants to bring code up to standard user: "refactor the profile screen to match our architecture" assistant: "Using implement skill in refactor mode to migrate the profile feature." </example> <example> Context: A list of architectural violations was received from review user: "fix the violations from the review" assistant: "

2026-04-173

plan

gorban-dev/gor-dev-plugins

Create and execute an implementation plan. Two modes: creating a granular plan (tasks of 2-5 minutes each) and step-by-step execution. Use for planning complex tasks or after brainstorm. <example> Context: User wants to plan a feature implementation user: "create a plan for the settings screen" assistant: "Using plan skill in plan mode to create a granular plan for the settings feature." </example> <example> Context: User wants to execute an existing plan user: "execute the plan from .claude/docs/android-dev/plans/2026-03-20-settings.md" assistant: "Using plan skill in execute mode for step-by-step plan execution." </example> <example> Context: User wants to break a complex task into steps user: "break down the DI migration task into steps" assistant: "Using plan skill to decompose the DI migration task into granular tasks." </example>

2026-04-173

review

gorban-dev/gor-dev-plugins

Architectural and code quality review of Android code. Two-pass check: (1) architectural rule compliance — 8 categories, (2) code quality — naming, duplication, error handling, security, performance, maintainability. Use after implementation to verify quality. <example> Context: User created a new feature and wants to check its quality user: "review the authorization feature" assistant: "Using review skill for a two-pass check of the auth feature." </example> <example> Context: User refactored code and wants to verify correctness user: "check the profile refactoring" assistant: "Using review skill to check architecture and code quality of the profile feature." </example> <example> Context: User wants to check code before committing user: "check my code before commit" assistant: "Using review skill for a full check of the modified files." </example>

2026-04-173

tdd

gorban-dev/gor-dev-plugins

Test-Driven Development workflow: RED → GREEN → REFACTOR. Write a failing test first, then write minimal code to pass it, then refactor while keeping tests green. Best for business logic (UseCases, mappers, utils, repositories), not for UI code. This skill should be used when the user says "tdd", "test first", "test driven", "red green refactor", "write tests before code", or when implementing business logic that benefits from test-first approach. <example> Context: User wants to implement a use case with TDD user: "implement the login use case with TDD" assistant: "I'll use the TDD skill — starting with a failing test for the login use case." <commentary> Explicit TDD request for business logic — perfect use case. </commentary> </example> <example> Context: User wants to add a data mapper user: "create the user mapper, let's do it test-first" assistant: "I'll use the TDD workflow — RED phase first with a test for the mapper." <commentary> Test-first request for a mapper — ideal for TDD. </commentary> </ex

2026-04-173

name	google-dev-docs
version	1.0.0
description	This skill should be used when the user asks about official Google developer documentation, including Android, Firebase, Google Cloud, Chrome Extensions, Flutter, Dart, TensorFlow, Google AI (Gemini), web.dev, Google Ads, or Google Maps Platform. Triggers on questions like "how do I use Jetpack Compose", "Firebase Auth setup", "Cloud Run deployment guide", "Firestore security rules", "Flutter state management", "Chrome extension manifest v3", "TensorFlow model serving", "Gemini API tutorial", or troubleshooting errors from Google services.

Google Developer Knowledge

Real-time access to official Google developer documentation via the Developer Knowledge API.

Tool Catalog (3 tools)

Tool	Purpose	When to Use
`search_documents`	Search across all supported Google documentation domains	Finding relevant docs by topic, API name, error message, or concept
`get_document`	Retrieve full content of a specific document by name	Reading a known document after finding it via search
`batch_get_documents`	Retrieve multiple documents in a single request (up to 100)	Deep research requiring content from several related pages

Supported Domains

Domain	Topics
Android Developers	Jetpack, Compose, Architecture, Kotlin, NDK, Play
Firebase	Auth, Firestore, Realtime DB, Cloud Functions, Crashlytics, Remote Config
Google Cloud	GKE, Cloud Run, BigQuery, Pub/Sub, IAM, Terraform on GCP
Chrome Extensions	Manifest V3, APIs, Web Store, DevTools
Flutter	Widgets, State management, Platform channels, Packages
Dart	Language, Core libraries, Package ecosystem
TensorFlow	Keras, TFLite, TF Serving, TFX pipelines
Google AI (Gemini)	Gemini API, AI Studio, Model tuning, Embeddings
web.dev	Core Web Vitals, PWA, Performance, Accessibility
Google Ads	Google Ads API, Campaign management, Reporting
Google Maps Platform	Maps SDK, Places API, Routes API, Geocoding

Critical Patterns

Document Name Format

Documents returned by search_documents include a name field (e.g., documents/firebase--firestore--manage-data--add-data). Use this exact value with get_document and batch_get_documents.

Parent Field

Effective Queries

Use specific API/class names: "Jetpack Compose LazyColumn" not "list in Android"
Include product context: "Firebase Auth email link sign-in" not "email login"
For errors, include the error text: "PERMISSION_DENIED Cloud Storage rules"
Combine topic + action: "Flutter platform channel invoke method"

Batch Limits

batch_get_documents accepts up to 100 document names per request. Group related documents for efficient retrieval.

Workflows

See workflows.md for detailed workflow patterns:

Quick Lookup
Deep Research
Code-Aware Lookup
Error Troubleshooting
Migration Guide Research