Table of Contents
Getting started
Blastin helps you build comprehensive documentation for generating complex software systems. There are three ways to utilise Blastin:
- Export your documentation to integrated low-code platforms (like Agilityflow) and build your application without writing code
- As a developer, use your documentation to contextualise other language models, enhancing their understanding of your system
- Combine both approaches: utilise an integrated low-code platform for backend data management whilst building your custom frontend with AI-powered tools like Cursor
Chatting with Blastin
We need to understand your system requirements. The best way is to think about the features your system will comprise and how the data will be structured in the database.
While describing your requirements, the best way to start simple and refine as you go. Even in the traditional software development, we don't start with the whole system, we start with a small part, usually what has more value for the business, and grow it as we go.
I would like to build a CRM
From there, you can analyse what is coming back, iterate and improve the suggestions, adding more details about the features and how they should work.
If you intend to run your system on an integrated low-code platform, you need to consider the capabilities that already exist in that platform. For example, you don't need to think about membership, roles, communication tracking or even reports because they may be already implemented.
With every change to your requirements, Blastin will ask you to confirm the changes and save them. If not confirmed, the changes won't be persisted.
Building your database model
Once you're happy with your module requirements, you can ask Blastin to generate the database model.
Build my ERD
The generated ERD will be represented in DBML format. At the moment, Blastin cannot display the diagram in graph format, but you can copy the DBML code and paste into DBDiagram App to see it in a graph format.
Table customer {
id guid [pk]
name string [not null]
email string [not null]
phone string
address string
}
Table sales_opportunity {
id guid [pk]
customer_id guid [not null]
stage enum(prospecting, qualification, proposal, negotiation, closed_won, closed_lost) [not null]
expected_close_date date
potential_revenue decimal
}
Ref: sales_opportunity.customer_id > customer.id // many-to-one
From this point, you can deploy the application to the integrated system or use it as documentation for other AI tools.
Workflows
Entities can have associated workflows that define their progression through different states. For example, a sales opportunity might follow a sales process workflow, or a customer might follow an onboarding workflow. Workflows are more sophisticated than simple status fields - they enforce a specific sequence of states that records must follow.
You can start with a generic request to see what steps the AI agent suggests, or be specific about which steps the workflow should include:
Build a workflow for the customer entity, progressing from prospecting to closed won
You can modify the steps and transitions at any time by asking the AI agent to make changes.
Note: Currently, workflows are limited to linear sequences and cannot include branches. Depending on your integration platform, you may be able to modify workflows in the running instance. Please refer to your integration's documentation for details.
Business rule step
Business rules are a way to define custom logic for your workflows. They are used to define the conditions that must be met for a workflow to progress to the next step.
Create a business rule step "Check customer email" for the customer entity before the "close won" step.
At this stage, the business rule is just a placeholder where the logic must be implemented in the integrated platform.
Deploy
We call it deploy because it's the term most developers are familiar with, but the instance is always running and changes are applied once you decide to deploy. Blastin can create a difference between environments and apply the changes. Once the environment is updated, Blastin retrieves the latest state of the instance and updates its ERD accordingly.
CAUTION: Blastin manages the schema changes but not data. If an attribute is removed from an entity, Blastin does not migrate the data automatically. The field is soft-deleted in the instance, and the migration must be done manually.
The deployment status:
If you have green ticks you ready to deploy.
Deployment target:
If you have an enabled subscription with one of our integrated low-code platform, you should be able to see it as a target.
Danger zone:
If you want to delete the current environment, you can do it from the danger zone. This action is irreversible and will delete the current environment and all its data.
That's it, click on deploy and once it finishes, you should be able to see your application running in the target environment.
Integrated platforms
Blastin offers a standardised integration protocol for various platforms. Currently, we prioritise low-code platform integrations as they provide immediate value to most users without the need to write any code.
The synchronisation between Blastin and the integrated platform is two-way. Blastin can push the changes to the platform and also pull the changes from it.
You may need an active subscription to use integrated platforms.
Agilityflow
Agilityflow was our first integrated platform. It's a powerful tool that allows you to build apps without writing any code. You don't need any knowledge of how to configure the platform, Blastin will do everything for you, but you still can use the tools available in the platform and import the changes into Blastin anytime.
Agilityflow has a user table out-of-the-box. If you want to create a relationship with it, just create a field sys_user_id of type guid in the table you want to have the relationship.
Pull changes from Agilityflow:
You can pull the changes from Agilityflow by clicking on the three dots and selecting "Pull ".
By doing that, your database schema in Blastin will be replaced by the one in Agilityflow. The same process happens after every deployments to keep things is in sync.
Cursor is one of the most popular IDEs for building applications with an AI-first approach. It can absolutely transform your coding performance.
Blastin enables you to contextualise the system specification gathered with Blastin into Cursor, making it even more powerful. A feature called Cursor docs will allow you to provide an external link to give more context to the AI.
Generating shareable link on Blastin:
Copy and create a new doc in Cursor with the link.
Now, let's say you have created a new NextJS project and want to create a new website based on the Blastin system specification. In cursor, press Ctrl+Shift+I to open Cursor composer, and start with something like:
It might not be perfect, but will give a good starting point. If you have already something implemented in your codebase is even better, once cursor will use it as reference to implement something new.
Note: Once a document is added to Cursor, it becomes indexed and any subsequent changes made in Blastin won't be reflected automatically. You'll need to either re-add the document or force Cursor to re-index it.
How the low-code platform comes into play?
In the provided example, we used Prisma and connected our application directly to the database. If you're using another integrated platform, you can integrate with its API endpoints instead of making direct database calls.