@powerhousedao/academy 4.1.0-dev.55 → 4.1.0-dev.57

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 (6) hide show
  1. package/CHANGELOG.md +32 -11
  2. package/docs/academy/01-GetStarted/01-CreateNewPowerhouseProject.md +10 -11
  3. package/docs/academy/01-GetStarted/02-DefineToDoListDocumentModel.md +1 -1
  4. package/docs/academy/01-GetStarted/05-SpecDrivenAI.md +26 -19
  5. package/package.json +1 -1
  6. package/tsconfig.tsbuildinfo +1 -0
package/CHANGELOG.md CHANGED
@@ -1,3 +1,26 @@
1
+ ## 4.1.0-dev.57 (2025-09-17)
2
+
3
+ ### 🚀 Features
4
+
5
+ - **monorepo:** empty commit to satisfy naming ([5aa18f417](https://github.com/powerhouse-inc/powerhouse/commit/5aa18f417))
6
+ - **monorepo:** merge main ([79f6472b1](https://github.com/powerhouse-inc/powerhouse/commit/79f6472b1))
7
+ - **monorepo:** update release branch workflow ([e9c221ab5](https://github.com/powerhouse-inc/powerhouse/commit/e9c221ab5))
8
+
9
+ ### 🩹 Fixes
10
+
11
+ - **monorepo:** re-add nx js plugin ([d477a49d7](https://github.com/powerhouse-inc/powerhouse/commit/d477a49d7))
12
+ - **monorepo:** regenerate lockfile ([7811171ff](https://github.com/powerhouse-inc/powerhouse/commit/7811171ff))
13
+ - **monorepo:** linting and type checking ([#1776](https://github.com/powerhouse-inc/powerhouse/pull/1776))
14
+
15
+ ### ❤️ Thank You
16
+
17
+ - Ryan Wolhuter @ryanwolhuter
18
+ - ryanwolhuter @ryanwolhuter
19
+
20
+ ## 4.1.0-dev.56 (2025-09-17)
21
+
22
+ This was a version bump only for @powerhousedao/academy to align it with other projects, there were no code changes.
23
+
1
24
  ## 4.1.0-dev.55 (2025-09-16)
2
25
 
3
26
  ### 🚀 Features
@@ -54,29 +77,27 @@ This was a version bump only for @powerhousedao/academy to align it with other p
54
77
  - Callme-T
55
78
  - ryanwolhuter @ryanwolhuter
56
79
 
57
- ## 4.1.0-dev.50 (2025-09-09)
80
+ ## 5.0.0-staging.9 (2025-09-09)
58
81
 
59
82
  This was a version bump only for @powerhousedao/academy to align it with other projects, there were no code changes.
60
83
 
61
- ## 4.1.0-dev.49 (2025-09-09)
84
+ ## 5.0.0-staging.8 (2025-09-09)
62
85
 
63
86
  This was a version bump only for @powerhousedao/academy to align it with other projects, there were no code changes.
64
87
 
65
- ## 4.1.0-dev.48 (2025-09-09)
88
+ ## 5.0.0-staging.7 (2025-09-09)
66
89
 
67
90
  This was a version bump only for @powerhousedao/academy to align it with other projects, there were no code changes.
68
91
 
69
- ## 4.1.0-dev.47 (2025-09-06)
92
+ ## 5.0.0-staging.6 (2025-09-08)
70
93
 
71
- ### 🩹 Fixes
72
-
73
- - **docs:** added zip redundancy to release notes ([3acfe1027](https://github.com/powerhouse-inc/powerhouse/commit/3acfe1027))
94
+ This was a version bump only for @powerhousedao/academy to align it with other projects, there were no code changes.
74
95
 
75
- ### ❤️ Thank You
96
+ ## 5.0.0-staging.5 (2025-09-08)
76
97
 
77
- - Callme-T
98
+ This was a version bump only for @powerhousedao/academy to align it with other projects, there were no code changes.
78
99
 
79
- ## 4.1.0-dev.46 (2025-09-05)
100
+ ## 5.0.0-staging.4 (2025-09-08)
80
101
 
81
102
  This was a version bump only for @powerhousedao/academy to align it with other projects, there were no code changes.
82
103
 
@@ -1201,4 +1222,4 @@ This was a version bump only for @powerhousedao/academy to align it with other p
1201
1222
 
1202
1223
  ### ❤️ Thank You
1203
1224
 
1204
- - Frank
1225
+ - Frank
package/docs/academy/01-GetStarted/01-CreateNewPowerhouseProject.md CHANGED
@@ -42,24 +42,25 @@ ph init
42
42
  ? What is the project name? ‣ getting-started
43
43
  ```
44
44
 
45
- Once the project is created, you will see the following output:
45
+
46
+ Once the project is created, you will see the following output:
46
47
  ```bash
47
48
  Initialized empty Git repository in /Users/you/ph-projects/getting-started/.git/
48
49
  The installation is done!
49
50
  ```
50
51
 
51
- Navigate to the newly created project directory:
52
+ Navigate to the newly created project directory:
52
53
  ```bash
53
54
  cd getting-started
54
55
  ```
55
- Once in the project directory, run the `ph connect` command to start a local instance of the Connect application. This allows you to start your document model specification document.
56
- Run the following command to start the Connect application:
56
+ Once in the project directory, run the `ph connect` command to start a local instance of the Connect application. This allows you to start your document model specification document.
57
+ Run the following command to start the Connect application:
57
58
 
58
59
  ```bash
59
60
  ph connect
60
61
  ```
61
62
 
62
- The Connect application will start and you will see the following output:
63
+ The Connect application will start and you will see the following output:
63
64
 
64
65
  ```bash
65
66
  ➜ Local: http://localhost:3000/
@@ -67,13 +68,11 @@ ph init
67
68
  ➜ press h + enter to show help
68
69
  ```
69
70
 
70
- A new browser window will open and you will see the Connect application. If it doesn't open automatically, you can open it manually by navigating to `http://localhost:3000/` in your browser.
71
-
72
- You will see your local drive and a button to create a new drive.
73
- If you local drive is not present navigate into Settings in the bottom left corner. Settings > Danger Zone > Clear Storage.
74
- Clear the storage of your localhost application as it might has an old session cached.
71
+ A new browser window will open and you will see the Connect application. If it doesn't open automatically, you can open it manually by navigating to `http://localhost:3000/` in your browser.
75
72
 
76
- ````
73
+ You will see your local drive and a button to create a new drive.
74
+ If you local drive is not present navigate into Settings in the bottom left corner. Settings > Danger Zone > Clear Storage.
75
+ Clear the storage of your localhost application as it might has an old session cached.
77
76
 
78
77
  4. Move into your local drive.
79
78
  Create a new document model by clicking the `DocumentModel` button, found in the 'New Document' section at the bottom of the page.
package/docs/academy/01-GetStarted/02-DefineToDoListDocumentModel.md CHANGED
@@ -113,4 +113,4 @@ Check below screenshot for the complete implementation:
113
113
  ### Up next: reducers
114
114
 
115
115
  Up next, you'll learn how to implement the runtime logic and components that will use the `ToDoList` document model specification you've just created and exported.
116
- ````
116
+
package/docs/academy/01-GetStarted/05-SpecDrivenAI.md CHANGED
@@ -1,23 +1,29 @@
1
- # Spec-Driven AI
1
+ # Vetra Studio: Specification Driven AI
2
2
 
3
- This chapter introduces you to one of the most powerfull features of the Powerhouse development framework.
4
- In this *Get Started'* chapter we've been making use of strict schema definition principles to communicate the intended use case. This shared language is not only a language that bridges the gap between developer, designer and analyst but also the gap between builder and AI-agent.
3
+ This chapter introduces you to one of the most powerfull features of the Powerhouse development framework: Specification Driven AI-control. In the **'Get Started'** chapter we've been making use of strict schema definition principles to communicate the intended use case of our reactive documents.
4
+
5
+ :::tip
6
+ The **schema definition language**, is a not only a shared language that bridges the gap between developer, designer and analyst but also the gap between **builder and AI-agent**.
7
+ :::
5
8
 
6
9
  ## Vision
7
10
 
8
- At Powerhouse we are embracing the progress of AI assisted coding while unlocking the next level of AI control through specification driven AI control.
11
+ At Powerhouse we are embracing the progress of AI assisted coding while unlocking the next level of AI control through **specification driven AI control**.
9
12
 
10
13
  - Communicate your solution and intent through a structured specification framework designed for AI collaboration.
11
14
  - Specifications enable precise, iterative edits, since all our specification documents are machine-readable and executable.
12
15
  - Specifications offer the ability to update exact parameters and properties as your specs evolve in lock-step with your agent.
13
- - Specs turn fragile sandcastles into solid, editable, and maintainable functionality with predictable results, so you can deliver AI driven projects to production environments with piece of mind.
16
+ - Specifications turn fragile sandcastles into solid, editable, and maintainable functionality with predictable results.
14
17
 
15
18
  This approach allows for the creation of editable specifications, enabling business analysts to modify details and instruct the AI to generate code based on updated specifications.
16
19
  It results in composable, maintainable, and scalable functionality.
17
20
 
18
21
  ## Introducing Vetra Studio
19
22
 
20
- Vetra studio functions as the orchestration hub where you as a builder assemble all the necessary specifications for your intended use-case, software solution or package. For each of the different *modules* that together form a package a specification document can be created in *Vetra Studio*.
23
+ **Vetra Studio** serves as a centralized hub for developers to access and manage specifications.
24
+ It allows developers to open packages (Git repositories with metadata) from a Vetra package library, providing access to a remote Vetra drive where all specifications are stored.
25
+
26
+ This setup ensures that all necessary documentation and project requirements are in one accessible location, streamlining communication and agreement on requirements and operations. Additionally, **Vetra Studio** functions as the orchestration hub where you as a builder assemble all the necessary specifications for your intended use-case, software solution or package. For each of the different **modules** that together form a package a specification document can be created in **Vetra Studio**.
21
27
 
22
28
  As Vetra Studio matures each of these specification documents will offer an interface by which you as a builder get more control over the modules that make up your package. These modules are divided in 3 categories.
23
29
 
@@ -28,7 +34,7 @@ As Vetra Studio matures each of these specification documents will offer an inte
28
34
  - **Editor specification**: Outlines the interface and functionalities of a document model editor, allowing users to interact with and modify document data.
29
35
  - **Drive-app specification**: Specifies the UI and interactions for managing documents within a Drive, providing tailored views and functionalities.
30
36
 
31
- ### 3 Data intagrations
37
+ ### 3. Data integrations
32
38
  - **Subgraph specification**: Details the connections and relationships within a subgraph, facilitating efficient data querying and manipulation.
33
39
  - **Codegen Processor Specification**: Describes the process for automatically generating code from document model specifications, ensuring alignment with intended architecture.
34
40
  - **RelationalDb Processor Specification**: Defines how relational databases are structured and queried, supporting efficient data management and retrieval.
@@ -60,18 +66,18 @@ In standard mode:
60
66
 
61
67
  ### 2. Launch Claude with MCP
62
68
 
63
- Vetra Studio integrates deeply with Claude through MCP (Model Control Protocol):
69
+ Vetra Studio integrates deeply with Claude through MCP (Model Control Protocol). This is where AI comes into the mix and you get the chance to have greater control and direction over what your llm is coding for you.
64
70
 
65
- 1. Start the MCP reactor:
71
+ #### 1. Start the MCP reactor:
66
72
  ```bash
67
73
  ph mcp
68
74
  ```
69
75
 
70
- 2. Verify MCP connection:
76
+ #### 2. Verify MCP connection:
71
77
  - Check that the reactor MCP is available
72
78
  - Confirm Vetra Studio shows "Connected to reactor MCP"
73
79
 
74
- Key MCP Features:
80
+ #### Key MCP Features:
75
81
  - Automatic document model creation from natural language descriptions
76
82
  - Smart editor generation based on document models
77
83
  - Uses reactor recipes for consistent code generation
@@ -79,11 +85,12 @@ Key MCP Features:
79
85
 
80
86
  The powerhouse config includes a vetra URL for consistent project configuration across different environments.
81
87
 
82
- ### Integration with Custom Drives:
88
+ :::tip
83
89
  - Vetra supports integration with custom remote drives, allowing users to create and manage documents within these drives.
84
90
  - The MCP server enables the agent to work with both existing and newly created document models.
91
+ :::
85
92
 
86
- ### 3. Document Creation Workflow
93
+ ### 3. Vetra Studio Package Creation Workflow
87
94
 
88
95
  #### A. Set Package Description (Required)
89
96
  1. Provide a name for your package
@@ -105,7 +112,7 @@ You can create document models in two ways:
105
112
  - Define document schema with fields and types
106
113
  - Create necessary operations
107
114
  - Add required modules
108
- - Reference the document modeling material for detailed guidance
115
+ - The document model creation chapter in the Mastery track provides support [here](apps/academy/docs/academy/MasteryTrack/DocumentModelCreation/SpecifyTheStateSchema)
109
116
 
110
117
  #### C. Add Document Editor (Required)
111
118
  1. **Using MCP (AI-Assisted)**
@@ -129,15 +136,15 @@ Support for:
129
136
 
130
137
  ### Best Practices
131
138
 
132
- 1. **Working with MCP**
133
- - Provide clear, specific instructions
134
- - Review generated schemas before confirmation
135
- - Verify implementation details in generated code
139
+ 1. **Working with MCP and claude**
140
+ - Provide clear, specific instructions and ask for clarifying questions to be answered before code generation.
141
+ - Review generated schemas before confirmation and work in layers instead of 'one-shotting' your code.
142
+ - Verify implementation details in generated code before continuing.
136
143
 
137
144
  2. **General Tips**
138
145
  - Use interactive mode during development
139
146
  - Review changes before confirmation
140
147
  - Double-check proposed next actions
141
- - Ask clarifying questions when needed
148
+ - Ask clarifying questions and double check if the task is understood correctly when needed.
142
149
 
143
150
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@powerhousedao/academy",
3
- "version": "4.1.0-dev.55",
3
+ "version": "4.1.0-dev.57",
4
4
  "homepage": "https://powerhouse.academy",
5
5
  "repository": {
6
6
  "type": "git",
package/tsconfig.tsbuildinfo ADDED
@@ -0,0 +1 @@
1
+ {"root":["./babel.config.js","./docusaurus.config.ts","./sidebars.ts","./scripts/generate-combined-cli-docs.ts","./src/components/HomepageFeatures/index.tsx","./src/pages/_archive-homepage.tsx","./src/theme/DocCardList/index.tsx"],"version":"5.9.2"}