A curated collection of system prompts and tool definitions from production AI coding agents. Benefits operations teams by providing pre-built prompts for AI agents, reducing setup time and improving consistency. Connects to Claude agents and integrates with Jinja templating for customization.
git clone https://github.com/tallesborges/agentic-system-prompts.gitThe agentic-system-prompts library documents system prompts, tool definitions, and design patterns from production AI coding agents including Claude Code, Gemini CLI, Cline, Aider, Roo Code, Zed, and Codex CLI. Each agent directory includes complete prompt templates, detailed tool API specifications, and source attribution to help developers understand how professional agentic systems structure instructions and capabilities. This collection provides research value for prompt engineering patterns, tool design approaches, safety measures, and user experience workflows across different agent implementations. Operations and development teams can use these documented prompts as reference material or starting points for building consistent, reliable AI agent configurations.
[{"step":1,"action":"Select a system prompt from the curated collection (e.g., `refactor-service-component`, `debug-performance-issue`, `generate-api-docs`).","tip":"Use prompts tagged for your tech stack (e.g., 'Spring Boot', 'React Native') to ensure compatibility."},{"step":2,"action":"Customize the prompt template by replacing [PLACEHOLDERS] with your task details (e.g., [TASK_DESCRIPTION], [CONSTRAINTS]).","tip":"For dynamic inputs, use Jinja templating (e.g., `{{ project_name }}` → `auth-service`)."},{"step":3,"action":"Deploy the prompt to your AI agent (e.g., Claude, Cursor, or custom agent). Ensure the agent has access to the required tools (e.g., `dependency-graph-tool`, `maven-wrapper`).","tip":"Test the agent in a sandbox environment first to validate tool outputs and constraints."},{"step":4,"action":"Monitor the agent’s execution log. Review outputs for accuracy, and use the documented steps to verify changes or debug issues.","tip":"For complex tasks, break the workflow into smaller subtasks and use separate prompts for each phase."},{"step":5,"action":"Integrate the agent’s outputs into your workflow (e.g., auto-generate PR descriptions, update documentation, or trigger CI/CD pipelines).","tip":"Use the agent’s structured output (e.g., JSON, Markdown) to automate downstream processes like ticket updates or Slack notifications."}]
Reference prompt engineering patterns from production AI agents
Compare tool capabilities and designs across different agentic platforms
Understand safety measures and defensive programming in AI agent systems
Accelerate development by studying established agent workflows
No install command available. Check the GitHub repository for manual installation instructions.
git clone https://github.com/tallesborges/agentic-system-promptsCopy the install command above and run it in your terminal.
Launch Claude Code, Cursor, or your preferred AI coding agent.
Use the prompt template or examples below to test the skill.
Adapt the skill to your specific use case and workflow.
You are an AI coding agent with access to [TOOLS]. Follow the system prompt below to complete the task: [SYSTEM_PROMPT] Task: [TASK_DESCRIPTION]. Use the provided tools to achieve the goal. Document your steps and reasoning in a [FORMAT]. Constraints: [CONSTRAINTS_IF_ANY]. Context: [ADDITIONAL_CONTEXT].
### AI Agent Execution Log **Agent ID:** dev-agent-01 **Task:** Refactor the legacy authentication module in the `auth-service` repository to use dependency injection. **System Prompt Used:** `refactor-service-component` **Step 1: Analyze Current Code** - Scanned `auth-service/src/main/java/com/example/auth/` (24 files, 1,200 LOC). - Identified 8 classes with hardcoded dependencies (e.g., `UserRepository`, `TokenService`). - Detected circular dependencies in `AuthController` → `UserService` → `TokenService` → `AuthController`. **Step 2: Generate Refactor Plan** - Created dependency graph using `dependency-graph-tool`. - Proposed 3 refactor phases: 1. Extract interfaces for `UserRepository` and `TokenService`. 2. Implement constructor injection in `AuthService`. 3. Resolve circular dependencies via setter injection. **Step 3: Execute Refactor** - Modified `UserRepositoryImpl.java` to implement `UserRepository` interface. - Updated `AuthService.java` to accept `UserRepository` and `TokenService` via constructor. - Resolved circular dependency by introducing `@Lazy` annotation on `TokenService`. **Step 4: Validate Changes** - Ran `mvn clean test` (100% pass rate, 0 regressions). - Verified dependency injection with `spring-boot-actuator` metrics. - Logged changes in `CHANGELOG.md` with Jira ticket reference: `AUTH-456`. **Output:** - Refactored code pushed to `feature/auth-refactor` branch. - Pull request description auto-generated with tool output. - Slack notification sent to #dev-team channel with link to PR.
IronCalc is a spreadsheet engine and ecosystem
Get more done every day with Microsoft Teams – powered by AI
Enterprise workflow automation and service management platform
Automate your spreadsheet tasks with AI power
Agentic AI Workflow platform
Connected workspace for docs, wikis, and projects
Take a free 3-minute scan and get personalized AI skill recommendations.
Take free scan