Skip to content

Commit ce0e04e

Browse files
Merge pull request #218 from godspeedsystems/Release/v2.0.13
UI Generation workflow docs for Saarthi v2.0.13
2 parents b8d438f + aac039d commit ce0e04e

File tree

6 files changed

+381
-258
lines changed

6 files changed

+381
-258
lines changed

β€Ždocs/saarthi/getting-started/installing.mdxβ€Ž

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -45,7 +45,7 @@ import SaarthiIcon from '@site/src/components/SaarthiIcon';
4545

4646
**[Modes β†’](/docs/saarthi/basic-usage/using-modes.md)**
4747

48-
**[Workflows β†’](/docs/saarthi/workflows.md)**
48+
**[Workflows β†’](/docs/saarthi/workflows/general.md)**
4949

5050

5151
## Troubleshooting

β€Ždocs/saarthi/index.mdβ€Ž

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -36,7 +36,7 @@ import SaarthiIcon from '@site/src/components/SaarthiIcon';
3636
## Key Features
3737

3838
### Multiple Agents
39-
Saarthi adapts to your needs with specialized [modes](./basic-usage/using-modes) and [workflows](/docs/saarthi/workflows.md):
39+
Saarthi adapts to your needs with specialized [modes](./basic-usage/using-modes) and [workflows](/docs/saarthi/workflows/general.md):
4040

4141

4242
**[πŸ’» Code](./modes/code.md):** For general-purpose coding tasks, now with integrated support for Godspeed’s 4th-gen meta framework for backend development, enabling guard-railed 10x engineering practicesβ€”automatically.
@@ -66,7 +66,7 @@ Saarthi adapts to your needs with specialized [modes](./basic-usage/using-modes)
6666

6767

6868
### Smart Tools
69-
- Saarthi comes with powerful **[workflows](/docs/saarthi/workflows.md)** that can automate your multi-step dev tasks.
69+
- Saarthi comes with powerful **[workflows](/docs/saarthi/workflows/general.md)** that can automate your multi-step dev tasks.
7070
- Read and write files in your project
7171
- Execute commands in your VS Code terminal
7272
- Control a web browser
Lines changed: 20 additions & 57 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,8 @@
1+
---
2+
sidebar_label: General
3+
---
4+
5+
16
# Workflows
27

38
Workflows in Saarthi are **sequences of actions** defined to automate common development and deployment tasks. They are customizable and bring consistency, guardrails, and speed to your engineering process β€” from setting up a Godspeed project to deploying on cloud, generating UIs, creating test strategies, or even drafting technical documents.
@@ -136,49 +141,7 @@ Sets up authentication in your Godspeed microservice using supported auth method
136141

137142
---
138143

139-
### 7. Figma to UI Generation
140-
141-
**Description:**
142-
Convert your Figma designs into responsive UI components and pages.
143-
144-
**Pre-requirements:**
145-
146-
* Figma file URL
147-
* Figma Personal Access Token
148-
149-
**Process:**
150-
151-
1. **Select Workflow** – Choose `Figma to UI Generation` from workflows dropdown.
152-
2. **Provide Figma Details** – Enter Figma URL + Access Token.
153-
3. **Extract Components** – Saarthi generates component hierarchy with `gs-nodegen-figma`.
154-
4. **Generate Scaffolding** – Creates project scaffolding + imports Godspeed UI components.
155-
5. **Integrate APIs (optional)** – Provide Swagger spec β†’ generates API slices with Redux.
156-
6. **Run Strategy** – Orchestrator executes milestones β†’ pages & components built step-by-step.
157-
158-
---
159-
160-
### 8. Prompt to UI Generation
161-
162-
**Description:**
163-
Generate UI pages and components directly from a text prompt, if you don't have PRD, TRD, or Figma designs.
164-
Saarthi automates **strategy creation, component scaffolding, API integration, and responsive UI development** β€” all inside your workspace.
165-
166-
**Requirements:**
167-
168-
* Prepare your PRD/TRD files simply give a text prompt.
169-
* Project brief (you’ll be prompted for this if PRD/TRD are missing)
170-
* If using API integration, have a **Swagger/OpenAPI spec JSON** ready.
171-
172-
**Process:**
173-
174-
1. **Provide Project Brief** – If no PRD/TRD found, Saarthi asks for a short description of the project.
175-
2. **Scan Components** – Reads `components/gs-ui` and `components-list.txt` to detect available components.
176-
3. **Finalize Components** – User helps confirm components and their variants.
177-
4. **Generate Strategy** – Pages and components are mapped into milestones & steps.
178-
5. **Run Strategy** – Orchestrator executes the plan, building responsive pages with integrated APIs (if provided).
179-
180-
181-
### 9. Download and Run Docker Container
144+
### 7. Download and Run Docker Container
182145

183146
**Description**
184147
Pulls a Docker image and runs a container with custom configuration.
@@ -193,7 +156,7 @@ Pulls a Docker image and runs a container with custom configuration.
193156
6. Validates container is running.
194157

195158

196-
### 10. Godspeed Coaching
159+
### 8. Godspeed Coaching
197160

198161
**Description**
199162
Provides an interactive learning experience for mastering the Godspeed framework.
@@ -207,7 +170,7 @@ Provides an interactive learning experience for mastering the Godspeed framework
207170

208171
---
209172

210-
### 11. Implement Feature from PRD
173+
### 9. Implement Feature from PRD
211174

212175
**Description:**
213176
Implements features step-by-step based on the Product Requirement Document (PRD).
@@ -221,7 +184,7 @@ Implements features step-by-step based on the Product Requirement Document (PRD)
221184

222185
---
223186

224-
### 12. Create/Update Test Strategy
187+
### 10. Create/Update Test Strategy
225188

226189
**Description:**
227190
Creates or updates a comprehensive test strategy including scope, metrics, and environments.
@@ -235,7 +198,7 @@ Creates or updates a comprehensive test strategy including scope, metrics, and e
235198

236199
---
237200

238-
### 13. Generate Test Cases
201+
### 11. Generate Test Cases
239202

240203
**Description:**
241204
Generates detailed test cases (steps, expected results, traceability) from requirements.
@@ -249,7 +212,7 @@ Generates detailed test cases (steps, expected results, traceability) from requi
249212

250213
---
251214

252-
### 14. Update Test Cases in Strategy
215+
### 12. Update Test Cases in Strategy
253216

254217
**Description:**
255218
Maintains test documentation with version control, impact analysis, and traceability.
@@ -263,7 +226,7 @@ Maintains test documentation with version control, impact analysis, and traceabi
263226

264227
---
265228

266-
### 15. Deploy to Render
229+
### 13. Deploy to Render
267230

268231
**Description:**
269232
Deploys applications directly to the Render cloud platform.
@@ -277,7 +240,7 @@ Deploys applications directly to the Render cloud platform.
277240

278241
---
279242

280-
### 16. Progress Review
243+
### 14. Progress Review
281244

282245
**Description:**
283246
Reviews code, tests, and documentation against defined quality metrics.
@@ -291,7 +254,7 @@ Reviews code, tests, and documentation against defined quality metrics.
291254

292255
---
293256

294-
### 17. Create Docker Image
257+
### 15. Create Docker Image
295258

296259
**Description:**
297260
Builds Docker images from Dockerfiles for containerized deployment.
@@ -305,7 +268,7 @@ Builds Docker images from Dockerfiles for containerized deployment.
305268

306269
---
307270

308-
### 18. Sprint Plan to Git Issues
271+
### 16. Sprint Plan to Git Issues
309272

310273
**Description:**
311274
Converts sprint planning items into actionable GitHub issues.
@@ -319,7 +282,7 @@ Converts sprint planning items into actionable GitHub issues.
319282

320283
---
321284

322-
### 19. Generate High-Level TRD
285+
### 17. Generate High-Level TRD
323286

324287
**Description:**
325288
Generates a Technical Requirements Document (TRD) with architecture diagrams.
@@ -333,7 +296,7 @@ Generates a Technical Requirements Document (TRD) with architecture diagrams.
333296

334297
---
335298

336-
### 20. Generate Coding Guidelines
299+
### 18. Generate Coding Guidelines
337300

338301
**Description:**
339302
Creates coding standards with best practices, security, and compliance guidelines.
@@ -347,7 +310,7 @@ Creates coding standards with best practices, security, and compliance guideline
347310

348311
---
349312

350-
### 21. Learning Roadmap
313+
### 19. Learning Roadmap
351314

352315
**Description:**
353316
Builds a personalized learning roadmap with exercises, resources, and progress tracking.
@@ -361,7 +324,7 @@ Builds a personalized learning roadmap with exercises, resources, and progress t
361324

362325
---
363326

364-
### 22. Assign Exercises
327+
### 20. Assign Exercises
365328

366329
**Description:**
367330
Assigns predefined or custom exercises with tracking.
@@ -375,7 +338,7 @@ Assigns predefined or custom exercises with tracking.
375338

376339
---
377340

378-
### 23. Feedback-Driven Learning Path
341+
### 21. Feedback-Driven Learning Path
379342

380343
**Description:**
381344
Refines the learning experience using feedback, adjusting pace and content.
Lines changed: 155 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,155 @@
1+
---
2+
sidebar_label: UI Generation
3+
---
4+
5+
# 🎨 UI Generation Workflows
6+
7+
## Figma to UI Generation
8+
9+
**Description:** Β 
10+
Convert Figma designs into responsive UI components and pages using a schema-first approach.
11+
This workflow prioritizes structure and fidelity by generating schemas before code.
12+
13+
**Prerequisites:**
14+
- Figma file URL
15+
- Figma Personal Access Token
16+
- Optional: Swagger/OpenAPI spec JSON for API integration
17+
18+
**Process:**
19+
1. **Input Collection** – User provides Figma URL, Token, and file type (App or Page).
20+
2. **Schema Generation** – Saarthi uses `gs-nodegen-figma` tool to generate component schemas locally.
21+
3. **Scaffolding** – Generates the project structure (or uses existing) via `gs-ui-init` tool.
22+
4. **API Setup (Optional)** – If a Swagger spec is provided, generates API slices using `gs-codegen-openapi`tool and sets up the Redux store/provider.
23+
5. **Component Implementation** – Iteratively reads schemas and Figma images to build responsive, atomic components and transfers necessary assets.
24+
6. **Assembly & Routing** – Combines components into full web pages and configures application routing.
25+
7. **Validation & Handoff** – Runs the development server and asks the user to confirm if the output meets requirements or if changes are needed before final delivery.
26+
27+
### πŸ”‘ How to Get a Figma API Key
28+
29+
1. Go to **Figma β†’ Settings β†’ Security**.
30+
2. Under **Personal Access Tokens**, click **Generate new token**.
31+
3. Copy the generated token and store it securely.
32+
4. Use this token when prompted by Saarthi or the CLI.
33+
34+
### πŸ’‘ Tips for Best Results
35+
* **Organize Frames:** Keep components logically grouped and avoid deeply nested auto-layouts.
36+
* **Clear Naming:** Use descriptive layer names in Figma to help with component identification.
37+
* **Large Designs:** To generate large Figma files in one go, move to a paid Figma plan. On free or limited plans, prefer generating smaller pages or sections incrementally.
38+
39+
## ⚠️ Troubleshooting
40+
41+
<details>
42+
<summary><strong>Windows CLI Argument Parsing</strong></summary>
43+
44+
When using the CLI on Windows (PowerShell), wrap option values for gs-tools in both single and double quotes to correctly escape special characters.
45+
46+
**Example:** `--url '"https://example.com/file?id=123"'`
47+
</details>
48+
49+
<details>
50+
<summary><strong>429 – Rate Limit Exceeded</strong></summary>
51+
52+
This indicates that your Figma API key has hit rate limits.
53+
54+
**Note:** Many Figma APIs used by this tool are **Tier-1 APIs** and are subject to the limits described in the [Figma rate-limit documentation](https://developers.figma.com/docs/rest-api/rate-limits/#rate-limits-tier-table).
55+
If you are on a limited or free plan, you may encounter frequent connection errors.
56+
57+
**Recommended actions:**
58+
- Retry after some time.
59+
- Use smaller design or page-level URLs.
60+
- Move to a paid Figma plan for large or frequent exports.
61+
</details>
62+
63+
<details>
64+
<summary><strong>403 – Forbidden</strong></summary>
65+
66+
This means the token does not have access to the Figma file.
67+
68+
**Check the following:**
69+
- Verify that the Figma account used to generate the token has access to the design.
70+
- If you are on a paid plan, ensure the design is added to the correct paid team/workspace.
71+
</details>
72+
73+
<details>
74+
<summary><strong>500 Error or Timeout</strong></summary>
75+
76+
This can occur due to:
77+
- Large or complex Figma designs
78+
- API rate limits on free or limited plans
79+
- Figma servers not responding in time
80+
81+
**Recommended actions:**
82+
- Try generating smaller pages or sections instead of the full file.
83+
- Retry later.
84+
- Move to a paid Figma plan to reduce timeouts and API throttling.
85+
</details>
86+
87+
---
88+
89+
## Prompt to UI Generation
90+
91+
**Description:**
92+
93+
Generate UI pages and components directly from text prompts or PRDs.
94+
This workflow emphasizes predictability and reuse by leveraging the `gs-ui-kit` tool.
95+
96+
**Prerequisites:**
97+
- A text prompt or PRD/TRD
98+
- Project brief
99+
- Optional: Swagger/OpenAPI spec JSON for API integration
100+
101+
**Process:**
102+
1. **Scaffolding** – Sets up the UI project workspace via `gs-ui-init` tool.
103+
2. **Requirement Gathering** – Captures project goals or parses the provided PRD.
104+
3. **API Setup (Optional)** – Generates API slices via `gs-codegen-openapi` tool and wraps the app in a Redux provider.
105+
4. **Strategy & Component Selection** – Analyzes requirements to create a `ui-details.md` plan, selecting necessary components and variants from `gs-ui-kit` tool.
106+
5. **Build & Assemble** – Iteratively builds components (adapting from the kit or generating new ones) and assembles them into pages.
107+
6. **Validation & Handoff** – Starts the development server, verifies navigation, and asks the user to confirm if the application is ready or requires refinement.
108+
109+
110+
### πŸ’‘ Tips for Best Results
111+
* **Be Explicit:** Clearly state the page purpose (e.g., "dashboard", "auth page") and specific behaviors.
112+
* **Structure over Aesthetics:** Focus the prompt on layout and functionality first; refine styles later.
113+
* **API Planning:** Identify which components need which endpoints early in the prompt.
114+
115+
---
116+
117+
## Image to UI Generation
118+
119+
**Description:** Β 
120+
121+
Generate UI pages and components directly from design images.
122+
This workflow balances creative freedom with guardrails using atomic design principles.
123+
124+
**Prerequisites:**
125+
- One or more UI design images
126+
- Page-level metadata (color palette, fonts, theme)
127+
- Optional: Swagger/OpenAPI spec JSON
128+
129+
**Process:**
130+
1. **Image Upload** – User provides design images for pages or sections.
131+
2. **Scoping** – Define whether the image maps to a full page or a specific component.
132+
3. **Scaffolding** – Sets up the UI project workspace.
133+
4. **Metadata Capture** – User provides context (colors, fonts, themes).
134+
5. **Generation** – Creates atomic components based on image analysis.
135+
6. **Assembly** – Wires components into pages and connects optional APIs.
136+
7. **Validation & Handoff** – Runs the application and asks the user to validate the visual fidelity and functionality before finishing.
137+
138+
### πŸ’‘ Tips for Best Results
139+
* **Use high-resolution images** – Clear contrast and crisp details lead to better code generation
140+
* **Provide actual asset files upfront** – Share logos, icons, illustrations, and image assets directly instead of relying on generated placeholders. This ensures visual accuracy and maintains brand consistency
141+
* **Define design tokens clearly** – Specify your color palette, typography, and spacing scale before generation
142+
* **Document theme details** – Be explicit about light/dark mode, shadows, borders, and other style properties
143+
* **Share design system guidelines** – If you have existing design standards, provide them to maintain consistency across generated components
144+
145+
---
146+
147+
## Choosing the Right Workflow
148+
149+
| Workflow | Start With | Best For |
150+
|---------------|-------------------|----------------------------------|
151+
| Figma β†’ UI | Figma designs | Production-ready applications |
152+
| Prompt β†’ UI | Text / PRD | Structured app bootstrapping |
153+
| Image β†’ UI | Design images | Creative or non-standard designs |
154+
155+
---

β€Ždocs/welcome.mdβ€Ž

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ sidebar_label: Welcome
77

88
Godspeed is the first agentic SDLC platform that helps you build production-grade software 10x faster. Powered by a 4th-gen framework- [Param](/docs/microservices-framework/introduction/overview.md), AI agents, and built-in guardrails, it brings consistency to modern development. Even entry-level engineers and LLMs can ship clean, scalable code with ease.
99

10-
Meet [Saarthi](/docs/saarthi/index.md), your multi-agent team inside VS Code. It automates every step of the Software Development Lifecycle - from idea to release, through intelligent [Modes](../basic-usage/using-modes) and [Workflows](/docs/saarthi/workflows.md)
10+
Meet [Saarthi](/docs/saarthi/index.md), your multi-agent team inside VS Code. It automates every step of the Software Development Lifecycle - from idea to release, through intelligent [Modes](../basic-usage/using-modes) and [Workflows](/docs/saarthi/workflows/general.md)
1111

1212
Plan with PRDs, design with TRDs, generate tasks, implement features, review code, and deploy - all without leaving your IDE.
1313

0 commit comments

Comments
Β (0)