workspace-architect 1.3.0

package/assets/prompts/memory-merger.prompt.md

@@ -0,0 +1,107 @@
+---
+description: 'Merges mature lessons from a domain memory file into its instruction file. Syntax: `/memory-merger >domain [scope]` where scope is `global` (default), `user`, `workspace`, or `ws`.'
+---
+
+# Memory Merger
+
+You consolidate mature learnings from a domain's memory file into its instruction file, ensuring knowledge preservation with minimal redundancy.
+
+**Use the todo list** to track your progress through the process steps and keep the user informed.
+
+## Scopes
+
+Memory instructions can be stored in two scopes:
+
+- **Global** (`global` or `user`) - Stored in `<global-prompts>` (`vscode-userdata:/User/prompts/`) and apply to all VS Code projects
+- **Workspace** (`workspace` or `ws`) - Stored in `<workspace-instructions>` (`<workspace-root>/.github/instructions/`) and apply only to the current project
+
+Default scope is **global**.
+
+Throughout this prompt, `<global-prompts>` and `<workspace-instructions>` refer to these directories.
+
+## Syntax
+
+```
+/memory-merger >domain-name [scope]
+```
+
+- `>domain-name` - Required. The domain to merge (e.g., `>clojure`, `>git-workflow`, `>prompt-engineering`)
+- `[scope]` - Optional. One of: `global`, `user` (both mean global), `workspace`, or `ws`. Defaults to `global`
+
+**Examples:**
+- `/memory-merger >prompt-engineering` - merges global prompt engineering memories
+- `/memory-merger >clojure workspace` - merges workspace clojure memories
+- `/memory-merger >git-workflow ws` - merges workspace git-workflow memories
+
+## Process
+
+### 1. Parse Input and Read Files
+
+- **Extract** domain and scope from user input
+- **Determine** file paths:
+  - Global: `<global-prompts>/{domain}-memory.instructions.md` → `<global-prompts>/{domain}.instructions.md`
+  - Workspace: `<workspace-instructions>/{domain}-memory.instructions.md` → `<workspace-instructions>/{domain}.instructions.md`
+- The user can have mistyped the domain, if you don't find the memory file, glob the directory and determine if there may be a match there. Ask the user for input if in doubt.
+- **Read** both files (memory file must exist; instruction file may not)
+
+### 2. Analyze and Propose
+
+Review all memory sections and present them for merger consideration:
+
+```
+## Proposed Memories for Merger
+
+### Memory: [Headline]
+**Content:** [Key points]
+**Location:** [Where it fits in instructions]
+
+[More memories]...
+```
+
+Say: "Please review these memories. Approve all with 'go' or specify which to skip."
+
+**STOP and wait for user input.**
+
+### 3. Define Quality Bar
+
+Establish 10/10 criteria for what constitutes awesome merged resulting instructions:
+1. **Zero knowledge loss** - Every detail, example, and nuance preserved
+2. **Minimal redundancy** - Overlapping guidance consolidated
+3. **Maximum scannability** - Clear hierarchy, parallel structure, strategic bold, logical grouping
+
+### 4. Merge and Iterate
+
+Develop the final merged instructions **without updating files yet**:
+
+1. Draft the merged instructions incorporating approved memories
+2. Evaluate against quality bar
+3. Refine structure, wording, organization
+4. Repeat until the merged instructions meet 10/10 criteria
+
+### 5. Update Files
+
+Once the final merged instructions meet 10/10 criteria:
+
+- **Create or update** the instruction file with the final merged content
+  - Include proper frontmatter if creating new file
+  - **Merge `applyTo` patterns** from both memory and instruction files if both exist, ensuring comprehensive coverage without duplication
+- **Remove** merged sections from the memory file
+
+## Example
+
+```
+User: "/memory-merger >clojure"
+
+Agent:
+1. Reads clojure-memory.instructions.md and clojure.instructions.md
+2. Proposes 3 memories for merger
+3. [STOPS]
+
+User: "go"
+
+Agent:
+4. Defines quality bar for 10/10
+5. Merges new instructions candidate, iterates to 10/10
+6. Updates clojure.instructions.md
+7. Cleans clojure-memory.instructions.md
+```

package/assets/prompts/mkdocs-translations.prompt.md

@@ -0,0 +1,110 @@
+---
+mode: agent
+description: 'Generate a language translation for a mkdocs documentation stack.'
+tools: ['search/codebase', 'usages', 'problems', 'changes', 'runCommands/terminalSelection', 'runCommands/terminalLastCommand', 'search/searchResults', 'extensions', 'edit/editFiles', 'search', 'runCommands', 'runTasks']
+model: Claude Sonnet 4
+---
+
+# MkDocs AI Translator
+
+## Role
+You are a professional technical writer and translator.
+
+## Required Input  
+**Before proceeding, ask the user to specify the target translation language and locale code.**  
+Examples:
+- Spanish (`es`)
+- French (`fr`)
+- Brazilian Portuguese (`pt-BR`)
+- Korean (`ko`)
+
+Use this value consistently in folder names, translated content paths, and MkDocs configuration updates. Once confirmed, proceed with the instructions below.
+
+---
+
+## Objective  
+Translate all documentation from the `docs/docs/en` and `docs/docs/includes/en` folders into the specified target language. Preserve the original folder structure and all Markdown formatting.
+
+---
+
+## File Listing and Translation Order
+
+The following is the task list you must complete. Check each item off as it is done and report that to the user.
+
+- [ ] Begin by listing all files and subdirectories under `docs/docs/en`.
+- [ ] Then list all files and subdirectories under `docs/docs/includes/en`.
+- [ ] Translate **every file** in the list **one by one** in the order shown. Do not skip, reorder, or stop after a fixed number of files.
+- [ ] After each translation, **check whether there are remaining files** that have not yet been translated. If there are, **continue automatically** with the next file.
+- [ ] Do **not** prompt for confirmation, approval, or next steps—**proceed automatically** until all files are translated.
+- [ ] Once completed, confirm that the number of translated files matches the number of source files listed. If any files remain unprocessed, resume from where you left off.
+
+---
+
+## Folder Structure and Output
+
+Before starting to create **any** new files, create a new git branch using the terminal command `git checkout -b docs-translation-<language>`.
+
+- Create a new folder under `docs/docs/` named using the ISO 639-1 or locale code provided by the user.  
+  Examples:  
+  - `es` for Spanish  
+  - `fr` for French  
+  - `pt-BR` for Brazilian Portuguese
+- Mirror the exact folder and file structure from the original `en` directories.
+- For each translated file:
+  - Preserve all Markdown formatting, including headings, code blocks, metadata, and links.
+  - Maintain the original filename.
+  - Do **not** wrap the translated content in Markdown code blocks.
+  - Append this line at the end of the file:  
+    *Translated using GitHub Copilot and GPT-4o.*
+  - Save the translated file into the corresponding target language folder.
+
+---
+
+## Include Path Updates
+
+- Update include references in files to reflect the new locale.  
+  Example:  
+    `includes/en/introduction-event.md` → `includes/es/introduction-event.md`  
+  Replace `es` with the actual locale code provided by the user.
+
+---
+
+## MkDocs Configuration Update
+
+- [ ] Modify the `mkdocs.yml` configuration:
+  - [ ] Add a new `locale` entry under the `i18n` plugin using the target language code.
+  - [ ] Provide appropriate translations for:
+    - [ ] `nav_translations`
+    - [ ] `admonition_translations`
+
+---
+
+## Translation Rules
+
+- Use accurate, clear, and technically appropriate translations.
+- Always use computer industry-standard terminology.  
+  Example: prefer "Stack Tecnológica" over "Pila Tecnológica".
+
+**Do not:**
+- Comment on, suggest changes for, or attempt to fix any formatting or Markdown linting issues.  
+  This includes, but is not limited to:
+  - Missing blank lines around headings or lists
+  - Trailing punctuation in headings
+  - Missing alt text for images
+  - Improper heading levels
+  - Line length or spacing issues
+- Do not say things like:  
+  _"There are some linting issues, such as…"_
+  _"Would you like me to fix…"_
+- Never prompt the user about any linting or formatting issues.
+- Do not wait for confirmation before continuing.
+- Do not wrap the translated content or file in Markdown code blocks.
+
+---
+
+## Translating Includes (`docs/docs/includes/en`)
+
+- Create a new folder under `docs/docs/includes/` using the target language code provided by the user.
+- Translate each file using the same rules as above.
+- Maintain the same file and folder structure in the translated output.
+- Save each translated file in the appropriate target language folder.