Back to Gallery
Google Adk (.cursorrules)
View Full Resolution
100% Free Access
AI Architecture Claude 3.7 Sonnet / Cursor
Category Coding Agents
Best Use Case Commercial & Cinematic
Coding Agents AI Agent System Prompt

Google Adk (.cursorrules)

# Google ADK Rules ## Agent Design - Keep each agent focused on a clear goal, persona, and tool set. - Use LLM agents for flexible reasoning...

Quick Answer (Voice / AI Overview) Here is the verified Google Adk (.cursorrules) prompt for Claude 3.7 Sonnet / Cursor under the Coding Agents category. You can copy the full JSON blueprint on JsonPrompts.in for free.
Ready-to-Run Prompt
100% Free Copy
# Google ADK Rules ## Agent Design - Keep each agent focused on a clear goal, persona, and tool set. - Use LLM agents for flexible reasoning and workflow agents for deterministic orchestration. - Write instructions that define task boundaries, tool-use rules, and escalation behavior. - Split multi-agent systems by responsibility rather than by implementation convenience. - Keep model choices configurable. ## Tools - Give tools narrow, typed inputs and outputs. - Validate tool arguments before performing side effects. - Keep secrets, credentials, and privileged APIs out of agent prompts. - Handle tool errors explicitly and return actionable failure messages. - Be aware of ADK tool limitations; some built-in tools cannot be combined with other tools on the same agent. ## Sessions, State, and Memory - Use session state for current-conversation data. - Use memory for cross-session recall and retrieval. - Keep state small and serializable. - Do not store large files or binary payloads in session state. - Make state keys stable and documented. ## Artifacts - Use artifacts for generated files, uploaded files, reports, images, audio, and other binary data. - Configure an artifact service in the runner before relying on artifact operations. - Version artifact filenames intentionally and avoid overwriting semantically different outputs. - Store only references or summaries in state when full content belongs in artifacts. ## Evaluation and Deployment - Add tests for tool behavior, agent routing, - Use trace or event logs to debug agent decisions. - Keep local development, staging, and production configuration separate. - Add observability for latency, tool failures, token use, and handoff failures. ## Common Mistakes - Do not make one agent responsible for every workflow. - Do not let tools accept arbitrary shell, SQL, or HTTP input without validation. - Do not rely on - Do not hide important side effects behind generic tool names.

Structured JSON Schema

Use with automated API pipelines, LangChain, or custom image generators

{
    "prompt": "# Google ADK Rules ## Agent Design - Keep each agent focused on a clear goal, persona, and tool set. - Use LLM agents for flexible reasoning and workflow agents for deterministic orchestration. - Write instructions that define task boundaries, tool-use rules, and escalation behavior. - Split multi-agent systems by responsibility rather than by implementation convenience. - Keep model choices configurable. ## Tools - Give tools narrow, typed inputs and outputs. - Validate tool arguments before performing side effects. - Keep secrets, credentials, and privileged APIs out of agent prompts. - Handle tool errors explicitly and return actionable failure messages. - Be aware of ADK tool limitations; some built-in tools cannot be combined with other tools on the same agent. ## Sessions, State, and Memory - Use session state for current-conversation data. - Use memory for cross-session recall and retrieval. - Keep state small and serializable. - Do not store large files or binary payloads in session state. - Make state keys stable and documented. ## Artifacts - Use artifacts for generated files, uploaded files, reports, images, audio, and other binary data. - Configure an artifact service in the runner before relying on artifact operations. - Version artifact filenames intentionally and avoid overwriting semantically different outputs. - Store only references or summaries in state when full content belongs in artifacts. ## Evaluation and Deployment - Add tests for tool behavior, agent routing, - Use trace or event logs to debug agent decisions. - Keep local development, staging, and production configuration separate. - Add observability for latency, tool failures, token use, and handoff failures. ## Common Mistakes - Do not make one agent responsible for every workflow. - Do not let tools accept arbitrary shell, SQL, or HTTP input without validation. - Do not rely on - Do not hide important side effects behind generic tool names.",
    "model": "Claude 3.7 Sonnet / Cursor",
    "aspect_ratio": "1:1",
    "category": "Coding Agents",
    "content_type": "coding_prompt",
    "surface": "agents_hub",
    "quality_score": 83,
    "provenance": "SYSTEM_RULE"
}

Voice Search & FAQs

Natural voice queries and direct answers for Siri, Google Assistant & Perplexity

"What is the best Coding Agents prompt for Claude 3.7 Sonnet / Cursor?"

The Google Adk (.cursorrules) blueprint is optimized for Claude 3.7 Sonnet / Cursor to produce high-precision output with verified JSON formatting.

"How do I prompt Claude 3.7 Sonnet / Cursor for Google Adk (.cursorrules)?"

Use the verified Google Adk (.cursorrules) prompt from JsonPrompts.in. Copy the prompt or structured JSON blueprint and paste it directly into Claude 3.7 Sonnet / Cursor.

"Where can I find free Claude 3.7 Sonnet / Cursor prompt templates for Coding Agents?"

JsonPrompts.in offers free verified Coding Agents JSON prompt blueprints including Google Adk (.cursorrules), with zero sign-up required.

Internal Discovery

More Coding Agents Prompts

View All →