How to get started with SimpleGen?

AI solutions SimpleGen
,
1

Frame 1 (2)
Frame 1 (2)2568×648 149 KB

SimpleGen — a new product for generating solutions on the SimpleOne platform using AI. In this article, we’ll cover how to get started with SimpleGen: what to install on your workstation, how to prepare the repository, configure access to SimpleOne, and execute your first task.

Preparation

1) Requirements :toolbox:

SimpleOne Platform Instance (Standalone)

To work with SimpleGen, you need any instance of the SimpleOne platform. Any type of instance (dev/test/stage/personal standalone, etc.) and any deployment type (cloud/internal network) will work — as long as you have:

  • The instance URL
  • Administrator credentials or an API key

You do not need to install SimpleGen on the instance: it connects to the instance via URL and uses your credentials or key.

Tools on Your Workstation :hammer_and_wrench:

  • Node.js + npm
  • Git for your OS (for git init, commits, and GitLab integration)
  • Cursor (offers a free tier with limited request quota)

2) Install SimpleGen :inbox_tray:

Open your OS’s standard terminal, where node, npm, and git are accessible, and perform a global installation: this makes the simplegen command available from any directory. Use the -g flag:

npm install -g @simplegen/simplegen[1]

Group 1 (8)
Group 1 (8)1168×603 99.9 KB

3) Prepare the Git Repository (Initialize Repository) :card_index_dividers:

If your project folder is not yet a Git repository, run in the terminal:

  • git init

Group 2 (2)
Group 2 (2)876×329 85.1 KB

Error: 'git is not recognized as an internal or external command...'

Important! If you see an error like “git is not recognized as an internal or external command…”, Git is either not installed or not added to your PATH. Install the appropriate Git version for your OS and verify with git --version.

4) Configure Access to SimpleOne :key:

SimpleGen uses environment variables. In the root of your project (repository), the .env file must contain:

  • SIMPLEONE_URL
  • and either SIMPLEONE_API_KEY or SIMPLEONE_LOGIN + SIMPLEONE_PASSWORD

Example:

SIMPLEONE_URL=http://simple.test
SIMPLEONE_LOGIN=admin
SIMPLEONE_PASSWORD=123456

Source priority for variables:

  1. Process environment variables (SIMPLEONE\_\*)
  2. .env in the repository root
  3. ~/.simplegen/.env

5) Initial SimpleGen Project Setup :page_with_curl:

If you need to initialize an empty repository (the product already exists on the instance but hasn’t been cloned into the local folder), run this command in your project folder:

  • simplegen init ApplicationName

The application name must exactly match the name field in the Applications table on the instance.

image 4
image 42188×610 78.5 KB

This command downloads your application’s records, along with required applications (Simple Application and Platform).

Group 3 (2)
Group 3 (2)886×980 249 KB

Error: 'simplegen fetch failed'

Important! If you see the message “[simplegen] fetch failed”, your instance is unreachable. Verify its accessibility from the external network.

If your project repository is not empty, use the command /simplegen.init for subsequent version updates.

Notes:

  • Downloading “heavy” products may take up to ~10 minutes.
  • The command simplegen init ApplicationName must be executed only once during initial setup, if the repository is empty.

6) Commit the Initial State :round_pushpin:

  • git add .
  • git commit -m “Initial SimpleGen setup”

Group 4 (4)
Group 4 (4)849×986 271 KB

Error: 'Author identity unknown'

Important! If you see the message “Author identity unknown”, you must set your Git profile. Run these two commands:

git config --global user.name "your_username"

git config --global user.email "your_email@example.com"

Why Commit the Initial State?

  • Establish a baseline after initialization
    The commit captures the correct base state of the project immediately after setup.

  • Simplify change tracking and troubleshooting
    All future actions (generation, edits, synchronization) will show clear changes relative to this commit: exactly what changed and where. This is especially useful for understanding what was introduced by generation or updates.

  • Safe rollback capability
    If something goes wrong after the next steps, you can quickly revert to the committed state.

  • Team collaboration convenience (GitLab)
    With the baseline committed, the entire team shares the same starting point: easier code reviews and change comparisons.

Working on a Task with Cursor (How to Run SimpleGen Commands)

Cursor is an editor where SimpleGen commands are executed via chat using slash commands (via menu).

1) Open the Project in Cursor

SimpleGen relies on the project structure and repository files, so the entire project must be opened. Click the Open project button and select the repository root (the folder containing .env, platform/, sa/, etc.).

image 5
image 51928×1088 62 KB

Below is the typical workflow for working on a task in SimpleGen via Cursor: from specification to deployment on the instance. Commands are executed in the Cursor chat via the / menu (as slash commands), not as plain text.

2) Create a Task Specification

In the Cursor chat, run the specification creation command: /simplegen.spec_create

Along with the command, enter: a brief task description + acceptance criteria.

Cursor status shows 'Reconnecting...' for a long time

“Reconnecting…” appears for a long time in the Cursor request status: this indicates a connection issue between Cursor and the instance (network/VPN). First restore the connection, then run SimpleGen commands.

Example:

Name: Validate urgency field
Description: When saving a task, the urgency field must be mandatory
Acceptance criteria:
- An error is shown when urgency is empty
- The record is not saved without urgency

Group 5 (2)
Group 5 (2)1920×3759 433 KB

3) Generate an Implementation Plan

/simplegen.spec_plan — breaks the task into steps and creates a work plan in _task.md

Group 6
Group 6908×815 112 KB

Once you’re satisfied with the specification and plan, commit them to Git:

git add .
git commit -m "Add spec for <featu
```">\"\n```\n\n![Group 7 (1)|690x262](upload://mqQyK0jZKWVpK1yXOn629KPjA2p.png)\n\n### 4) Generate changes (code/configuration)\n\n`/simplegen.code_generate` — generates changes based on the specification and plan for the current feature.\n\nAfter generation:\n\n* Review the changes in git diff/Changes in the editor,\n* If needed, correct the specification/plan and regenerate (iteratively),\n* **Keep All** — accept all changes.\n\n![Group 8|417x500](upload://iTMXlYLG6ZhcL7jVBNIVvEBWVQf.png)\n\n### 5) Commit the results\n\nWhen you are satisfied with the changes:\n\n```bash\ngit add .\ngit commit -m \"Implement <feature>\"\n```\n\n### 6) Build and deploy to the SimpleOne environment\n\n`/simplegen.product_build` — builds the SOP and deploys the changes to the environment (deployment status is displayed in the console)\n\n![Group 11|429x500](upload://nXg1LUtoggfVQGn7Ryz4voNqH80.png)\n\n## Conclusion :chequered_flag:\n\nYou now have:\n\n* SimpleGen installed\n\n* A local repository (git)\n\n* Configured access to **your SimpleOne instance** (via URL + credentials/key)\n\n* Your first completed task\n\n  ![Group 12|690x436](upload://i4kbUB2T6Tcyyw0WApEpksW2K88.png)\n\n> In the next articles, we'll cover how to connect Figma and work on advanced project tasks. If you have any questions about getting started with SimpleGen or ideas for new articles, we welcome your comments!\n\nToolset for AI-powered code generation on the SimpleOne platform: https://www.npmjs.com/package/@simplegen/simplegen

  1. Learn more here: https://www.npmjs.com/package/@simplegen/simplegen ↩︎

7 Likes