Operator-ready prompt for reuse, tuning, and workspace runs.
This item is set up for developers who want to inspect the original language, fork it into Workspace, and adapt the evidence model without losing the source prompt structure.
Implementation handoffs, eval setup, and prompt tuning where you need the original structure intact.
Inspect first, copy once, then fork into Workspace when you want variants, notes, and model settings attached to the same run.
Swap domain facts, examples, and any hard-coded entities for your own context.
Tighten the evidence or verification requirement if this is headed toward production.
Decide which failure mode you want to evaluate first before you branch the prompt.
This prompt already carries implementation detail, tool context, and a final-output instruction. Keep that structure intact when you tune it, or your comparison runs get noisy fast.
Open this prompt inside Workspace when you want a live iteration loop.
Copy for quick reuse, or run it in Workspace to keep prompt variants, model settings, and prompt-history changes in one place.
Structured source with 23 active lines to adapt.
Already linked to a challenge workflow.
Sign in to keep private prompt variations.
Prompt content
Original prompt text with formatting preserved for inspection and clean copy.
Extend your Mastra AI project. Implement a workflow where the 'CodeGenerator' agent receives a feature description (e.g., 'a function to sort a list of dictionaries by a key'). It should then use Claude Sonnet 4 to generate the Python function code and corresponding unit tests. Implement a custom tool that allows the agent to 'save_file(filename, content)' to a mock file system. The agent should invoke this tool twice: once for the function, once for the tests. Ensure it follows PEP8 where possible.
```typescript
// Example of a custom tool
const saveFileTool = createTool({
id: 'save_file',
description: 'Saves content to a specified file.',
schema: {
type: 'object',
properties: {
filename: { type: 'string' },
content: { type: 'string' },
},
required: ['filename', 'content'],
},
async execute({ filename, content }) {
console.log(`Saving ${filename}...`);
// Simulate file save, e.g., write to a local temp dir or in-memory map
return `File ${filename} saved successfully.`;
},
});
codeGenerator.addTool(saveFileTool);
// ... Workflow to use the tool
```Adaptation plan
Keep the source stable, then branch your edits in a predictable order so the next prompt run is easier to evaluate.
Hold the task contract and output shape stable so generated implementations remain comparable.
Update libraries, interfaces, and environment assumptions to match the stack you actually run.
Test failure handling, edge cases, and any code paths that depend on hidden context or secrets.
Copy once for a pristine source snapshot, then move the prompt into Workspace when you want variants, run history, and side-by-side tuning without losing the original.
Prompt diagnostics
Quick signals for how structured this prompt already is and where adaptation work is likely to happen first.
This prompt already mixes executable detail with instructions, so the safest path is to tune examples and interfaces before you rewrite the overall scaffold.
Accelerated Code Dev & Review Agent
Inspired by Claude's growing footprint in GitHub commits, this challenge focuses on building an advanced agentic development environment. You will use Mastra AI to orchestrate a team of agents that automate parts of the software development lifecycle, from generating code snippets based on user stories to automated testing and code review. The system should integrate with a simulated codebase, providing intelligent suggestions and even committing code. Emphasis is placed on code quality, security, and developer productivity.
Use the challenge page to recover the original task boundaries before you tune the prompt. That keeps your variants grounded in the same evaluation target instead of drifting into a different problem.