Prompt Library: Collection of prompts for developers to use with AI tools

Intuit has released a prompt library for developers to use with AI tools, organizing reusable prompts by workflow and topic to help teams adapt to platform changes and implement new features. The library is tool-agnostic and includes recipes for API discovery, webhook migration, and other tasks, with support for referencing prompts via @file syntax in IDEs.

Collection of reusable prompts for Intuit developers to use with AI tools. This library organizes prompts by workflow and topic so you can quickly find, copy, and adapt them in your own development work. The goal of this prompt library is to help you quickly adapt to platform changes and implement new features. Prompt recipes written in plain Markdown. Organized by workflow/topic , e.g. discovery, change management, migrations, etc. Tool‑agnostic : you can use them with any AI assistant IDE plugin, chat UI, API, etc. . | Folder | What it does | When to use it | |---|---|---| discover/ | Intuit Enterprise Suite IES Dimensions API and Projects & Estimates API . Configure target language, transaction type, and instructions in prompt-config.json , then run node merge-prompt.js to produce a ready-to-paste prompt. workflows/webhooks-migration/ webhook handler from the legacy payload to the CloudEvents format . Supports Java, .NET, PHP, Node.js, and Python. The generated prompt detects the codebase's current state and routes to the right migration tasks.Each folder has its own README with full setup, configuration, and usage details. - Browse to a relevant folder Pick the workflow or topic that matches what you're trying to do for example, discovering APIs, managing webhooks, running a migration, etc. . - Open a prompt file Read the description at the top to confirm it fits your use case. - Copy the prompt text Copy everything under the main "Prompts" or similar heading. - Customize placeholders Replace any placeholder text for example: <your app name , <project id , <API key , or bracketed variables with your own details. - Paste into your AI tool - Paste into your IDE assistant, chat UI, or API request body. - Add any extra context code snippets, logs, links as needed. - Iterate - If the response isn't quite right, refine inputs more context, narrower scope . - Save new or refined prompt variants back into this repo if they're reusable. Many AI tools and IDE assistants let you reference local files using @ for example, @filename or @path/to/file . You can use this pattern with this prompt library. - Get the prompts into your workspace - Clone the repo, or - Copy the specific .md files you need into your project for example: prompts/ , .prompt/ , or any folder your tool can see . - Open your AI tool in the same workspace - For IDE assistants, ensure the project that contains the .md prompts is open. - For CLI or other tools, point them at the folder where the prompts live. - For IDE assistants, ensure the project that contains the - Reference a prompt with @ - In your AI chat, type something like: @workflows/webhooks-migration/prompt-template.md - or shorter, if your tool supports it: @prompt-template.md - The exact syntax depends on your tool, but typically: @file-name → references a file in the repo. @path/to/file.md → references a nested file. - In your AI chat, type something like: - Add instructions on top of the @ reference- Example: @workflows/webhooks-migration/prompt-template.md Use this prompt and apply it to my current Java service. Assume Gradle and Spring Boot. - Example: - Edit prompts locally if needed - Tweak the .md file to better match your app or environment. - Re‑run the same @file reference; your tool will pick up the updated content. - Tweak the Note:Exact @ behavior varies by tool. If @file doesn't work, check your AI/IDE assistant's docs for how it resolves local file references. Be specific : give concrete details stack, language, framework, API version . Include context : link or paste relevant code, logs, or docs. Keep scope small : ask for one clear outcome at a time e.g., "design a migration plan" before "implement everything" . Treat prompts as templates : tweak wording to match your own voice and needs.