claudient 0.1.0

package/prompts/task-specific/es/debugging.md

@@ -0,0 +1,78 @@
+> 🇪🇸 Esta es la traducción en español. [Versión en inglés](../debugging.md).
+
+# Prompt: Depuración Estructurada
+
+Usa este prompt cuando entregues un bug a Claude para un diagnóstico sistemático.
+
+---
+
+## Prompt completo de depuración
+
+```
+I have a bug. Help me diagnose it systematically.
+
+## The symptom
+[Describe exactly what goes wrong: error message, unexpected output, wrong behavior.
+Include the exact error text if there is one.]
+
+## Reproduction
+[Describe how to reproduce it — steps, curl command, test case, or "cannot reliably reproduce"]
+
+## What I've already tried
+[List anything you've already checked or changed — saves Claude from repeating it]
+
+## Relevant files
+[List the files most likely involved — or ask Claude to identify them]
+
+## Recent changes
+[What changed recently in this area? Paste relevant git log output if helpful]
+
+---
+
+Using this information:
+
+1. Identify the 3 most likely root causes, ranked by probability
+2. For each cause, describe a specific test that would confirm or rule it out
+3. Start with the highest-probability cause
+4. Do not fix anything yet — diagnose first
+
+After each test, report what you found and move to the next hypothesis or proceed to fix.
+```
+
+---
+
+## Variante rápida (bugs obvios)
+
+Para bugs donde la causa es aproximadamente conocida:
+
+```
+Bug: [describe the symptom]
+Likely cause: [your hypothesis]
+Relevant code: [paste the relevant function or file]
+
+Confirm whether my hypothesis is correct, then apply the minimal fix.
+Write a regression test after fixing.
+```
+
+---
+
+## Variante de incidente de producción
+
+Para incidentes en vivo donde la velocidad importa:
+
+```
+PRODUCTION INCIDENT — [service name] is [symptom]
+
+Immediate priority: identify the blast radius and any actions to reduce user impact NOW.
+
+Then diagnose:
+- Error logs: [paste relevant log lines]
+- Recent deployments: [list last 3 deploys with timestamps]
+- Affected users: [number/percentage if known]
+
+What is the fastest safe mitigation while we find the root cause?
+```
+
+---
+
+> **Trabaja con nosotros:** Claudient está respaldado por [Uitbreiden](https://uitbreiden.com/) — construimos productos de IA y soluciones B2B con comunidades de desarrolladores. [uitbreiden.com](https://uitbreiden.com/)

package/prompts/task-specific/es/pr-description.md

@@ -0,0 +1,69 @@
+> 🇪🇸 Esta es la traducción en español. [Versión en inglés](../pr-description.md).
+
+# Prompt: Generar Descripción de PR
+
+Usa este prompt para generar una descripción de pull request de alta calidad a partir de tus cambios.
+
+---
+
+## Prompt
+
+```
+Write a pull request description for the following changes.
+
+Branch: [branch name]
+Base: main
+
+Changed files:
+[paste: git diff --stat main...HEAD]
+
+What this PR does:
+[one sentence — the user should fill this in so Claude has intent, not just diff]
+
+Write the PR description with these sections:
+
+## Summary
+[2–4 bullet points: what changed and why, from the reader's perspective]
+
+## Motivation
+[one short paragraph: what problem this solves or what improvement it makes]
+
+## Changes
+[bullet list of meaningful changes — not a file list, but behavioral/structural changes]
+
+## Test plan
+[bulleted checklist of how a reviewer can verify this works:
+- specific steps to test
+- edge cases to check
+- what a successful result looks like]
+
+## Notes
+[anything a reviewer needs to know: breaking changes, migration steps, follow-up work, known limitations]
+
+Rules:
+- No generic filler ("this PR improves the codebase")
+- No file lists (the diff already shows files)
+- Specific and concrete — a reviewer should be able to test this without asking questions
+- If there are no notes, omit the Notes section
+```
+
+---
+
+## Variante rápida (PRs pequeños)
+
+Para cambios pequeños y obvios:
+
+```
+Write a concise PR description for this change: [describe the change in one sentence]
+
+Include:
+- What: one sentence
+- Why: one sentence  
+- How to test: one or two specific steps
+
+Keep it under 100 words total.
+```
+
+---
+
+> **Trabaja con nosotros:** Claudient está respaldado por [Uitbreiden](https://uitbreiden.com/) — construimos productos de IA y soluciones B2B con comunidades de desarrolladores. [uitbreiden.com](https://uitbreiden.com/)

package/prompts/task-specific/fr/changelog.md

@@ -0,0 +1,83 @@
+> 🇫🇷 This is the French translation. [English version](../changelog.md).
+
+# Prompt : Générer un Changelog
+
+Utilisez ce prompt pour générer un changelog orienté utilisateur depuis l'historique git ou une liste de changements.
+
+---
+
+## Depuis git log
+
+```
+Generate a user-facing changelog for version [X.Y.Z].
+
+Git log since last release:
+[paste: git log v[prev-version]..HEAD --oneline]
+
+Rules:
+- Write for users, not developers — explain impact, not implementation
+- Group by: New Features / Improvements / Bug Fixes / Breaking Changes
+- Omit: chore commits, dependency bumps, internal refactors with no user impact
+- Breaking changes section must be first if it exists
+- Each entry: one sentence, active voice, present tense ("Adds X", "Fixes Y", "Removes Z")
+- If a commit is unclear, ask me rather than guess
+
+Format:
+## [X.Y.Z] — [YYYY-MM-DD]
+
+### Breaking Changes
+- ...
+
+### New Features
+- ...
+
+### Improvements
+- ...
+
+### Bug Fixes
+- ...
+```
+
+---
+
+## Depuis une liste de changements
+
+```
+Generate a user-facing changelog entry for these changes:
+
+[paste bullet list of what changed]
+
+Target audience: [developers using our API / end users of the web app / etc.]
+
+Rules:
+- User impact first — "You can now X" not "We added Y"
+- Group related changes under one entry
+- One sentence per entry
+- No technical jargon unless the audience is technical
+```
+
+---
+
+## Format Keep a Changelog
+
+```
+Generate a changelog entry following the Keep a Changelog format (keepachangelog.com).
+
+Changes:
+[describe or paste git log]
+
+Version: [X.Y.Z]
+Date: [YYYY-MM-DD]
+
+Use these exact section headers where applicable:
+### Added
+### Changed
+### Deprecated
+### Removed
+### Fixed
+### Security
+```
+
+---
+
+> **Travaillez avec nous :** Claudient est soutenu par [Uitbreiden](https://uitbreiden.com/) — nous construisons des produits IA et des solutions B2B avec des communautés de développeurs. [uitbreiden.com](https://uitbreiden.com/)

package/prompts/task-specific/fr/debugging.md

@@ -0,0 +1,78 @@
+> 🇫🇷 This is the French translation. [English version](../debugging.md).
+
+# Prompt : Débogage Structuré
+
+Utilisez ce prompt quand vous confiez un bug à Claude pour un diagnostic systématique.
+
+---
+
+## Prompt de débogage complet
+
+```
+I have a bug. Help me diagnose it systematically.
+
+## The symptom
+[Describe exactly what goes wrong: error message, unexpected output, wrong behavior.
+Include the exact error text if there is one.]
+
+## Reproduction
+[Describe how to reproduce it — steps, curl command, test case, or "cannot reliably reproduce"]
+
+## What I've already tried
+[List anything you've already checked or changed — saves Claude from repeating it]
+
+## Relevant files
+[List the files most likely involved — or ask Claude to identify them]
+
+## Recent changes
+[What changed recently in this area? Paste relevant git log output if helpful]
+
+---
+
+Using this information:
+
+1. Identify the 3 most likely root causes, ranked by probability
+2. For each cause, describe a specific test that would confirm or rule it out
+3. Start with the highest-probability cause
+4. Do not fix anything yet — diagnose first
+
+After each test, report what you found and move to the next hypothesis or proceed to fix.
+```
+
+---
+
+## Variante rapide (bugs évidents)
+
+Pour les bugs dont la cause est approximativement connue :
+
+```
+Bug: [describe the symptom]
+Likely cause: [your hypothesis]
+Relevant code: [paste the relevant function or file]
+
+Confirm whether my hypothesis is correct, then apply the minimal fix.
+Write a regression test after fixing.
+```
+
+---
+
+## Variante incident de production
+
+Pour les incidents en direct où la vitesse est importante :
+
+```
+PRODUCTION INCIDENT — [service name] is [symptom]
+
+Immediate priority: identify the blast radius and any actions to reduce user impact NOW.
+
+Then diagnose:
+- Error logs: [paste relevant log lines]
+- Recent deployments: [list last 3 deploys with timestamps]
+- Affected users: [number/percentage if known]
+
+What is the fastest safe mitigation while we find the root cause?
+```
+
+---
+
+> **Travaillez avec nous :** Claudient est soutenu par [Uitbreiden](https://uitbreiden.com/) — nous construisons des produits IA et des solutions B2B avec des communautés de développeurs. [uitbreiden.com](https://uitbreiden.com/)

package/prompts/task-specific/fr/pr-description.md

@@ -0,0 +1,69 @@
+> 🇫🇷 This is the French translation. [English version](../pr-description.md).
+
+# Prompt : Générer une Description de PR
+
+Utilisez ce prompt pour générer une description de pull request de haute qualité à partir de vos changements.
+
+---
+
+## Prompt
+
+```
+Write a pull request description for the following changes.
+
+Branch: [branch name]
+Base: main
+
+Changed files:
+[paste: git diff --stat main...HEAD]
+
+What this PR does:
+[one sentence — the user should fill this in so Claude has intent, not just diff]
+
+Write the PR description with these sections:
+
+## Summary
+[2–4 bullet points: what changed and why, from the reader's perspective]
+
+## Motivation
+[one short paragraph: what problem this solves or what improvement it makes]
+
+## Changes
+[bullet list of meaningful changes — not a file list, but behavioral/structural changes]
+
+## Test plan
+[bulleted checklist of how a reviewer can verify this works:
+- specific steps to test
+- edge cases to check
+- what a successful result looks like]
+
+## Notes
+[anything a reviewer needs to know: breaking changes, migration steps, follow-up work, known limitations]
+
+Rules:
+- No generic filler ("this PR improves the codebase")
+- No file lists (the diff already shows files)
+- Specific and concrete — a reviewer should be able to test this without asking questions
+- If there are no notes, omit the Notes section
+```
+
+---
+
+## Variante rapide (petites PRs)
+
+Pour les petits changements évidents :
+
+```
+Write a concise PR description for this change: [describe the change in one sentence]
+
+Include:
+- What: one sentence
+- Why: one sentence  
+- How to test: one or two specific steps
+
+Keep it under 100 words total.
+```
+
+---
+
+> **Travaillez avec nous :** Claudient est soutenu par [Uitbreiden](https://uitbreiden.com/) — nous construisons des produits IA et des solutions B2B avec des communautés de développeurs. [uitbreiden.com](https://uitbreiden.com/)

package/prompts/task-specific/nl/changelog.md

@@ -0,0 +1,83 @@
+> 🇳🇱 Dit is de Nederlandse vertaling. [Engelse versie](../changelog.md).
+
+# Prompt: Changelog Genereren
+
+Gebruik deze prompt om een gebruikersgericht changelog te genereren vanuit git-geschiedenis of een lijst van wijzigingen.
+
+---
+
+## Vanuit git log
+
+```
+Generate a user-facing changelog for version [X.Y.Z].
+
+Git log since last release:
+[paste: git log v[prev-version]..HEAD --oneline]
+
+Rules:
+- Write for users, not developers — explain impact, not implementation
+- Group by: New Features / Improvements / Bug Fixes / Breaking Changes
+- Omit: chore commits, dependency bumps, internal refactors with no user impact
+- Breaking changes section must be first if it exists
+- Each entry: one sentence, active voice, present tense ("Adds X", "Fixes Y", "Removes Z")
+- If a commit is unclear, ask me rather than guess
+
+Format:
+## [X.Y.Z] — [YYYY-MM-DD]
+
+### Breaking Changes
+- ...
+
+### New Features
+- ...
+
+### Improvements
+- ...
+
+### Bug Fixes
+- ...
+```
+
+---
+
+## Vanuit een lijst van wijzigingen
+
+```
+Generate a user-facing changelog entry for these changes:
+
+[paste bullet list of what changed]
+
+Target audience: [developers using our API / end users of the web app / etc.]
+
+Rules:
+- User impact first — "You can now X" not "We added Y"
+- Group related changes under one entry
+- One sentence per entry
+- No technical jargon unless the audience is technical
+```
+
+---
+
+## Keep a Changelog formaat
+
+```
+Generate a changelog entry following the Keep a Changelog format (keepachangelog.com).
+
+Changes:
+[describe or paste git log]
+
+Version: [X.Y.Z]
+Date: [YYYY-MM-DD]
+
+Use these exact section headers where applicable:
+### Added
+### Changed
+### Deprecated
+### Removed
+### Fixed
+### Security
+```
+
+---
+
+> **Werk met ons:** Claudient wordt ondersteund door [Uitbreiden](https://uitbreiden.com/) — we bouwen AI-producten en B2B-oplossingen met ontwikkelaarsgemeenschappen. [uitbreiden.com](https://uitbreiden.com/)

package/prompts/task-specific/nl/debugging.md

@@ -0,0 +1,78 @@
+> 🇳🇱 Dit is de Nederlandse vertaling. [Engelse versie](../debugging.md).
+
+# Prompt: Gestructureerd Debuggen
+
+Gebruik deze prompt bij het overhandigen van een bug aan Claude voor systematische diagnose.
+
+---
+
+## Volledige debuggingprompt
+
+```
+I have a bug. Help me diagnose it systematically.
+
+## The symptom
+[Describe exactly what goes wrong: error message, unexpected output, wrong behavior.
+Include the exact error text if there is one.]
+
+## Reproduction
+[Describe how to reproduce it — steps, curl command, test case, or "cannot reliably reproduce"]
+
+## What I've already tried
+[List anything you've already checked or changed — saves Claude from repeating it]
+
+## Relevant files
+[List the files most likely involved — or ask Claude to identify them]
+
+## Recent changes
+[What changed recently in this area? Paste relevant git log output if helpful]
+
+---
+
+Using this information:
+
+1. Identify the 3 most likely root causes, ranked by probability
+2. For each cause, describe a specific test that would confirm or rule it out
+3. Start with the highest-probability cause
+4. Do not fix anything yet — diagnose first
+
+After each test, report what you found and move to the next hypothesis or proceed to fix.
+```
+
+---
+
+## Snelle variant (voor duidelijke bugs)
+
+Voor bugs waarbij de oorzaak ruwweg bekend is:
+
+```
+Bug: [describe the symptom]
+Likely cause: [your hypothesis]
+Relevant code: [paste the relevant function or file]
+
+Confirm whether my hypothesis is correct, then apply the minimal fix.
+Write a regression test after fixing.
+```
+
+---
+
+## Productie-incident variant
+
+Voor live-incidenten waarbij snelheid belangrijk is:
+
+```
+PRODUCTION INCIDENT — [service name] is [symptom]
+
+Immediate priority: identify the blast radius and any actions to reduce user impact NOW.
+
+Then diagnose:
+- Error logs: [paste relevant log lines]
+- Recent deployments: [list last 3 deploys with timestamps]
+- Affected users: [number/percentage if known]
+
+What is the fastest safe mitigation while we find the root cause?
+```
+
+---
+
+> **Werk met ons:** Claudient wordt ondersteund door [Uitbreiden](https://uitbreiden.com/) — we bouwen AI-producten en B2B-oplossingen met ontwikkelaarsgemeenschappen. [uitbreiden.com](https://uitbreiden.com/)

package/prompts/task-specific/nl/pr-description.md

@@ -0,0 +1,69 @@
+> 🇳🇱 Dit is de Nederlandse vertaling. [Engelse versie](../pr-description.md).
+
+# Prompt: PR-beschrijving Genereren
+
+Gebruik deze prompt om een hoogwaardige pull request-beschrijving te genereren vanuit je wijzigingen.
+
+---
+
+## Prompt
+
+```
+Write a pull request description for the following changes.
+
+Branch: [branch name]
+Base: main
+
+Changed files:
+[paste: git diff --stat main...HEAD]
+
+What this PR does:
+[one sentence — the user should fill this in so Claude has intent, not just diff]
+
+Write the PR description with these sections:
+
+## Summary
+[2–4 bullet points: what changed and why, from the reader's perspective]
+
+## Motivation
+[one short paragraph: what problem this solves or what improvement it makes]
+
+## Changes
+[bullet list of meaningful changes — not a file list, but behavioral/structural changes]
+
+## Test plan
+[bulleted checklist of how a reviewer can verify this works:
+- specific steps to test
+- edge cases to check
+- what a successful result looks like]
+
+## Notes
+[anything a reviewer needs to know: breaking changes, migration steps, follow-up work, known limitations]
+
+Rules:
+- No generic filler ("this PR improves the codebase")
+- No file lists (the diff already shows files)
+- Specific and concrete — a reviewer should be able to test this without asking questions
+- If there are no notes, omit the Notes section
+```
+
+---
+
+## Snelle variant (voor kleine PR's)
+
+Voor kleine, duidelijke wijzigingen:
+
+```
+Write a concise PR description for this change: [describe the change in one sentence]
+
+Include:
+- What: one sentence
+- Why: one sentence  
+- How to test: one or two specific steps
+
+Keep it under 100 words total.
+```
+
+---
+
+> **Werk met ons:** Claudient wordt ondersteund door [Uitbreiden](https://uitbreiden.com/) — we bouwen AI-producten en B2B-oplossingen met ontwikkelaarsgemeenschappen. [uitbreiden.com](https://uitbreiden.com/)

package/prompts/task-specific/pr-description.md

@@ -0,0 +1,67 @@
+# Prompt: Generate PR Description
+
+Use this prompt to generate a high-quality pull request description from your changes.
+
+---
+
+## Prompt
+
+```
+Write a pull request description for the following changes.
+
+Branch: [branch name]
+Base: main
+
+Changed files:
+[paste: git diff --stat main...HEAD]
+
+What this PR does:
+[one sentence — the user should fill this in so Claude has intent, not just diff]
+
+Write the PR description with these sections:
+
+## Summary
+[2–4 bullet points: what changed and why, from the reader's perspective]
+
+## Motivation
+[one short paragraph: what problem this solves or what improvement it makes]
+
+## Changes
+[bullet list of meaningful changes — not a file list, but behavioral/structural changes]
+
+## Test plan
+[bulleted checklist of how a reviewer can verify this works:
+- specific steps to test
+- edge cases to check
+- what a successful result looks like]
+
+## Notes
+[anything a reviewer needs to know: breaking changes, migration steps, follow-up work, known limitations]
+
+Rules:
+- No generic filler ("this PR improves the codebase")
+- No file lists (the diff already shows files)
+- Specific and concrete — a reviewer should be able to test this without asking questions
+- If there are no notes, omit the Notes section
+```
+
+---
+
+## Quick variant (small PRs)
+
+For small, obvious changes:
+
+```
+Write a concise PR description for this change: [describe the change in one sentence]
+
+Include:
+- What: one sentence
+- Why: one sentence  
+- How to test: one or two specific steps
+
+Keep it under 100 words total.
+```
+
+---
+
+> **Work with us:** Claudient is backed by [Uitbreiden](https://uitbreiden.com/) — we build AI products and B2B solutions with developer communities. [uitbreiden.com](https://uitbreiden.com/)