dave/storkit
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 7 Wiki Activity

Renamed .living_spec in a few more places

Browse Source
This commit is contained in:
Dave
2026-02-16 15:45:44 +00:00
parent 3865883998
commit caf293a8c4
2 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
.story_kit/specs/00_CONTEXT.md
View File

@@ -29,5 +29,5 @@ To build a standalone **Agentic AI Code Assistant** application as a single Rust
## Glossary ## Glossary
* **SDSW:** Story-Driven Spec Workflow. * **SDSW:** Story-Driven Spec Workflow.
* **Web Server Binary:** The Rust binary that serves the Vite/React frontend and exposes the WebSocket API. * **Web Server Binary:** The Rust binary that serves the Vite/React frontend and exposes the WebSocket API.
* **Living Spec:** The collection of Markdown files in `.living_spec/` that define the project. * **Living Spec:** The collection of Markdown files in `.story_kit/` that define the project.
* **Tool Call:** A structured request from the LLM to execute a specific native function. * **Tool Call:** A structured request from the LLM to execute a specific native function.

2
server/src/llm/prompts.rs
View File

@@ -18,7 +18,7 @@ You have the following tools available:
YOUR WORKFLOW: YOUR WORKFLOW:
When the user requests a feature or change: When the user requests a feature or change:
1. **Understand:** Read `.living_spec/README.md` if you haven't already to understand the development process 1. **Understand:** Read `.story_kit/README.md` if you haven't already to understand the development process
2. **Explore:** Use `read_file` and `list_directory` to understand the current codebase structure 2. **Explore:** Use `read_file` and `list_directory` to understand the current codebase structure
3. **Implement:** Use `write_file` to create or modify files directly 3. **Implement:** Use `write_file` to create or modify files directly
4. **Verify:** Use `exec_shell` to run tests, linters, or build commands to verify your changes work 4. **Verify:** Use `exec_shell` to run tests, linters, or build commands to verify your changes work