Software Orchestrator
5769c1cd22
- 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
1.3 KiB
1.3 KiB
name, description, tags
| name | description | tags | |||
|---|---|---|---|---|---|
| library-extractor | Extract patterns from completed project artifacts into the self-learning patterns library. |
|
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
- Identify the pattern: what worked, why it worked, when to reuse it
- Categorize: architecture_decision, best_practice, error_solution, design_pattern, etc.
- Capture: title, description, content (with code if relevant), tags, project_id
- Call the library-extractor API:
POST /api/plugins/a0_software_orchestrator/library_extract
{"title": "...", "description": "...", "category": "...", "content": "...", "tags": [...], "project_id": "..."}
- Verify the pattern was stored (check via library-query)
See Also
- Help:
library/query.md - API:
/api/plugins/a0_software_orchestrator/library_extract