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.
2026-06-30 20:39:52 +02:00
parent 2f2b295531
commit a5f8fb49ab
1717 changed files with 447332 additions and 0 deletions
@@ -0,0 +1,135 @@
+# CV Formatting Guide
+
+Reference document for consistent CV formatting in generated output.
+
+## Section Structure and Ordering
+
+### Individual CV Sections
+
+1. **Header** — Name, contact details, professional summary
+2. **Professional Summary** — 2–4 sentence overview tailored to the target role
+3. **Key Skills** — Grouped by category, most relevant to the posting listed first
+4. **Professional Experience** — Reverse chronological, relevant roles expanded with achievements
+5. **Projects** — Selected projects demonstrating relevant competencies
+6. **Education** — Degrees and institutions
+7. **Certifications** — Relevant certifications with issuer and date
+8. **Languages** — Language proficiency levels
+9. **Publications** — If applicable and relevant
+
+### Tandem CV Sections
+
+1. **Header** — Both partner names, "Job Sharing Tandem" label
+2. **Tandem Introduction** — Shared vision and collaboration model
+3. **Complementary Skills Overview** — How the partners' skills complement each other
+4. **Joint Competencies** — Competencies the tandem brings together
+5. **Partner A Profile** — Condensed individual profile (summary, key skills, top experiences)
+6. **Partner B Profile** — Condensed individual profile (summary, key skills, top experiences)
+7. **Combined Experience Timeline** — Merged chronological view of both partners' relevant experience
+8. **Education & Certifications** — Combined list from both partners
+
+## Formatting Conventions
+
+### Dates
+
+- Format: `MM/YYYY` (e.g., `04/2023`)
+- Current/ongoing roles: `MM/YYYY – present`
+- Date ranges: `MM/YYYY – MM/YYYY`
+- Education with only years: `YYYY – YYYY`
+
+### Skills
+
+- Group by category: Programming Languages, Frameworks, Methodologies, Soft Skills, Domain Knowledge
+- Within each category, list most relevant to the posting first
+- Use the skill name exactly as stored in the knowledge base
+- Include skill level only when it adds value (e.g., "Python (expert)")
+
+### Experiences
+
+- Format: **Role Title** | Organization | Date Range
+- Follow with 2–4 bullet points highlighting achievements and responsibilities
+- Prioritize achievements that match the job posting requirements
+- Use action verbs at the start of each bullet point
+
+### Achievements
+
+- Start with an action verb (Led, Developed, Implemented, Designed, Managed)
+- Include quantifiable results where available
+- Keep each bullet to one or two sentences
+
+### Projects
+
+- Format: **Project Name** — Brief description
+- Include technologies used and outcome/impact
+- Only include projects relevant to the target posting
+
+### Certifications
+
+- Format: **Certification Name** — Issuer, Date
+- Include expiry date if applicable: `(expires MM/YYYY)`
+
+### Languages
+
+- Format: Language — Level (e.g., "German — Native", "English — Fluent")
+
+## Tandem-Specific Formatting
+
+### Tandem Header
+
+```markdown
+# [Partner A Name] & [Partner B Name]
+## Job Sharing Tandem Application
+### [Target Role Title]
+```
+
+### Complementary Skills Presentation
+
+Present as a two-column comparison or paired list showing how skills complement:
+
+```markdown
+| Area | Partner A | Partner B |
+|------|-----------|-----------|
+| Technical Leadership | Cloud architecture, AI/ML | Data engineering, DevOps |
+| Management | Strategic planning | Operational execution |
+```
+
+### Collaboration Model
+
+Describe the working arrangement in 2–3 sentences covering:
+- How responsibilities are divided
+- Communication and handoff approach
+- Availability model (e.g., split days, alternating weeks)
+
+## Markdown Output Guidelines
+
+### Document Structure
+
+- Use `#` for the CV title (person name or tandem names)
+- Use `##` for major sections (Professional Experience, Skills, etc.)
+- Use `###` for subsections (individual roles, project entries)
+- Use `---` horizontal rules to separate major sections visually
+
+### Text Formatting
+
+- **Bold** for role titles, company names, and section emphasis
+- *Italic* for dates and supplementary context
+- Unordered lists (`-`) for achievements and skill lists
+- Tables for structured comparisons (tandem skills, language levels)
+
+### Whitespace
+
+- One blank line between sections
+- No trailing whitespace
+- End file with a single newline
+
+### Metadata Block
+
+Include a YAML front matter block at the top of each generated CV:
+
+```markdown
+---
+generated: YYYY-MM-DD
+person: <person-id>
+posting: <brief posting identifier>
+type: individual | tandem
+---
+```