tillerhand 3.47.1 → 3.48.1

package/.claude/hooks/status-read.mjs

@@ -1,13 +1,17 @@
 // Reads the project state from the docs. Used by statusline, session-start and the dashboard.
-// Formats read: **Label:** lines and ## sections in docs/workflow/progress.md, checkboxes under "## Faz" headings
-// in docs/product/roadmap.md, the "Karar günlüğü" in docs/decisions/log.md and the docs/workflow/board.md tables.
+// Formats read: **Label:** lines and ## sections in docs/workflow/progress.md, checkboxes under "## Phase" headings
+// in docs/product/roadmap.md, the "Decision log" in docs/decisions/log.md and the docs/workflow/board.md tables.
+// Labels are read in English: readText turns the Turkish ones of pre-3.48 projects into English.
 // Must stay fast: the status line calls it on every refresh (git and heavy reads are in dashboard.mjs).
 import fs from 'node:fs';
 import path from 'node:path';
 import { t } from './lang.mjs';
+import { normalize, isValue } from './labels.mjs';
 
 // Only a regular file: a folder or a link to a folder named like a test or report file must not throw (EISDIR)
-export const readText = (p) => { try { return fs.statSync(p).isFile() ? fs.readFileSync(p, 'utf8') : ''; } catch { return ''; } };
+// The project name placeholder in AGENTS.md (before 3.48 '[PROJE ADI]')
+export const PLACEHOLDER_NAMES = ['[PROJECT NAME]', '[PROJE ADI]'];
+export const readText = (p) => { try { return fs.statSync(p).isFile() ? normalize(fs.readFileSync(p, 'utf8')) : ''; } catch { return ''; } };
 
 export function sections(text, level = '## ') {
   const result = {};
@@ -57,7 +61,7 @@ export function readStatus(root) {
 
   const roadmap = sections(readText(d('docs/product/roadmap.md')));
   const phases = Object.entries(roadmap)
-    .filter(([b]) => /^Faz \d/.test(b))
+    .filter(([b]) => /^Phase \d/.test(b))
     .map(([name, body]) => ({
       name, ...tally(body),
       tasks: body.split('\n').map((s) => s.match(/^\s*- \[( |x)\]\s*(.+)$/i)).filter(Boolean)
@@ -65,8 +69,8 @@ export function readStatus(root) {
     }));
   const taskCount = phases.reduce((a, f) => ({ done: a.done + f.done, total: a.total + f.total }), { done: 0, total: 0 });
 
-  // 8 columns (with Kapı, kit 2.3+) or the old 7 columns
-  const decisions = tableRows(sections(readText(d('docs/decisions/log.md')))['Karar günlüğü'], 7)
+  // 8 columns (with Door, kit 2.3+) or the old 7 columns
+  const decisions = tableRows(sections(readText(d('docs/decisions/log.md')))['Decision log'], 7)
     .map((c) => (c.length >= 8 ? c : [...c.slice(0, 6), '', c[6]]))
     .map(([no, date, stage, topic, question, chosen, door, decidedBy]) => ({ no, date, stage, topic, question, chosen, door, decidedBy }));
 
@@ -82,29 +86,29 @@ export function readStatus(root) {
   const boardLabels = labels(boardText);
   const boardSections = sections(boardText);
   const board = {
-    state: boardLabels['Durum'] ?? 'kurulmadı',
-    commitReview: boardLabels['Commit denetimi'] ?? 'açık',
-    members: tableRows(boardSections['Üyeler'], 5).map(([member, agent, model, focus, meetings]) => ({ member, agent, model, focus, meetings })),
-    meetings: tableRows(boardSections['Toplantı günlüğü'], 8)
+    state: boardLabels['Status'] ?? 'not set up',
+    commitReview: boardLabels['Commit review'] ?? 'on',
+    members: tableRows(boardSections['Members'], 5).map(([member, agent, model, focus, meetings]) => ({ member, agent, model, focus, meetings })),
+    meetings: tableRows(boardSections['Meeting log'], 8)
       .map(([no, date, kind, scope, attendees, result, critical, decision]) => ({ no, date, kind, scope, attendees, result, critical, decision })),
   };
 
   const title = (f) => readText(d(f)).match(/^# (.+)$/m)?.[1].trim();
   return {
     // The project name is in AGENTS.md; in projects before 3.9.0 in CLAUDE.md (the update adds AGENTS.md with a placeholder)
-    project: [title('AGENTS.md'), title('CLAUDE.md')].find((a) => a && a !== '[PROJE ADI]') ?? title('AGENTS.md') ?? t(root, 'statusRead.defaultProject'),
+    project: [title('AGENTS.md'), title('CLAUDE.md')].find((a) => a && !PLACEHOLDER_NAMES.includes(a)) ?? title('AGENTS.md') ?? t(root, 'statusRead.defaultProject'),
     // type: null = set up by init, no type chosen yet (waiting for /start or /adopt)
     installed: !!kit && kit.type !== null,
     kitPending: kit ? kit.type === null : fs.existsSync(d('kit/kit.mjs')),
     kit,
     fields,
-    state: (progressSections['Şu anki durum'] ?? '').split('\n').filter((s) => s.trim() && !s.startsWith('>')).join(' ').trim(),
-    lastSession: rows(progressSections['Son oturumda yapılanlar']),
-    next: rows(progressSections['Sıradaki adım']),
-    pending: rows(progressSections['Bekleyen kararlar']),
-    issues: rows(progressSections['Açık sorunlar / bloklayıcılar']),
-    leftOff: rows(findSection(progressSections, 'Kaldığı yer')),
-    handoffPending: /^\*\*Durum:\*\*\s*bekliyor/im.test(readText(d('docs/workflow/handoff.md'))),
+    state: (progressSections['Current state'] ?? '').split('\n').filter((s) => s.trim() && !s.startsWith('>')).join(' ').trim(),
+    lastSession: rows(progressSections['Done last session']),
+    next: rows(progressSections['Next step']),
+    pending: rows(progressSections['Pending decisions']),
+    issues: rows(progressSections['Open issues / blockers']),
+    leftOff: rows(findSection(progressSections, 'Where we left off')),
+    handoffPending: isValue(readText(d('docs/workflow/handoff.md')).match(/^\*\*Status:\*\*(.*)$/im)?.[1], 'waiting'),
     phases,
     taskCount,
     decisions,

package/.claude/hooks/statusline.mjs

@@ -6,6 +6,7 @@ import fs from 'node:fs';
 import { readStatus } from './status-read.mjs';
 import { writeLimits, readLimits, level } from './usage.mjs';
 import { t } from './lang.mjs';
+import { isValue } from './labels.mjs';
 
 let root = process.cwd();
 let input = {};
@@ -48,14 +49,15 @@ try {
     parts.push(t(root, 'statusline.notSetUp'));
   } else {
     const a = d.fields;
-    // The values in progress.md stay Turkish (açık / kapalı); only what the line shows is localized
-    const question = (a['Soru modu'] ?? 'açık')
-      .replace(/^(açık|kapalı)(?=$|\s)/i, (m) => t(root, m.toLowerCase() === 'açık' ? 'statusline.modeOpen' : 'statusline.modeOff'))
-      .replace(/\s*·\s*kapalı konular:\s*yok/i, '')
-      .replace(/\s*·\s*kapalı konular:\s*(.*)$/i, (_, topics) => ` ${t(root, 'statusline.closed', { topics })}`);
-    parts.push(`▶ ${a['Aktif faz'] ?? '-'}`);
-    if (/başlangıç/i.test(a['Aktif faz'] ?? '')) parts.push(t(root, 'statusline.step', { step: a['Başlangıç adımı'] ?? '-' }));
-    else parts.push(a['Aktif görev'] ?? '-', t(root, 'statusline.task', { done: d.taskCount.done, total: d.taskCount.total }));
+    // progress.md says on / off (açık / kapalı before 3.48); only what the line shows is localized
+    const mode = a['Question mode'] ?? 'on';
+    const question = mode
+      .replace(/^\S+/, (m) => (isValue(m, 'on') ? t(root, 'statusline.modeOpen') : isValue(m, 'off') ? t(root, 'statusline.modeOff') : m))
+      .replace(/\s*·\s*(?:kapalı konular|closed topics):\s*(?:yok|none)\s*$/i, '')
+      .replace(/\s*·\s*(?:kapalı konular|closed topics):\s*(.*)$/i, (_, topics) => ` ${t(root, 'statusline.closed', { topics })}`);
+    parts.push(`▶ ${a['Active phase'] ?? '-'}`);
+    if (isValue(a['Active phase'], 'setup')) parts.push(t(root, 'statusline.step', { step: a['Setup step'] ?? '-' }));
+    else parts.push(a['Active task'] ?? '-', t(root, 'statusline.task', { done: d.taskCount.done, total: d.taskCount.total }));
     parts.push(t(root, 'statusline.question', { mode: question }));
     if (d.pending.length) parts.push(t(root, 'statusline.pending', { count: d.pending.length }));
   }

package/.claude/hooks/tools.mjs

@@ -5,7 +5,7 @@
 //   node .claude/hooks/tools.mjs --disable <package>   deletes the personal override, back to the project default
 //   node .claude/hooks/tools.mjs --required <package>  0 if enabled, 2 if disabled (commands call it in their first step)
 //   node .claude/hooks/tools.mjs --measure             skill and agent description load of installed plugins
-//   node .claude/hooks/tools.mjs --commands light|full non-core kit commands listed by name only (Hafif/Standart) or in full (Tam)
+//   node .claude/hooks/tools.mjs --commands light|full non-core kit commands listed by name only (Light/Standard profile) or in full (Full)
 // Why: the skill list is capped at 1% of the context; past that, descriptions drop and skills get missed. Plugin skills cannot
 // be turned off one by one, a plugin is on or off as a whole. Enabling mid-session breaks the prompt cache: best at a phase boundary, with /clear.
 import fs from 'node:fs';
@@ -14,20 +14,20 @@ import path from 'node:path';
 import { missingPlugins } from './plugins-sync.mjs';
 import { findRoot, isMain } from './shared.mjs';
 
-// Keys are the package names users type (/tools ac tasarim): they stay Turkish
+// Keys are the package names users type (/tools on design)
 export const PACKAGES = {
-  tasarim: {
+  design: {
     description: 'Style directions, palette and typefaces, GSAP',
     command: '/design',
     plugins: ['taste-skill@taste-skill', 'ui-ux-pro-max@ui-ux-pro-max-skill', 'gsap-skills@gsap-skills'],
   },
-  guvenlik: {
+  security: {
     description: 'Deep security scan',
     command: '/findings-security, /release',
     plugins: ['differential-review', 'insecure-defaults', 'sharp-edges', 'static-analysis', 'supply-chain-risk-auditor', 'agentic-actions-auditor', 'fp-check']
       .map((e) => `${e}@trailofbits`).concat('claude-security@claude-plugins-official'),
   },
-  yayin: {
+  release: {
     description: 'Code map for humans, session report',
     command: '/release, /handoff, /adopt',
     plugins: ['understand-anything@understand-anything', 'session-report@claude-plugins-official'],
@@ -50,9 +50,13 @@ function readJson(p) {
   }
 }
 
+// Package names before 3.48; they still work as input
+const OLD_NAMES = { tasarim: 'design', guvenlik: 'security', yayin: 'release' };
+export const packageName = (name) => (Object.hasOwn(OLD_NAMES, name ?? '') ? OLD_NAMES[name] : name);
+
 function pkg(name) {
-  if (!Object.hasOwn(PACKAGES, name ?? '')) throw new Error(`Unknown package: ${name}. Options: ${Object.keys(PACKAGES).join(', ')}`);
-  return PACKAGES[name];
+  if (!Object.hasOwn(PACKAGES, packageName(name ?? ''))) throw new Error(`Unknown package: ${name}. Options: ${Object.keys(PACKAGES).join(', ')}`);
+  return PACKAGES[packageName(name)];
 }
 
 export function packageStatus(root) {
@@ -144,7 +148,8 @@ const tokenOf = (measurement, ids) => {
 const NOTE = 'After enabling, run /reload-plugins. Enabling mid-session breaks the prompt cache; best at a phase boundary, together with /clear.';
 if (isMain(import.meta.url)) {
   const root = findRoot();
-  const [flag, name] = process.argv.slice(2);
+  const [flag, typed] = process.argv.slice(2);
+  const name = packageName(typed);
   try {
     if (flag === '--enable' || flag === '--disable') {
       const ids = setPackage(root, name, flag === '--enable');

package/.claude/output-styles/{anlatici.md → narrator.md}

@@ -1,5 +1,5 @@
 ---
-name: anlatici
+name: narrator
 description: Narrator mode. Explains every change and error in plain language in the conversation language, as if to someone who knows no software. Coding behavior does not change.
 keep-coding-instructions: true
 ---
@@ -27,7 +27,7 @@ After the `/build` or `/fix-bug` report (before the status block), ask at most 2
 - Ask with AskUserQuestion. Give 3 options: one correct, two plausible but wrong. Shuffle the position of the correct option and do not write "(Recommended)". Make the last option "Not now".
 - Make the question of the type "Why was this change needed?" or "What would happen without it?". Do not ask about file names or code details.
 - Respond to a correct answer in one sentence. For a wrong answer, explain the correct one in 1-2 sentences and do not make a big deal of the mistake.
-- Add every answered question as one row to the "Kayıtlar" table in `docs/workflow/learning.md`: `| YYYY-AA-GG | <task id> | <concept, 1-3 words> | doğru |` (or `yanlış`). Do not write "Not now" and unanswered questions. If the file does not exist, create it with the same heading and columns.
+- Add every answered question as one row to the "Records" table in `docs/workflow/learning.md`: `| YYYY-MM-DD | <task id> | <concept, 1-3 words> | right |` (or `wrong`). Do not write "Not now" and unanswered questions. If the file does not exist, create it with the same heading and columns.
 
 ## When an error occurs
 

package/.claude/skills/logo-design/SKILL.md

@@ -5,7 +5,7 @@ description: Designs a brand logo: asks brand questions first, presents 4-6 SVG
 
 # Logo design
 
-A logo is not an image-generation request. It is **code**: editable SVG built from simple geometric shapes that reads at every size. Ask decisions per `docs/workflow/decision-protocol.md` (design decision = visual preview). If the `tasarim` topic is closed in question mode, go with the recommended option and still produce the previews.
+A logo is not an image-generation request. It is **code**: editable SVG built from simple geometric shapes that reads at every size. Ask decisions per `docs/workflow/decision-protocol.md` (design decision = visual preview). If the `design` topic is closed in question mode, go with the recommended option and still produce the previews.
 
 ## 1. Brand summary (questions)
 
@@ -62,5 +62,5 @@ Output folder: `public/brand/` for web, `assets/brand/` for mobile (allowed in t
 - `docs/design/brand.md`:
   - Brand summary and the reason for the chosen concept
   - Usage rules: clear space (half the symbol height), minimum size, color codes, what not to do (stretch, shadow, rotate, change color)
-- Write the choices to `docs/decisions/log.md` (topic: `tasarim`) and to `docs/design/design-guide.md` → decision log.
+- Write the choices to `docs/decisions/log.md` (topic: `design`) and to `docs/design/design-guide.md` → decision log.
 - If there is a slogan or brand text, run it through `humanizer:humanizer`.

package/.claude/skills/source-research/SKILL.md

@@ -42,7 +42,7 @@ If a critical decision or finding rests on level D, say so openly.
 ## 4. Output
 
 - In the answer, put the source next to every claim: `[title](url) · date · level`.
-- Save lasting research done for a decision or report as `docs/research/YYYY-AA-GG-topic.md`: question, short answer, evidence (with sources), contradictions, open questions. Other docs link to this file.
+- Save lasting research done for a decision or report as `docs/research/YYYY-MM-DD-topic.md`: question, short answer, evidence (with sources), contradictions, open questions. Other docs link to this file.
 
 ## 5. Firecrawl (optional)
 

package/.claude/skills/ui-motion/SKILL.md

@@ -31,11 +31,11 @@ Motion's job is to give information: what changed, where it came from, is the sy
 
 | Stack | Library |
 |---|---|
-| Web (React/Next.js) | CSS transitions for simple cases; **Motion** (`motion/react`) for springs, layout and enter/exit. GSAP only if a landing page needs scroll-driven storytelling (`gsap-skills:`, `tasarim` package; free, commercial use included, forbidden in a no-code animation tool that competes with Webflow). |
+| Web (React/Next.js) | CSS transitions for simple cases; **Motion** (`motion/react`) for springs, layout and enter/exit. GSAP only if a landing page needs scroll-driven storytelling (`gsap-skills:`, `design` package; free, commercial use included, forbidden in a no-code animation tool that competes with Webflow). |
 | Web 3D | **three.js**; **React Three Fiber** + drei in React. The skills are copied in `/start` step 3c (`threejs-*`). |
 | Mobile (Expo) | **react-native-reanimated** (runs on the UI thread); use Reanimated layout animations instead of `LayoutAnimation`. Haptic feedback on important actions. |
 
-Adding a new animation library is a `teknik` decision; ask.
+Adding a new animation library is a `tech` decision; ask.
 
 ## 3D
 

package/AGENTS.md

@@ -1,4 +1,4 @@
-# [PROJE ADI]
+# [PROJECT NAME]
 
 > [One sentence: who is this project for, and what problem does it solve?]
 
@@ -10,13 +10,13 @@ This file holds the shared rules of the project. Claude Code, Codex and Antigrav
 
 ## Core rules (always apply)
 
-1. **The user decides.** Ask with AskUserQuestion for product, technical, design, content, data, security and cost decisions. Offer 2-4 options; put your recommendation first and label it "(Recommended)". For each option, state when it is better and what it costs. Ask design decisions with a visual preview. In question mode, pick the recommended option on closed topics and record it as `otomatik` in the decision log ("Auto decisions" in the status block). **Read `docs/workflow/decision-protocol.md` before the first decision question.** Earlier decisions are in `docs/decisions/log.md`; do not ask them again. Classify every decision as a one-way or two-way door; for one-way doors (database, auth, payment, data model), get the board's opinion first.
-2. **The expert board reviews** (`docs/workflow/board.md`, rules in `.claude/board/rules.md`). The relevant members meet before plan approval, when a task ends, at every commit (light) and at the end of a phase. The board only advises; if there is a RET (critical finding), the work is not done and the user is asked.
+1. **The user decides.** Ask with AskUserQuestion for product, technical, design, content, data, security and cost decisions. Offer 2-4 options; put your recommendation first and label it "(Recommended)". For each option, state when it is better and what it costs. Ask design decisions with a visual preview. In question mode, pick the recommended option on closed topics and record it as `automatic` in the decision log ("Auto decisions" in the status block). **Read `docs/workflow/decision-protocol.md` before the first decision question.** Earlier decisions are in `docs/decisions/log.md`; do not ask them again. Classify every decision as a one-way or two-way door; for one-way doors (database, auth, payment, data model), get the board's opinion first.
+2. **The expert board reviews** (`docs/workflow/board.md`, rules in `.claude/board/rules.md`). The relevant members meet before plan approval, when a task ends, at every commit (light) and at the end of a phase. The board only advises; if there is a REJECT (critical finding), the work is not done and the user is asked.
 3. **Right source.** Do not use information that can change from memory: versions, prices, quotas, regulation, APIs. Use the `source-research` skill (primary source first, every claim with source and date). When using a library, first fetch the current docs with the **Context7** MCP.
 4. **Spend few tokens.** If the code map (codebase-memory-mcp) is connected, query it first when exploring code (`get_architecture`, `search_graph`, `trace_path`, `get_code_snippet`). Do not read files in bulk. Read docs only when needed (table below).
 5. **Follow the structure (mandatory).** Write each new file to its place in the `.claude/structure.json` map (by feature: `features/<feature>/`); it is explained in `docs/architecture/structure.md`. Writing outside the map is asked about; clutter files (`*.bak`, `*-old.*`, copies) are blocked. Temporary and trial work goes to `sandbox/`, outdated docs to `docs/archive/`. Changing the map is a technical decision.
 6. **Plan first, then code.** Work that touches more than 2 files goes through `/plan-task`. One task at a time. Do not widen the scope. Four principles: (1) state your assumption, ask if unsure; (2) simplest solution, no flexibility nobody asked for; (3) touch only the lines the task needs; (4) write a verifiable success criterion when you start.
-7. **Root cause, evidence, tests.** Acceptance tests (criterion id in the test name, `Ö-01.1`) and adversarial tests are written before the code and are red first. A separate agent (`test-writer`, with the test role's model) writes the tests, not the one who writes the code; the code writer does not touch test files (test protection blocks it). Risky features ship behind a feature flag (`docs/operations/feature-flags.md`). When fixing a bug, reproduce it first. Show that it works before saying "done". If you cannot fix the same error in 2 attempts, stop and ask for direction.
+7. **Root cause, evidence, tests.** Acceptance tests (criterion id in the test name, `AC-01.1`) and adversarial tests are written before the code and are red first. A separate agent (`test-writer`, with the test role's model) writes the tests, not the one who writes the code; the code writer does not touch test files (test protection blocks it). Risky features ship behind a feature flag (`docs/operations/feature-flags.md`). When fixing a bug, reproduce it first. Show that it works before saying "done". If you cannot fix the same error in 2 attempts, stop and ask for direction.
 8. **A status block at the end of every answer** (short). Format:
 
 ```
@@ -26,7 +26,7 @@ Done: … · Board: … · Auto decisions: …
 Next: … · pending decision: …
 ```
 
-9. **Know the user.** Follow the "Personal preferences" that arrive at session start (project rules come first). If the user corrects a behavior or says how they want to work (conversation, question frequency, report format, code style, things to avoid), note it briefly; do not break the flow. At the end of a task (`/build`) and at the end of a session (`/wrap-up`), ask about the notes with AskUserQuestion as a multi-select ("Save as a preference?"). Write the selected ones with `node .claude/hooks/prefs.mjs --add <konusma|sorular|raporlar|kod|kacin> "<preference>"`. Do not write without approval. Do not write secrets, personal data or the project name. A project-specific rule goes to "Öğrenilen kurallar" (learned rules), not to this file.
+9. **Know the user.** Follow the "Personal preferences" that arrive at session start (project rules come first). If the user corrects a behavior or says how they want to work (conversation, question frequency, report format, code style, things to avoid), note it briefly; do not break the flow. At the end of a task (`/build`) and at the end of a session (`/wrap-up`), ask about the notes with AskUserQuestion as a multi-select ("Save as a preference?"). Write the selected ones with `node .claude/hooks/prefs.mjs --add <conversation|questions|reports|code|avoid> "<preference>"`. Do not write without approval. Do not write secrets, personal data or the project name. A project-specific rule goes to "Learned rules", not to this file.
 
 <!-- kit:other-tools -->
 ## In Codex and Antigravity
@@ -58,15 +58,15 @@ The kit was written for Claude Code; these equivalents apply in these two tools:
 | `docs/product/feedback.md`, `docs/quality/metrics.md` | User feedback, retro, maintenance |
 | `docs/findings/<type>/latest.md` | When working in the relevant area: known findings (`/findings-<type>` reports) |
 
-## Komutlar
+## Commands
 
 ```bash
 # /start fills these in for the chosen stack
-geliştirme:  [ ]
-önizleme:    [ ]
+dev:         [ ]
+preview:     [ ]
 test:        [ ]
 lint:        [ ]
-tip kontrol: [ ]
+type check: [ ]
 build:       [ ]
 ```
 
@@ -76,7 +76,7 @@ build:       [ ]
 - [ ] Lint, types and tests are clean; a test was added if critical flow was touched
 - [ ] Error, empty and loading states are handled; evidence that it works was shown (the verification command ran in this turn and its output was shown; "it should work" is not evidence)
 - [ ] If there is an interface: matches `DESIGN.md`, Impeccable critique done, texts passed through humanizer
-- [ ] No RET in the end-of-task board meeting
+- [ ] No REJECT in the end-of-task board meeting
 - [ ] No secrets in code; any new environment variable is in `.env.example`; `docs/product/roadmap.md` is marked
 
 ## Never
@@ -91,6 +91,6 @@ build:       [ ]
 
 Small, frequent commits. Message format: `type: description` (`feat`, `fix`, `refactor`, `docs`, `test`, `chore`, `wip`). `main` must always work.
 
-## Öğrenilen kurallar
+## Learned rules
 
-> `/fix-bug` suggests when the same error class repeats, `/retro` suggests at the end of a period; added if you approve. Format: `- Rule. (kaynak: … · YYYY-AA-GG)`; the date is when it was added or last reviewed. At most ~10 lines. `/maintain monthly` reviews those older than 90 days.
+> `/fix-bug` suggests when the same error class repeats, `/retro` suggests at the end of a period; added if you approve. Format: `- Rule. (source: … · YYYY-MM-DD)`; the date is when it was added or last reviewed. At most ~10 lines. `/maintain monthly` reviews those older than 90 days.

package/CLAUDE.md

@@ -7,5 +7,5 @@
 The shared rules are in `AGENTS.md` (imported above). These are additions to them:
 
 - **Use the right skill.** Code: `ponytail:ponytail`. Critical flow: `mattpocock-skills:tdd`. Interface: the chosen style skill + `impeccable:impeccable`; motion: `ui-motion`. Logo: `logo-design`. Promo video: `motion-video`. Text: `humanizer:humanizer`. Report language: `caveman:caveman`. Full table (read on first need): `docs/workflow/skills.md`. Non-core plugins come switched off as packages; when a command needs one, ask to switch it on (`/tools`).
-- **Watch the limit and the context** (`docs/workflow/usage-limits.md`). Read the limit before starting work: the `get_usage` tool on desktop, `node .claude/hooks/usage.mjs` in the terminal. At yellow/red level, state the estimated cost in one line. The limit is only a reason to warn, not to stop work: remind at 90%, warn at 95% and update "Kaldığı yer" (where we left off), say "may be left unfinished" at 99%; keep going unless the user says "stop". When the context passes 50%, suggest `/wrap-up` + `/clear` at a suitable point.
+- **Watch the limit and the context** (`docs/workflow/usage-limits.md`). Read the limit before starting work: the `get_usage` tool on desktop, `node .claude/hooks/usage.mjs` in the terminal. At yellow/red level, state the estimated cost in one line. The limit is only a reason to warn, not to stop work: remind at 90%, warn at 95% and update "Where we left off" (where we left off), say "may be left unfinished" at 99%; keep going unless the user says "stop". When the context passes 50%, suggest `/wrap-up` + `/clear` at a suitable point.
 - **The status block** is written in caveman style.

package/README.md

@@ -6,7 +6,7 @@
 </p>
 
 <p align="center">
-  <a href="kit/CHANGELOG.md"><img alt="Version" src="https://img.shields.io/badge/version-3.47.1-2a78d6?style=flat-square"></a>
+  <a href="kit/CHANGELOG.md"><img alt="Version" src="https://img.shields.io/badge/version-3.48.1-2a78d6?style=flat-square"></a>
   <a href="LICENSE"><img alt="License: MIT" src="https://img.shields.io/badge/license-MIT-2a78d6?style=flat-square"></a>
   <img alt="Claude Code" src="https://img.shields.io/badge/Claude%20Code-ready-d97757?style=flat-square">
   <img alt="Also Codex and Antigravity" src="https://img.shields.io/badge/also-Codex%20%C2%B7%20Antigravity-5b6577?style=flat-square">
@@ -90,7 +90,7 @@ The first question is the language: Turkish, English or another one. Claude then
 **Good to know**
 - **Limits:** Pro has 5-hour and weekly limits. Claude warns at 90%, 95% and 99%; if a limit runs out, continue with `/build` once it resets.
 - **Approval:** Database, design and cost decisions are never made without asking. Deleting data, payments and going live always need your approval.
-- **Handoff:** Leaving the project to someone else? Use `/handoff`; they continue from the same point with `/handoff devral`.
+- **Handoff:** Leaving the project to someone else? Use `/handoff`; they continue from the same point with `/handoff take`.
 
 ## Quick start
 

package/README.tr.md

@@ -6,7 +6,7 @@
 </p>
 
 <p align="center">
-  <a href="kit/CHANGELOG.md"><img alt="Sürüm" src="https://img.shields.io/badge/s%C3%BCr%C3%BCm-3.47.1-2a78d6?style=flat-square"></a>
+  <a href="kit/CHANGELOG.md"><img alt="Sürüm" src="https://img.shields.io/badge/s%C3%BCr%C3%BCm-3.48.1-2a78d6?style=flat-square"></a>
   <a href="LICENSE"><img alt="Lisans: MIT" src="https://img.shields.io/badge/lisans-MIT-2a78d6?style=flat-square"></a>
   <img alt="Claude Code" src="https://img.shields.io/badge/Claude%20Code-haz%C4%B1r-d97757?style=flat-square">
   <img alt="Codex ve Antigravity" src="https://img.shields.io/badge/ayr%C4%B1ca-Codex%20%C2%B7%20Antigravity-5b6577?style=flat-square">
@@ -90,7 +90,7 @@ Kod yazmayı bilmen gerekmez. Git, terminal ve kurulum işlerini Claude yapar; s
 **Bilmen gerekenler**
 - **Limit:** Pro'da 5 saatlik ve haftalık limit var. Claude %90, %95 ve %99'da uyarır; limit dolarsa yenilenince `/build` ile kaldığın yerden devam edersin.
 - **Onay:** Veritabanı, tasarım, maliyet kararları sorulmadan verilmez. Veri silme, ödeme ve canlıya alma her zaman onay ister.
-- **Devir:** Projeyi başkasına bırakacaksan `/handoff`; devralan `/handoff devral` ile aynı yerden devam eder.
+- **Devir:** Projeyi başkasına bırakacaksan `/handoff`; devralan `/handoff take` ile aynı yerden devam eder.
 
 ## Hızlı başlangıç
 
@@ -177,7 +177,7 @@ flowchart LR
 
 ## Uzman kurulu
 
-Ürün tipine göre projene özel kurul ajanları oluşturulur. Kurul danışmandır; kritik bulgu (RET) varsa iş bitmez, sana sorulur.
+Ürün tipine göre projene özel kurul ajanları oluşturulur. Kurul danışmandır; kritik bulgu (REJECT) varsa iş bitmez, sana sorulur.
 
 | Tip | Önerilen kurul |
 |---|---|

package/docs/decisions/adr-template.md

@@ -1,6 +1,6 @@
 # ADR-NNNN: [Short title]
 
-- **Date:** YYYY-AA-GG
+- **Date:** YYYY-MM-DD
 - **Status:** Proposed / Accepted / Superseded by: ADR-NNNN
 - **Door:** one-way / two-way
 - **Decision log:** #N (`docs/decisions/log.md`)

package/docs/decisions/log.md

@@ -1,13 +1,13 @@
 # Decisions
 
 > There are two sections:
-> 1. **Decision log ("Karar günlüğü"):** one line for every decision asked. Door: `tek` (one-way, costly to reverse) / `çift` (two-way, easy to reverse). Decided by: `kullanıcı` (user) or `otomatik` (automatic, when question mode is off).
+> 1. **Decision log:** one line for every decision asked. Door: `one-way` (costly to reverse) / `two-way` (easy to reverse). Decided by: `user` or `automatic` (when question mode is off). Logs from before 3.48 say `tek` / `çift` and `kullanıcı` / `otomatik`; both are read.
 > 2. **ADRs** (Architecture Decision Record): decisions that affect the architecture or the long term, and all one-way decisions, go in a separate file: `docs/decisions/adr-NNNN-kisa-ad.md` (template: `adr-template.md`).
 >
 > Look here before asking a decision: if it was made before, do not ask again, follow it.
 > Decisions are never deleted; if one changes, a new line is added and "→ changed by #N" is written next to the old one.
 
-## Karar günlüğü
+## Decision log
 
 `/dashboard` reads this table; do not change the columns.
 

package/docs/findings/README.md

@@ -14,7 +14,7 @@ Reports that scan the project through different expert eyes. Each report ranks a
 
 Each type's folder holds dated reports and a copy of the latest report (`latest.md`).
 
-## Raporlar
+## Reports
 
 The `/dashboard` dashboard reads this table; do not change the columns. Write health and the previous score in the `NN` format.
 

package/docs/operations/accounts.md

@@ -5,23 +5,23 @@
 > a key nobody remembers owning. The `/dashboard` dashboard shows **dates expiring within 30 days** in the "Needs attention" area.
 >
 > **Never write a password, key or token here.** Write only which account, who holds it, when it ends.
-> Dates must use the `YYYY-AA-GG` format (the dashboard reads them).
+> Dates must use the `YYYY-MM-DD` format (the dashboard reads them).
 
-## Hesaplar
+## Accounts
 
 | Service | Purpose | Account owner | 2FA | Plan / monthly cost | Expiry / renewal | Key rotation | Note |
 |---|---|---|---|---|---|---|---|
 | [GitHub] | Code repository | [email] | [yes/no] | [Free] | - | - | |
-| [Domain registrar] | Domain name | | | | [YYYY-AA-GG] | - | Is auto-renewal on? |
+| [Domain registrar] | Domain name | | | | [YYYY-MM-DD] | - | Is auto-renewal on? |
 | [Hosting] | | | | | | | |
-| [Database] | | | | | | [YYYY-AA-GG] | |
+| [Database] | | | | | | [YYYY-MM-DD] | |
 | [Email service] | | | | | | | |
 | [Payment provider] | | | | | | | |
 | [Error tracking] | | | | | | | |
-| [AI provider] | | | | | | [YYYY-AA-GG] | Spend limit: |
-| [Apple / Google developer] | Store | | | | [YYYY-AA-GG] | | Annual membership |
+| [AI provider] | | | | | | [YYYY-MM-DD] | Spend limit: |
+| [Apple / Google developer] | Store | | | | [YYYY-MM-DD] | | Annual membership |
 
-## Ortamlar (dev / prod)
+## Environments (dev / prod)
 
 > A project ref and a URL are not secrets; keys are still not written here. `/release` reads this table: it blocks the release
 > if the prod ref appears in `.mcp.json`, in `.claude/` or in code.

package/docs/operations/deploy-setup.md

@@ -10,8 +10,8 @@
 - **A secret value is never written in chat or in a file.** Not in this file, not in `accounts.md`, not in code. The AI says only the variable name (as in `.env.example`); the user enters the value in the provider's panel themselves.
 - The `mattpocock-skills:wizard` script does not ask for a prod secret and does not write a prod value to `.env`. The prod value is entered in the panel. The script passes only CI secrets (e.g. `LIVE_TEST_*`) to `gh secret set` with hidden input in the user's terminal. The script stays under `sandbox/` and is deleted when the work is done.
 - A prod deploy, a rollback drill and a restore from backup do not start without approval.
-- The AI and the local environment do not connect to the prod database (`accounts.md` → Ortamlar). The only exception: the backup the user takes in their own terminal (Supabase → Backup).
-- The result of each step goes into `accounts.md` (service, owner, 2FA, plan, expiry; the prod ref and URL under Ortamlar) and into the `/release` report.
+- The AI and the local environment do not connect to the prod database (`accounts.md` → Environments). The only exception: the backup the user takes in their own terminal (Supabase → Backup).
+- The result of each step goes into `accounts.md` (service, owner, 2FA, plan, expiry; the prod ref and URL under Environments) and into the `/release` report.
 - The kit updates this file; do not edit it in the project. Write a step that conflicts with the source in the report.
 
 ## Order
@@ -47,7 +47,7 @@ Checked: 2026-10-25. Sources: [Environment variables](https://vercel.com/docs/en
 
 Checked: 2026-10-25. Sources: [Backups](https://supabase.com/docs/guides/platform/backups) · [Backup and restore using the CLI](https://supabase.com/docs/guides/platform/migrating-within-supabase/backup-restore) · [API keys](https://supabase.com/docs/guides/api/api-keys) (no dates on the pages)
 
-**Project.** Open a separate project for prod. Write its ref in `accounts.md` → Ortamlar → prod row. Auth and email settings: `docs/architecture/stack.md` → "Go live (extra)".
+**Project.** Open a separate project for prod. Write its ref in `accounts.md` → Environments → prod row. Auth and email settings: `docs/architecture/stack.md` → "Go live (extra)".
 
 **Keys.** The new keys are `sb_publishable_…` (can go to the client) and `sb_secret_…` (server only; as Secret in the hosting panel). A long key starting with `eyJ` is the old type. Supabase is deprecating the old `anon` and `service_role` keys by the end of 2026: use the new keys in a new project. If `.env.example` still has the old names (`NEXT_PUBLIC_SUPABASE_ANON_KEY`, `SUPABASE_SERVICE_ROLE_KEY`), enter the new key under the same name.
 

package/docs/operations/feature-flags.md

@@ -12,9 +12,9 @@
 - A feature that deletes, moves or exports data
 - A large interface change (to roll it out gradually)
 
-## Bayraklar
+## Flags
 
-The `/dashboard` dashboard reads this table. Date format `YYYY-AA-GG`, status `on` / `off` / `gradual %N`.
+The `/dashboard` dashboard reads this table. Date format `YYYY-MM-DD`, status `on` / `off` / `gradual %N`.
 
 | Flag | Purpose | Status | Owner | Added | Removal date | Kill switch tested |
 |---|---|---|---|---|---|---|

package/docs/operations/maintenance.md

@@ -45,7 +45,7 @@
 4. **Notify:** For a personal data breach, notify the KVKK Board within **72 hours** and inform the affected users (`docs/legal/privacy-kvkk.md`).
 5. **Learn:** Write it in the log below. Add the check that prevents a repeat to the matching list.
 
-## Bakım kaydı
+## Maintenance log
 
 | Date | Type | Findings | Done / task opened |
 |---|---|---|---|

package/docs/operations/release-checklist.md

@@ -41,7 +41,7 @@
 - [ ] `docs/product/unit-economics.md`: contribution margin is positive, break-even point is known
 - [ ] Spend alarms: every paid service has a cap or alert set up and tried once (`docs/operations/spend-alarms.md`); an AI/paid API call has a per-user quota and a global daily budget
 - [ ] All acceptance tests are green (MVP criteria)
-- [ ] The last `/qa` report (`docs/quality/qa/`) has no "kaldı" (remaining) item; in a web project the interface criteria were run in the browser
+- [ ] The last `/qa` report (`docs/quality/qa/`) has no `failed` item; in a web project the interface criteria were run in the browser
 
 ### Infrastructure
 > Steps by provider are in `docs/operations/deploy-setup.md` (`/release first` → Deploy setup).
@@ -72,4 +72,4 @@
 
 - [ ] Check error tracking twice a day
 - [ ] Check the cost panel once a day
-- [ ] First user feedback was added to `docs/product/roadmap.md` → "Faz 4" (Phase 4)
+- [ ] First user feedback was added to `docs/product/roadmap.md` → "Phase 4"

package/docs/operations/spend-alarms.md

@@ -4,9 +4,9 @@
 > This is separate from the Claude Code limit: here the subject is your own product's bill.
 > The `/dashboard` dashboard (Operations tab) reads the table below. It marks a paid row with an empty limit as "not set".
 
-## Alarmlar
+## Alarms
 
-One row per paid service. **Type:** `cap` (cap: the service stops or requests are rejected) or `alert` (alert: only warns). **Amount:** monthly, with currency (e.g. `50 USD`). **Last check:** `YYYY-AA-GG`.
+One row per paid service. **Type:** `cap` (cap: the service stops or requests are rejected) or `alert` (alert: only warns). **Amount:** monthly, with currency (e.g. `50 USD`). **Last check:** `YYYY-MM-DD`.
 
 | Service | Type | Amount | Alert thresholds | Set up at | Last check |
 |---|---|---|---|---|---|

package/docs/product/feedback.md

@@ -2,17 +2,17 @@
 
 > The voice of the users. The `/user-feedback` command puts new feedback here, prioritizes it with the Product board member,
 > and asks you which items go into the roadmap. `/dashboard` shows open feedback and the leading themes.
-> The headings "Gelen kutusu" (inbox) and "Temalar" (themes) stay Turkish: the dashboard reads them.
+> The dashboard reads the "Inbox" and "Themes" headings and the type and status words below; keep their wording.
 > Do not write personal data: label the user anonymously (K-001).
 
-## Gelen kutusu
+## Inbox
 
-Types: `hata` / `istek` / `şikayet` / `övgü` / `soru`. Statuses: `yeni` / `planlandı` / `yapıldı` / `reddedildi` / `birleşti`.
+Types: `bug` / `request` / `complaint` / `praise` / `question`. Statuses: `new` / `planned` / `done` / `rejected` / `merged`.
 
 | # | Date | Source | User | Summary | Type | Theme | Priority | Status | Task |
 |---|---|---|---|---|---|---|---|---|---|
 
-## Temalar
+## Themes
 
 Similar feedback is collected under one theme. 3+ feedback items in the same theme is a strong signal.
 

package/docs/product/launch.md

@@ -33,7 +33,7 @@
 
 - [ ] Talk one-on-one with the first 10 users: Why did they sign up, where did they get stuck, what did they expect?
 - [ ] Weekly metrics review (table below).
-- [ ] Add the feedback as tasks to `docs/product/roadmap.md` → Faz 4; start with the most repeated one.
+- [ ] Add the feedback as tasks to `docs/product/roadmap.md` → Phase 4; start with the most repeated one.
 - [ ] Compare with the `docs/product/prd.md` §4 success criteria: Is it close to the target, or is a change of direction needed?
 
 ## 4. Metrics tracking

package/docs/product/prd.md

@@ -1,7 +1,7 @@
 # Product Requirements (PRD)
 
 > Stage: **0 - Idea**. Fill it in before writing code. The `/start` command fills this file in together with you.
-> Last updated: [YYYY-AA-GG]
+> Last updated: [YYYY-MM-DD]
 
 ## 1. Problem
 
@@ -14,7 +14,7 @@
 | [Primary] | | | |
 | [Secondary] | | | |
 
-## 3. Değer önerisi (value proposition)
+## 3. Value proposition (value proposition)
 
 [One sentence: "With [product], [user] gets [result], because [difference]."]
 
@@ -27,20 +27,20 @@
 ## 5. MVP scope
 
 Each feature is a user story + acceptance criteria. A feature without acceptance criteria is not ready.
-Each criterion has an id (`Ö-01.1`). Acceptance tests carry this id in the test name; the `/dashboard` reads MVP progress from **test results**, not from checkboxes (`docs/quality/test-plan.md` §1a).
-The label "Öncelik" (priority) stays Turkish: the dashboard reads it.
+Each criterion has an id (`AC-01.1`). Acceptance tests carry this id in the test name; the `/dashboard` reads MVP progress from **test results**, not from checkboxes (`docs/quality/test-plan.md` §1a).
+The dashboard reads the "Priority" label; keep its wording.
 
-### Ö-01: [Feature name]
+### AC-01: [Feature name]
 **Story:** As a [user], I want to [action], so that [benefit].
 **Acceptance criteria:**
-- [ ] Ö-01.1: [Observable behavior: "When an invalid email is entered, the form is not sent and an error message is shown"]
-- [ ] Ö-01.2: [...]
-**Öncelik:** Must have / Nice to have
+- [ ] AC-01.1: [Observable behavior: "When an invalid email is entered, the form is not sent and an error message is shown"]
+- [ ] AC-01.2: [...]
+**Priority:** Must have / Nice to have
 
-### Ö-02: [Feature name]
+### AC-02: [Feature name]
 ...
 
-## 6. Kapsam dışı (out of scope: NOT built in this release)
+## 6. Out of scope (out of scope: NOT built in this release)
 
 This list stops the AI from widening the scope. Write every "later" idea that comes to mind here.