Migrate all repos into monorepo context folders
Bahn: aisupport, Analyse-O2C-C2S, awesome-bahn-mcp-servers, beam-mcp,
Confluence_Bot, db-planet-mcp-server, O2C-Harness, project-audit,
Projekt-KIQ-HP, teamlandkarte-mcp
Dhive: Jury-Voting
Privat: CV, NoteGraph (NOTE: NoteGraph needs complete redo after consolidation)
Shared: AI-Orchestrator, OrgMyLife, power_skills_and_more
Shared/references: symphony (read-only)
Bahn repos remain available as independent remotes - this monorepo
pulls them in via subtree, the originals are untouched.
This commit is contained in:
@@ -0,0 +1,45 @@
|
||||
# Knowledge Base Conventions
|
||||
|
||||
## File Naming
|
||||
|
||||
- All entity files: `<entity-id>.yaml`
|
||||
- Entity IDs: lowercase letters, numbers, hyphens only (kebab-case)
|
||||
- No leading/trailing hyphens, no double hyphens
|
||||
- Pattern: `/^[a-z0-9]+(-[a-z0-9]+)*$/`
|
||||
|
||||
## Directory Structure
|
||||
|
||||
| Path | Contents |
|
||||
|------|----------|
|
||||
| `kb/profiles/` | Person entities |
|
||||
| `kb/experiences/` | Experience entities |
|
||||
| `kb/skills/` | Skill entities |
|
||||
| `kb/organizations/` | Organization entities |
|
||||
| `kb/projects/` | Project entities |
|
||||
| `kb/certifications/` | Certification entities |
|
||||
| `kb/tandems/` | Tandem entities |
|
||||
| `kb/tracking/` | LinkedIn tracking entities |
|
||||
| `kb/graph-index.yaml` | Central graph index |
|
||||
|
||||
## Graph Index Maintenance
|
||||
|
||||
- Always update `kb/graph-index.yaml` when entities are added or removed
|
||||
- Valid relationship types: `has_skill`, `worked_at`, `collaborated_with`, `applied_for`, `partners_with`
|
||||
- All relationships must reference existing entity IDs
|
||||
- Rebuild with `src/graph/index-manager.ts` if index drifts out of sync
|
||||
|
||||
## Entity Schema Conventions
|
||||
|
||||
- Common header on every entity file: `id`, `type`, `created`, `modified`
|
||||
- Dates in ISO format: `YYYY-MM-DD` or `YYYY-MM`
|
||||
- Use `null` for open-ended dates (e.g., current role `end: null`)
|
||||
- YAML files use kebab-case keys (e.g., `skills-used`, `shared-vision`)
|
||||
- TypeScript uses camelCase (e.g., `skillsUsed`, `sharedVision`)
|
||||
|
||||
## Validation Rules
|
||||
|
||||
- Always validate entities before writing to disk
|
||||
- Temporal consistency: start ≤ end (when both are present)
|
||||
- Tandem entities must have exactly 2 partners
|
||||
- All referenced entity IDs must exist in the knowledge base
|
||||
- Use `src/schemas/validate.ts` for programmatic validation
|
||||
@@ -0,0 +1,47 @@
|
||||
---
|
||||
inclusion: auto
|
||||
---
|
||||
|
||||
# CV Project Standards
|
||||
|
||||
## Quality Gates (before every commit)
|
||||
|
||||
1. `gitleaks detect --source . --no-git` — no secrets in code
|
||||
2. `npm run typecheck` — TypeScript passes
|
||||
3. `npm test` — all vitest tests pass (252 tests, 80%+ coverage)
|
||||
4. `npm audit` — 0 vulnerabilities
|
||||
|
||||
## Conventional Commits
|
||||
|
||||
```
|
||||
feat(cv): add tandem CV template
|
||||
fix(graph): handle circular references in index
|
||||
test(interview): add property test for gap detection
|
||||
docs(readme): update entity schema section
|
||||
```
|
||||
|
||||
## Testing
|
||||
|
||||
- Vitest + fast-check for property-based testing
|
||||
- 15 formal correctness properties defined in SPEC.md
|
||||
- Given-When-Then structure
|
||||
- 80% coverage minimum
|
||||
|
||||
## Autonomous Mode
|
||||
|
||||
- Never push directly to main — use feature branches
|
||||
- Create PRs on GitHub targeting main
|
||||
- If stuck after 3 attempts: stop and document
|
||||
- Report: `PROGRESS: X%` / `HELP: description`
|
||||
|
||||
## Architecture
|
||||
|
||||
- File-based knowledge graph (YAML entities, one file per entity)
|
||||
- TypeScript for validation and logic
|
||||
- Kiro skills for workflows (interview, cv-generate, talk-intro, kb-review)
|
||||
- No build step, no server — file system is the database
|
||||
|
||||
## File Naming
|
||||
|
||||
- Entity files: kebab-case (`andre-knie.yaml`, `db-cargo-innovation-lead.yaml`)
|
||||
- All filenames OneDrive-safe (no brackets, no special chars)
|
||||
@@ -0,0 +1,78 @@
|
||||
---
|
||||
inclusion: always
|
||||
---
|
||||
|
||||
# Start — Projektübersicht & Steuerung
|
||||
|
||||
## Zweck
|
||||
|
||||
Dieses Projekt ist eine persönliche Knowledge Base mit automatisierter Generierung von CVs, Beraterprofilen und Speaker-Intros. Es nutzt strukturierte YAML-Daten und Skills zur Produktion maßgeschneiderter Dokumente.
|
||||
|
||||
## Ordnerstruktur
|
||||
|
||||
| Pfad | Inhalt |
|
||||
|------|--------|
|
||||
| `kb/` | Knowledge Base — Profile, Erfahrungen, Skills, Projekte, Zertifizierungen, Organisationen, Tandems |
|
||||
| `src/` | TypeScript Source Code — Validierung, Graph-Management, CV-Generierung, Interview, Review |
|
||||
| `templates/` | Markdown-Templates für CV und Intro-Generierung |
|
||||
| `output/` | Generierte Outputs (Profile, Intros, CVs) |
|
||||
| `assets/` | Fotos, Logos (d-hive CD) |
|
||||
| `bewerbungen/` | Stellenausschreibungen und Bewerbungsmaterial |
|
||||
| `archive/` | Ältere CVs und Referenzdokumente |
|
||||
| `sources/` | Quelldokumente für KB-Import |
|
||||
| `.kiro/skills/` | Kiro Skills (consultant-profile, cv-generate, interview-collect, kb-review, talk-intro) |
|
||||
| `.kiro/steering/` | Steering-Dateien (kb-conventions, start) |
|
||||
| `.kiro/specs/` | Spec-Dokumente |
|
||||
|
||||
## Wesentliche Steuerungsdokumente
|
||||
|
||||
1. **SPEC.md** — Technische Spezifikation des Projekts (Source of Truth)
|
||||
2. **AGENTS.md** — Coding Rules, Git-Workflow, Dokumentationsregeln
|
||||
3. **RULES.md** — Zusätzliche Projektregeln
|
||||
4. **README.md** — Projektbeschreibung
|
||||
5. **.kiro/steering/kb-conventions.md** — KB-Konventionen (Dateinamen, Schema, Validierung)
|
||||
|
||||
## Skills (verfügbar via `#`-Kontext)
|
||||
|
||||
| Skill | Zweck |
|
||||
|-------|-------|
|
||||
| `consultant-profile` | Beraterprofil (HTML One-Pager) aus KB + RFP generieren |
|
||||
| `cv-generate` | CV aus KB + Stellenausschreibung generieren |
|
||||
| `talk-intro` | Speaker-Intro in 3 Längenvarianten generieren |
|
||||
| `interview-collect` | Interview-Session zur KB-Erweiterung |
|
||||
| `kb-review` | KB-Review mit Completeness-Scoring |
|
||||
|
||||
## Corporate Design (d-hive)
|
||||
|
||||
- **Farben:** Schwarz (#0a0a0a) + Neon-Grün (#39ff14)
|
||||
- **Auf weißem Hintergrund:** Schwarz für Struktur, Neon-Grün für Highlights
|
||||
- **Logo (heller BG):** `assets/d-Hive_logo_darkText_transparent_crop.png`
|
||||
- **Logo (dunkler BG):** `assets/d-Hive_logo_transparent_crop.png`
|
||||
- **Foto André:** `assets/230823_Einfachbahn_Andre-brillenlos-hochformat.png`
|
||||
- **Typografie:** Inter (Google Fonts)
|
||||
|
||||
## Key Facts (für Stats-Bars)
|
||||
|
||||
- 50+ Projekte, 15+ Kunden
|
||||
- 13+ Jahre KI-Erfahrung (erste ML-Publikation 2012)
|
||||
- 60+ wissenschaftliche Veröffentlichungen, 2.000+ Zitationen
|
||||
- 6 Live Use Cases (Projekt KIQ)
|
||||
- 100% DSGVO & AI-Act konform
|
||||
|
||||
## Session-Routing
|
||||
|
||||
Wenn die erste Nachricht des Users vage ist oder ein Gruß (z.B. "hi", "hallo", "was geht?"), biete folgende Optionen an:
|
||||
|
||||
1. **Introduction erstellen** — Speaker-Intro oder Kurztext für ein Event generieren
|
||||
2. **CV / Beraterprofil erstellen** — CV oder Consultant One-Pager passend zu einer Stellenausschreibung oder RFP generieren
|
||||
3. **Neuen Input liefern** — Neue Informationen in die Knowledge Base eintragen (Interview, Korrekturen, Updates)
|
||||
4. **Sonstiges** — Etwas anderes
|
||||
|
||||
Wenn die Nachricht bereits klar erkennen lässt, was gewünscht ist (z.B. ein RFP wird eingefügt oder "erstell mir eine Intro für..."), überspringe das Menü und starte direkt mit dem passenden Skill.
|
||||
|
||||
## Quick Start
|
||||
|
||||
1. Lies `SPEC.md` für die technische Architektur
|
||||
2. Lies `.kiro/steering/kb-conventions.md` für KB-Regeln
|
||||
3. Nutze Skills via `#consultant-profile`, `#cv-generate`, `#talk-intro`, etc.
|
||||
4. Outputs landen in `output/`
|
||||
Reference in New Issue
Block a user