Initial commit: a0_software_orchestrator v1.0

- Auto-Registration-Bug behoben (register_project/get_project_id/resolve_project Trennung)
- 25 Tests gruen (Pytest)
- block_compactor-Tool refactored (Option B: Soft-Check statt Hard-Block)
- 4 Restbaustellen gefixt
- DB-Schema: plugin_settings-Tabelle hinzugefuegt
- 3 Schattenprojekte aus DB geloescht
- Plan v3 + Refactor-Plan + Worklog dokumentiert
This commit is contained in:
Software Orchestrator
2026-06-16 22:13:06 +00:00
commit 5769c1cd22
236 changed files with 17825 additions and 0 deletions
+36
View File
@@ -0,0 +1,36 @@
---
name: library-extractor
description: Extract patterns from completed project artifacts into the self-learning patterns library.
tags: ['library', 'extract', 'learning']
---
# Library Extractor
## Purpose
Capture reusable patterns from completed project work and store them in the patterns library for future reuse.
## When to Use
- After a major project milestone
- When a novel design decision is made
- When an error is resolved with a non-obvious solution
- When a best practice is discovered
## When Not to Use
- For trivial implementations (CRUD, boilerplate)
- For project-specific code (not reusable)
- For incomplete work (wait for validation)
## Procedure
1. Identify the pattern: what worked, why it worked, when to reuse it
2. Categorize: architecture_decision, best_practice, error_solution, design_pattern, etc.
3. Capture: title, description, content (with code if relevant), tags, project_id
4. Call the library-extractor API:
```
POST /api/plugins/a0_software_orchestrator/library_extract
{"title": "...", "description": "...", "category": "...", "content": "...", "tags": [...], "project_id": "..."}
```
5. Verify the pattern was stored (check via library-query)
## See Also
- Help: `library/query.md`
- API: `/api/plugins/a0_software_orchestrator/library_extract`
+37
View File
@@ -0,0 +1,37 @@
---
name: library-query
description: Query the patterns library for relevant patterns, best practices, and known errors.
tags: ['library', 'query', 'search']
---
# Library Query
## Purpose
Find relevant patterns from the self-learning library before starting work, to avoid reinventing solutions and to apply known best practices.
## When to Use
- At the start of any new project or task
- When designing architecture for a new feature
- When debugging an error (find prior solutions)
- When planning a phase
## When Not to Use
- For trivial questions (just ask)
- For project-specific state (read the project files)
## Procedure
1. Formulate query keywords: technology, problem type, domain, project type
2. Call the library-query API:
```
GET /api/plugins/a0_software_orchestrator/library_search?q=<keywords>
```
3. Review top results by relevance
4. For each relevant pattern, read the full content via:
```
GET /api/plugins/a0_software_orchestrator/library_get?id=<pattern_id>
```
5. Apply the pattern to the current work, citing the pattern_id
## See Also
- Help: `library/extract.md`
- API: `/api/plugins/a0_software_orchestrator/library_search`