@nomad-e/bluma-cli 0.0.49 → 0.0.50

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/dist/main.js +22 -0
  2. package/package.json +1 -1
package/dist/main.js CHANGED
@@ -1681,6 +1681,28 @@ When asked to perform tasks such as fixing bugs, adding features, refactoring, o
1681
1681
 
1682
1682
  ---
1683
1683
 
1684
+ ## New Applications
1685
+
1686
+ Objective: To independently implement and deliver a visually appealing, substantially complete, and functional prototype. Use all tools at your disposal to implement the application.
1687
+
1688
+ 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.
1689
+ 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.
1690
+ - Ultimate Goal:
1691
+ 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:
1692
+ - **Websites (Frontend):** NEXT.js (TypeScript) with Tailwindcss, incorporating Material Design or Shadcn principles for UI/UX.
1693
+ - **Backend APIs:** Node.js with Express.js (JavaScript/TypeScript) or Python with FastAPI.
1694
+ - **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.
1695
+ - **CLIs:** Python or Go.
1696
+ - **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.
1697
+ - **3D Games:** HTML/CSS/JavaScript with Three.js.
1698
+ - **2D Games:** HTML/CSS/JavaScript.
1699
+ 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.
1700
+
1701
+ 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.
1702
+ 5. Run App Once finished, run the app and provide the user with a quick, straightforward user guide.
1703
+
1704
+ ---
1705
+
1684
1706
  ### CURRENT ENVIRONMENT CONTEXT
1685
1707
  <current_system_environment>
1686
1708
  - Operating System: {os_type} ({os_version})
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@nomad-e/bluma-cli",
3
- "version": "0.0.49",
3
+ "version": "0.0.50",
4
4
  "description": "BluMa independent agent for automation and advanced software engineering.",
5
5
  "author": "Alex Fonseca",
6
6
  "license": "Apache-2.0",