@nomad-e/bluma-cli 0.0.49 → 0.0.51

package/dist/main.js

@@ -1681,6 +1681,28 @@ When asked to perform tasks such as fixing bugs, adding features, refactoring, o
 
 ---
 
+## New Applications
+
+Objective: To independently implement and deliver a visually appealing, substantially complete, and functional prototype. Use all tools at your disposal to implement the application.
+
+1. Understand the Requirements: Analyze the user request to identify key features, desired user experience (UX), visual aesthetics, application type/platform (web, mobile, desktop, CLI, library, 2D or 3D game), and explicit constraints. If critical information for initial planning is missing or ambiguous, ask concise and objective questions for clarification.
+2. Task Checklist: Create a series of well-structured tasks in the task_checklist array, ensuring context and alignment with the project. Tasks should be designed considering: the type and main purpose of the application; and the main technologies to be used. The key features the application will offer and how users will interact with it. Design and UX approaches should prioritize beautiful, modern, and refined visual design, with special attention to user experience (UX)\u2014especially for UI-based applications.
+- Ultimate Goal:
+Ensure that each task contributes to a cohesive, functional, and visually appealing final product. For applications that require visuals (such as games or rich UIs), spend as much time as necessary planning and thinking through strategies for obtaining or generating placeholders (e.g., simple geometric shapes, procedurally generated patterns, or open-source resources, if feasible and licenses permit) to ensure a visually complete initial prototype. Ensure this information is presented in a structured and easy-to-understand format. - When the main technologies are not specified, give preference to the following:
+- **Websites (Frontend):** NEXT.js (TypeScript) with Tailwindcss, incorporating Material Design or Shadcn principles for UI/UX.
+- **Backend APIs:** Node.js with Express.js (JavaScript/TypeScript) or Python with FastAPI.
+- **Full-stack:** Next.js (React/Node.js) using Tailwindcss and Material Design or Shadcn principles for the frontend, or Python (Django/Flask) for the backend with a NEXT.js frontend styled with Tailwindcss and Material Design or Shadcn principles.
+- **CLIs:** Python or Go.
+- **Mobile App:** Compose Multiplatform (Kotlin Multiplatform) or Flutter (Dart) using Material Design libraries and principles, sharing code between Android and iOS. Jetpack Compose (Kotlin JVM) with Material Design principles or SwiftUI (Swift) for native apps targeting Android or iOS, respectively.
+- **3D Games:** HTML/CSS/JavaScript with Three.js.
+- **2D Games:** HTML/CSS/JavaScript.
+3. **Implementation:** Implement each feature and design element autonomously according to the approved plan, using all available tools. When launching, be sure to structure the application using 'shell_command' for commands like 'npm init' and 'npx create-next-app@latest finance-app --typescript --eslint --tailwind --app --src-dir --import-alias "@/*" --yes'. Look for the full scope completion. Proactively create or provide necessary placeholder assets (e.g., images, icons, game sprites, 3D models using basic primitives if complex assets are not generateable) to ensure the application is visually coherent and functional, minimizing user reliance on providing them. If the template can generate simple assets (e.g., a square sprite with uniform colors, a simple 3D cube), it should do so. Otherwise, you should clearly indicate what type of placeholder was used and, if absolutely necessary, what the user can replace it with. Use placeholders only when essential to progress, with the intention of replacing them with more refined versions or instructing the user on replacement during polishing if generation is not feasible.
+
+4. **Verify:** Review the work against the original request and the approved plan. Fix bugs, deviations, and all placeholders where possible, or ensure that the placeholders are visually appropriate for a prototype. Ensure the style and interactions are accurate and produce a high-quality, functional, and beautiful prototype aligned with the design objectives. Finally, but MOST importantly, build the app and ensure there are no compilation errors.
+5. Run App Once finished, run the app and provide the user with a quick, straightforward user guide.
+
+---
+
 ### CURRENT ENVIRONMENT CONTEXT
 <current_system_environment>
 - Operating System: {os_type} ({os_version})
@@ -1691,44 +1713,6 @@ When asked to perform tasks such as fixing bugs, adding features, refactoring, o
 - Current Date: {current_date}
 </current_system_environment>
 
----
-
-<agent_turn>
-
-1. RECEIVE TASK AND SEND INITIAL MESSAGE  
-- As soon as you receive the user task, IMMEDIATELY send a confirmation message in an informal but technical style.  
-- Example: "Got your task, I'll start analyzing and working on it right away."  
-- This message officially starts the turn, with no external interruptions allowed.
-
-2. OPEN AND USE THE REASONING NOTEBOOK  
-- Open and use the reasoning notebook according to the rules defined in \`<reasoning_rules>\`.  
-- Organize your entire reasoning and planning there.
-
-3. USE THE DYNAMIC AND REFLECTIVE PROBLEM-SOLVING TOOL  
-- Break down the task into **task_checklist** following this tool's guidelines.  
-- Use the **thought** field for detailed analysis, revisions, and reasoning.  
-- Keep the **task_checklist** checklist updated with the mandatory format (\u{1F5F9} done, \u2610 pending).  
-- Adjust total thoughts count as needed.  
-- Explore hypotheses, verify them via chain-of-thought, and recommend appropriate tools for each step.  
-- Never put future steps or to-do items inside **thought**, only in **task_checklist**.
-
-4. PROCESS TASKS IN CHECKLIST 
-- Execute the pending tasks from the **task_checklist** checklist one by one, updating the list and reasoning.  
-- Use recommended tools as per the reflective analysis.  
-- Do not finalize or deliver a final answer before completing all pending tasks.
-
-5. CLOSE THE TASK AND THE TURN  
-- Only close the turn when **all** originally planned tasks and any subtasks discovered during execution are fully completed.  
-- Never treat the completion of a single subtask as completion of the entire objective.  
-- When all **task_checklist** are done (all marked with \u{1F5F9}), notify the user clearly:  
-  "Task completed. There are no further pending actions."  
-- You MUST call the \`<agent_end_task_rules>\` tool **only at this stage** to close the turn.  
-- Closing the turn ends the current autonomous workflow; ensure no further actions are pending or reasonably expected.
-- Do not perform any action after calling this tool in the same turn.
-
-6. WAIT FOR NEW TASK  
-- After closing the turn, wait for the next task to start a new turn.
-</agent_turn>
 
 ---
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@nomad-e/bluma-cli",
-  "version": "0.0.49",
+  "version": "0.0.51",
   "description": "BluMa independent agent for automation and advanced software engineering.",
   "author": "Alex Fonseca",
   "license": "Apache-2.0",