@nebulit/embuilder 0.1.47 → 0.1.49

package/package.json

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

package/templates/backend/AGENTS.md

@@ -104,20 +104,22 @@ import { ContextEvents } from '../../events/ContextEvents';
 - Use proper `initialState` function (not empty object `{}`) in `DeciderSpecification.for()`
 - Do NOT add explicit type arguments - let TypeScript infer (avoids TS2558)
 - Switch statements: always use explicit `break` to prevent fallthrough bugs
+- you must not change the signature of evolve - it has (state:State, event:Event)
+- you must not change the signature of decide - it has (state:State, command:Command)  - all data to verify the command must be passed via state.
 
 **Structure**:
 ```typescript
 type State = { /* track relevant state */ };
 const initialState = (): State => ({ /* defaults */ });
 const decide = (state: State, cmd: Command): Event[] => {
-  if (invalidCondition) throw 'error.code';
-  return [createEvent(cmd)];
+    if (invalidCondition) throw 'error.code';
+    return [createEvent(cmd)];
 };
 const evolve = (state: State, event: ContextEvents): State => {
-  switch (event.type) {
-    case 'EventType': return { ...state, field: newValue };
-    default: return state;
-  }
+    switch (event.type) {
+        case 'EventType': return { ...state, field: newValue };
+        default: return state;
+    }
 };
 ```
 
@@ -133,14 +135,14 @@ const evolve = (state: State, event: ContextEvents): State => {
 **Projection Structure**:
 ```typescript
 export const ProjectionName = postgreSQLRawSQLProjection({
-  canHandle: ['Event1', 'Event2'],
-  evolve: (event: Event1 | Event2) => {
-    switch (event.type) {
-      case 'Event1': return sql(db(table).insert({...}).onConflict().merge());
-      case 'Event2': return sql(db(table).where({...}).delete());
-      default: return [];
+    canHandle: ['Event1', 'Event2'],
+    evolve: (event: Event1 | Event2) => {
+        switch (event.type) {
+            case 'Event1': return sql(db(table).insert({...}).onConflict().merge());
+            case 'Event2': return sql(db(table).where({...}).delete());
+            default: return [];
+        }
     }
-  }
 });
 ```
 
@@ -158,22 +160,22 @@ import { createServiceClient } from '../../common/supabaseClient';
 const config = { schedule: '*/30 * * * * *', endpoint: "work_queue_table" };
 
 export const processor = {
-  start: () => {
-    cron.schedule(config.schedule, async () => {
-      const client = createServiceClient();
-      const result = await client.from(config.endpoint)
-        .select("*").eq('must_process', true).limit(1);
-
-      if (result.error) return;
-      for (const item of result.data ?? []) {
-        try {
-          await handleCommand(streamId, command, { userId: 'system', ...metadata });
-        } catch (error) {
-          console.error('Processing error:', error);
-        }
-      }
-    });
-  }
+    start: () => {
+        cron.schedule(config.schedule, async () => {
+            const client = createServiceClient();
+            const result = await client.from(config.endpoint)
+                .select("*").eq('must_process', true).limit(1);
+
+            if (result.error) return;
+            for (const item of result.data ?? []) {
+                try {
+                    await handleCommand(streamId, command, { userId: 'system', ...metadata });
+                } catch (error) {
+                    console.error('Processing error:', error);
+                }
+            }
+        });
+    }
 };
 ```
 
@@ -189,9 +191,9 @@ export const processor = {
 ```typescript
 type State = { isActive: boolean };
 const decide = (state: State, cmd: Command): Event[] => {
-  if (state.isActive) throw "already.active";  // Activate guard
-  if (!state.isActive) throw "not.active";     // Deactivate guard
-  return [event];
+    if (state.isActive) throw "already.active";  // Activate guard
+    if (!state.isActive) throw "not.active";     // Deactivate guard
+    return [event];
 };
 ```
 
@@ -201,13 +203,13 @@ const decide = (state: State, cmd: Command): Event[] => {
 ```typescript
 type State = { trackedIds: Set<string> };
 const evolve = (state: State, event: ContextEvents): State => {
-  switch (event.type) {
-    case 'ItemAdded': return { trackedIds: new Set([...state.trackedIds, event.data.id]) };
-    case 'ItemRemoved':
-      const newSet = new Set(state.trackedIds);
-      newSet.delete(event.data.id);
-      return { trackedIds: newSet };
-  }
+    switch (event.type) {
+        case 'ItemAdded': return { trackedIds: new Set([...state.trackedIds, event.data.id]) };
+        case 'ItemRemoved':
+            const newSet = new Set(state.trackedIds);
+            newSet.delete(event.data.id);
+            return { trackedIds: newSet };
+    }
 };
 ```
 
@@ -217,10 +219,10 @@ const evolve = (state: State, event: ContextEvents): State => {
 ```typescript
 type State = { submitted: boolean; reverted: boolean; approved: boolean; declined: boolean };
 const decide = (state: State, cmd: Command): Event[] => {
-  if (state.submitted) throw 'cannot submit twice';
-  if (!state.submitted) throw 'not_submitted';
-  if (state.reverted) throw 'already_reverted';
-  return [event];
+    if (state.submitted) throw 'cannot submit twice';
+    if (!state.submitted) throw 'not_submitted';
+    if (state.reverted) throw 'already_reverted';
+    return [event];
 };
 ```
 
@@ -275,27 +277,27 @@ All endpoints must:
 ### STATE_CHANGE Tests
 ```typescript
 DeciderSpecification.for(decide, evolve, initialState)
-  .given([PrerequisiteEvent1, PrerequisiteEvent2])
-  .when(Command({ field: 'value' }))
-  .then([ExpectedEvent({ field: 'value' })]);
+    .given([PrerequisiteEvent1, PrerequisiteEvent2])
+    .when(Command({ field: 'value' }))
+    .then([ExpectedEvent({ field: 'value' })]);
 ```
 
 ### STATE_VIEW Tests
 ```typescript
 PostgreSQLProjectionSpec.for(ProjectionName)
-  .given([Event1, Event2])
-  .when([])  // Always empty
-  .then(async (state) => {
-    const result = await state.query();
-    assert.equal(result[0].field, expectedValue);
-  });
+    .given([Event1, Event2])
+    .when([])  // Always empty
+    .then(async (state) => {
+        const result = await state.query();
+        assert.equal(result[0].field, expectedValue);
+    });
 ```
 
 ### Error Case Tests
 ```typescript
 .given([EventCreated])
-.when(Command)
-.shouldFail();  // Expects error
+    .when(Command)
+    .shouldFail();  // Expects error
 ```
 
 ### Test Coverage

package/templates/backend/prompt.md

@@ -3,6 +3,8 @@
 You are an autonomous coding agent 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.
+If a slice is in status 'planned', Even if a slice seems to have been implemented, make sure to verify the implementation, check for new fields, new specifications, additional custom prompts in the slice json. A "planned" slice can also be an update of an existing slice. If that is the case, match the implemenetation to the updated slice definition.
+
 
 ## Your Task
 
@@ -10,27 +12,26 @@ The structure defined in the Project-Skills is relevant.
 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** 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:
+5. Pick the **highest priority** task assigned to backend_worker. This becomes your only task to work on. 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
-7. Define the slice type. If the processors-array is not empty, it´s an automation slice. Load the matching skill (automation-slice, state-change-slice, state-view-slice)
-8. Write a short progress one liner after each step to progress.txt
-9. Analyze and Implement that single slice, 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. Carefully inspect events, fields and compare against the implemented slice. JSON is the desired state. ATTENTION: A "planned" task can also be just added specifications. So always look at the slice itself, but also the specifications. If specifications were added in json, which are not on code, you need to add them in code.
-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
+6. Pick the slice definition from the project root /.slices in <folder> defined in the prd. Only work on this one assigned task, never other tasks.
+7. A slice can define additional prompts as codegen/backendPrompt in the slice.json. any additional prompts defined in json 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. Define the slice type. If the processors-array is not empty, it´s an automation slice. if there is a readmodel, it´s a state view. If there is a command and no processor, it´s a state change. Load the matching skill (slice-automation, slice-state-change, slice-state-view)
+9. Write a short progress one liner after each step to progress.txt
+10. Analyze and Implement that single slice, 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, whenever you work on a task. The definition can change for existing slices, which means the implementation has to adapt. Carefully inspect events, fields and compare against the implemented slice. JSON is the desired state. ATTENTION: A "planned" task can also be just added specifications. So always look at the slice itself, but also the specifications. If specifications were added in json, which are not on code, you need to add them in code.
+11. The slice in the json is always true, the code follows what is defined in the json
+12. 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 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. 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.
-20. Finish the iteration.
+13. make sure to write the ui-prompt.md for the ui_worker as defined if defined in the skill
+14. 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.
+15. even if the slice is fully implemented, run your test-analyzer skill and provide the code-slice.json file as defined in the skill
+16. 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'
+17. If checks pass, commit ALL changes with message: `feat: [Slice Name]`.
+18. Append your progress to `progress.txt` after each step in the iteration.
+19. append your new learnings to AGENTS.md in a compressed form, reusable for future iterations. Only add learnings if they are not already there.
+20. if the slice status is 'Done', merge back to main.
+21. Finish the iteration.
 
 ## Progress Report Format
 

package/templates/frontend/prompt.md

@@ -4,11 +4,13 @@ Build React + TypeScript UI components from slice JSON definitions using establi
 
 ## Your Task
 
+If a slice is in status 'planned', Even if a slice seems to have been implemented, make sure to verify the implementation, check for new fields, additional custom prompts in the slice json. A "planned" slice can also be an update of an existing slice. If that is the case, match the implemenetation to the updated slice definition.
+
 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:
+5. Pick the **highest priority** task assigned to ui_worker. This becomes your task. 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
@@ -16,15 +18,15 @@ Build React + TypeScript UI components from slice JSON definitions using establi
 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. Place the component where it belongs. If you can´t find a place, add a new page with /debug/<page> to showcase the component.
-14. Run quality checks ( npm run build, tsc ) - Attention - it´s enough to run the tests for the slice. Do not run all tests.
+11. make sure to read the ui-prompt.md in /backend/src/slices/<slice>/
+13. carefully read custom uiPrompt in the slice.json and follow the instructions. If no mount point is defined in uiPrompt, verify if there is natural place where to mount the component. If there is no natural place, create a new page,  name it after the Component and define a Route in App.tsx
+14. Run quality checks ( npm run build, tsc ) - Attention - the slice is only done if the component is mounted and testable.
+15. Make sure to style components according to the style guides.
 16. Update the Slice in the index.json to status 'Done' and remove assignment
-17. If checks pass, commit ALL changes with message: `feat: [Slice Name]` and merge back to main as FF merge ( update
+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.
+19. If checks pass, commit ALL changes with message: `feat: [Slice Name]` and merge back to main as FF merge ( update
     first )
-18. Append your progress to `progress.txt` after each step in the iteration.
-19. 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.
 
 ---
@@ -42,6 +44,7 @@ This project has custom skills available in `.claude/skills/` that automate comm
 - **`/ui-scaffold-component`**: Scaffold React components (List, Dialog, Page) using Bulma CSS
 
 **IMPORTANT**: When asked to build UI from slices, USE the `/ui-build-slice-ui` skill first! It will orchestrate all other skills in the correct order. Only use individual skills when you need to regenerate or modify a specific part.
+**IMPORTANT**: Unless stated in a custom prompt, components read directly from the tables provided, not from api-endpoints via HTTP
 
 ---
 

package/templates/prompt.md

@@ -5,8 +5,9 @@ You assign tasks to workers. Only one task can be assigned and in status planned
 
 ## Your Task
 
-1. find the most important next slice by watching .slices/index.json
+1. find the most important next slice by reading .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>
+5. if there is no task in status planned, return <promise>NO_TASKS</promise>
+6. If one task is done. Finish your work, do not continue with the next slice.