@nebulit/embuilder 0.1.42 → 0.1.44

package/dist/cli.js

@@ -14,7 +14,6 @@ program
 program
     .command('install')
     .description('Install event-model skills into Claude Code')
-    .option('--with-templates', 'Also copy template files (ralph.sh, AGENTS.md, Claude.md, prompt.md, README.md) and generators to current directory')
     .action((options) => {
     console.log('📦 Installing EMBuilder...\n');
     try {
@@ -28,8 +27,8 @@ program
             console.error(`   Package location: ${__dirname}`);
             console.error('');
             console.error('This might be caused by:');
-            console.error('  1. Old cached version - try: npx --yes @dilgerma/embuilder@latest install --with-templates');
-            console.error('  2. Package not published correctly - reinstall with: npm install -g @dilgerma/embuilder@latest');
+            console.error('  1. Old cached version - try: npx --yes @@nebulit/embuilder@latest install');
+            console.error('  2. Package not published correctly - reinstall with: npm install -g @nebulit/embuilder@latest');
             console.error('');
             console.error('If the problem persists, please report at:');
             console.error('  https://github.com/dilgerma/embuilder/issues');

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@nebulit/embuilder",
-  "version": "0.1.42",
+  "version": "0.1.44",
   "description": "Event-model driven development toolkit for Claude Code",
   "type": "module",
   "bin": {

package/templates/backend/prompt.md

@@ -7,10 +7,10 @@ The structure defined in the Project-Skills is relevant.
 ## Your Task
 
 0. Do not read the entire code base. Focus on the tasks in this description.
-1. Read the description at `.slices/index.json` (in the same directory as this file). Every item in status "planned" is a task.
+1. Read the description at `.slices/index.json` (in the same directory as this file). Every item in status "planned"  and assigned to "backend_worker" is a task.
 2. Read the progress log at `progress.txt` (check Codebase Patterns section first)
 3. Make sure you are on the right branch "feature/<slicename>", if unsure, start from main.
-5. Pick the **highest priority** slice where status is "planned" ( case insensitive ) and is not assigned to 'ui_worker'. This becomes your PRD. Set the status "InProgress", add a started_date ( including date and time ) and add an "assignee=backend_worker" in the index.json. If no slice has status planned, reply with:
+5. Pick the **highest priority** task assigned to backend_worker. This becomes your PRD. Set the status "InProgress", add a started_date ( including date and time ) in the index.json. If no slice has status planned, reply with:
    <promise>NO_TASKS</promise> and stop. Do not work on other slices.
 6. Pick the slice definition from the project root /.slices in <folder> defined in the prd. Never work on more than one slice per iteration.
 7. A slice can define additional prompts as codegen/backendPrompt. any additional prompts defined in backend are hints for the implementation of the slice and have to be taken into account. If you use the additional prompt, add a line in progress.txt
@@ -21,12 +21,12 @@ The structure defined in the Project-Skills is relevant.
 10. The slice in the json is always true, the code follows what is defined in the json
 11. the backend of a slice is only 'Done' if business logic is implemented as defined in the JSON, APIs are implemented, all scenarios in  JSON are implemented in code and it
     fulfills the slice.json. There must be no specification in json, that has no equivalent in code.
-12. make sure to write the ui-prompt.md as defined if defined in the skill
+12. make sure to write the ui-prompt.md for the ui_worker as defined if defined in the skill
 13. Run quality checks ( npm run build, npm run test ) - Attention - it´s enough to run the tests for the slice. Do not run all tests.
 14. even if the slice is fully implemented, run your test-analyzer skill and provide the code-slice.json file as defined in the skill
-15. Update the Slice in the index.json back to status 'Planned' and assign the 'ui-worker'
-16. If checks pass, commit ALL changes with message: `feat: [Slice Name]` and merge back to main as FF merge ( update
-    first )
+15. if the slice is an automation slice, set status to 'Done'. Otherwise - Update the Slice in the index.json back to status 'Planned' and assign the 'ui-worker'
+16. If checks pass, commit ALL changes with message: `feat: [Slice Name]`. 
+17. if the slice stauts is 'Done', merge back.
 17. Append your progress to `progress.txt` after each step in the iteration.
 18. append your new learnings to AGENTS.md in a compressed form, reusable for future iterations. Only add learnings if they are not already there.
 19. change the assignee to ui_worker and set it back to planned.

package/templates/frontend/prompt.md

@@ -2,6 +2,30 @@
 
 Build React + TypeScript UI components from slice JSON definitions using established patterns.
 
+## Your Task
+
+0. Do not read the entire code base. read /frontend/AGENTS.md. Focus on the tasks in this description.
+1. Read the description at `.slices/index.json` (in the same directory as this file). Every item in status "planned"  and assigned to "ui_worker" is a task.
+2. Read the progress log at `progress.txt` (check Codebase Patterns section first)
+3. Make sure you are on the right branch "feature/<slicename>", the branch should exist.
+5. Pick the **highest priority** task assigned to ui_worker. This becomes your PRD. Set the status "InProgress", add a started_date ( including date and time ) in the index.json. If no slice has status planned, reply with:
+   <promise>NO_TASKS</promise> and stop. Do not work on other slices.
+6. Pick the slice definition from the project root /.slices in <folder> defined in the prd. Never work on more than one slice per iteration.
+7. A slice can define additional prompts as codegen/uiPrompt. any additional prompts defined in backend are hints for the implementation of the slice and have to be taken into account. If you use the additional prompt, add a line in progress.txt
+8. Write a short progress one liner after each step to progress.txt
+9. Analyze and Implement according to the Rest of the instructions in this file, make use of the skills in the skills directory, but also your previsously collected
+   knowledge. Make a list TODO list for what needs to be done. Also make sure to adjust the implementation according to the json definition. 
+10. The slice in the json is always true, the code follows what is defined in the json
+11. the slice is only 'Done' if APIs are implemented.
+12. make sure to read the ui-prompt.md in /backend/src/slices/<slice>
+13. Run quality checks ( npm run build, tsc ) - Attention - it´s enough to run the tests for the slice. Do not run all tests.
+15. Update the Slice in the index.json to status 'Done' and remove assignment
+16. If checks pass, commit ALL changes with message: `feat: [Slice Name]` and merge back to main as FF merge ( update
+    first )
+17. Append your progress to `progress.txt` after each step in the iteration.
+18. append your new learnings to frontend/AGENTS.md in a compressed form, reusable for future iterations. Only add learnings if they are not already there.
+20. Finish the iteration.
+
 ---
 
 ## 0. Available Skills (Use These!)

package/templates/prompt.md

@@ -1,11 +1,12 @@
 # Ralph Agent Instructions
 
-You are an autonomous software architect, oversseing the sliced architecture.  working on the backend of a software project. You apply your skills to build software slices. You only work on one slice at a time.
-
-The structure defined in the Project-Skills is relevant.
+You are an autonomous software architect, overseeing the sliced architecture and who works on which slice.
+You assign tasks to workers. Only one task can be assigned and in status planned at a time.
 
 ## Your Task
 
-1. find the most important next slice
-2. if the slice is in status planned and not assigned, assign it to backend_worker (property assigned in ) and continue with backend/prompt.md. Ignore the rest of this file.
-3. if the slice is in status planned and assigned to ui_worker, continue with frontend/prompt.md. Ignore the rest of this file.
+1. find the most important next slice by watching .slices/index.json
+2. if the slice is in status planned and not assigned, assign it to backend_worker (property "assigned" ) and continue with backend/prompt.md. Ignore the rest of this file.
+3. if the status is in status "InProgress" and assigned to backend_worker, updated started_time and continue with backend/prompt.md. Ignore the rest of this file.
+4. if the status is "done" and assigned to "backend_worker", assign the task to "ui_worker" and move it back to status "planned". continue with frontend/prompt.md. Ignore the rest of this file.
+4. if there is no task in status planned, return <promise>NO_TASKS</promise>