Mastering Task Writing for Blaze Engineer
How to craft crystal‑clear coding jobs that unlock the full power of AI‑driven software engineering.
Quick Link: Explore the platform at blaze.engineer
Why Your Tasks Matter
Blaze Engineer turns natural‑language tasks into concrete code changes. The clearer your instructions, the faster the platform can ship working features. A well‑written task can save hours of back‑and‑forth, reduce hallucinations, and let the AI focus on what it does best: building software.
Every task you write is sent to the Blaze Engineer API as a Coding Job. The more context you provide, the tighter the feedback loop.
Blaze Engineer's Superpowers
Blaze Engineer excels at
- Creating brand‑new projects from scratch.
- Adding new features to an existing codebase.
- Modifying existing features for enhancements or bug fixes.
- Refactoring entire repositories for style, structure, or technology upgrades.
Give it a precise mission in any of these areas and the system will handle project scaffolding, file generation, and even heavy refactors on a live codebase.
Task Archetypes & What to Include
Below is a distilled version of the in‑app Writing Good Tasks guide.
1. New Project Tasks
When you need Blaze Engineer to spin up a green‑field repository, specify:
- Stack - frontend, backend, or full‑stack.
- Runtime details - Node version, JavaScript or TypeScript, ESM or CommonJS.
- Frameworks/Libraries - React, Vue, Express, Fastify, etc.
- External services - databases, caches, message buses, third‑party APIs.
- Architecture & Design - desired folder layout, entry files, screen list, API routes.
- Feature list - bullet‑point the MVP scope.
Example: "Create a full‑stack video‑sharing platform… React SPA (no JSX), Express backend, MongoDB + AWS S3…"
2. Editing Existing Projects
- Adding a New Feature
- Provide a short summary plus whether it touches UI, API, or both. Link to relevant files or folders when possible.
- Extending an Existing Feature
- Describe what you're adding and which feature it augments. Highlight edge cases.
- Project‑Wide New Capability
- Outline the cross‑cutting concern (e.g., internationalization, logging, dark mode) and enumerate the file types Blaze Engineer should modify.
- Refactors
- State the refactor's goal - naming, formatting, performance, or tech migration - and scope (entire repo or specific modules).
Five Golden Rules for Better Tasks
- Lead with a one‑sentence summary. Give Blaze Engineer the TL;DR up front.
- List environment variables and external service credentials it will need.
- Describe folder structure or point to existing directories for context.
- Use bullet points for features, endpoints, or UI screens - AI parses lists quickly.
- Clarify output expectations. If you want every changed file returned, say so.
Example Tasks From the Official Guide
The HTML guide ships with fully‑fleshed samples. Here are two that illustrate what "good" looks like.
Example 1 - Kick‑Off a New Project
We need to create the base of a new project. The new project is a Simple Video Sharing Platform. The Frontend will be a ReactJS Application not using JSX. The Backend will be an ExpressJS server that serves the ReactJS Application and the endpoints the Frontend Application will make requests too.
The Backend will upload the video file to an AWS S3 Bucket then insert a MongoDB record in a Videos Collection containing the title, description, uploadedTime, and location using the mongodb NPM Package and using the simpleVideoSharingPlatform MongoDB Database. The location will be the URL to the Video File in the AWS S3 Bucket. Use dotenv NPM Package to load environment variables. Create and generate the src/index.js file that will configure, setup, and run ExpressJS server. Create and generate every other file needed for the basic functionality for each Backend feature. The Backend will use IMPORT instead of require to import files.
The Frontend will have an Upload Video Screen and a View Uploaded Videos Screen. The two screens should be contained inside a single file ReactJS html file named core.html that can be served as a SPA that will contain all the HTML/CSS/JavaScript for everything inside the SPA.
Here is the folder structure I want the project to start with:
/src
/classes
/functions
/endpoints
/ui
core.html
index.js
There are no user accounts or authorization. Any visitor can upload a video or view the uploaded videos. The data attached to an uploaded video will be the title, description, uploadedTime, and the location. The visitor provides the title and description. The system provides the current time for the uploadedTime and the AWS S3 Bucket URL for the Video File location.
Example 1 Output
Example 2 - Editing an Existing Project
Add a delete‑button feature to uploaded videos. The button should appear-and work-only for visitors whose IP matches the IP of the uploader.
Example 2 Output
Notice how each example:
- Starts with a plain‑language summary.
- Specifies the what (feature), where (code areas), and any constraints (IP match).
- Provides folder layouts or environment hints when relevant.
Use these as templates and adapt them to your own domain.
Still in Beta - Grab Your Free Credits
The Blaze Engineer public beta is live and currently accepting beta‑key requests. Approved testers receive $10 in free AI credits to explore automated project creation, feature work, and repo‑scale refactors. Spaces are limited - request your key while the program is open!
Final Thoughts
Task writing is a skill, and with Blaze Engineer the payoff is exponential. By sharpening your prompts, you let the platform do what it does best - generate, modify, and refactor code at machine speed so you can ship faster.
Ready to give it a try? Draft a task, send it to the Blaze Engineer API, and watch your next feature land in minutes.
Top comments (1)
Building out an n8n workflow with Blaze Engineer to manage my blog updated on a gatsby site.