fjrevoredo

Add a new language/locale to Mini Diarium. Use this skill whenever the user asks to add a new locale (e.g., "add Italian", "add French locale", "add Portuguese support", "new language"). Handles the full workflow: JSON file creation, i18n wiring, language dropdown, sync script, and validation. For updating existing translations only — not for new locales.

Use this skill whenever the user asks you to apply dependency update PRs from GitHub — Dependabot bumps, version updates in package.json, or merging dependency PRs. Use this even if the user just says "apply this PR" or "merge these PRs" and the PRs change package.json. This skill handles the dual-lockfile setup (bun.lock + package-lock.json), detects partially-applied PRs, catches stale lockfiles, resolves overlapping version bumps across multiple PRs, and runs the full validation suite after applying. Do not apply Rust/Cargo dependency PRs with this skill.

Diagnose, fix, and manage Mini Diarium's Flatpak/Flathub packaging across the multi-repo ecosystem. Use when Flathub builds fail, the manifest or vendored sources (cargo-sources.json, node-sources.json) need regeneration, the runtime or permissions need bumping, AppStream metadata needs updating, or a Flathub PR needs manual intervention. Also use for initial Flathub submission changes, store listing updates, and any task touching flatpak/, .github/workflows/flathub-publish.yml, or the Flathub repo. Triggers: flathub, flatpak, Flatpak, Flathub, flatpak build, flathub build, vorarbeiter, flatpak-builder, flatpak manifest, flatpak publish, cargo-sources, node-sources, runtime bump, GNOME runtime, SDK extension, AppStream, metainfo, flathub PR, flathub publish, flathub token, flatpak permission, finish-args, flathub submission.

Spawn, probe, and stop Mini Diarium's live Windows Tauri dev app with WebView2 CDP enabled, then hand control to agent-browser for real UI inspection. Use this whenever the user wants to manually test the real desktop UI, drive the dev app, verify a bug or preference in the actual window, inspect localStorage, take a real screenshot, or "actually try it in the app" instead of relying only on unit tests or WDIO. Triggers: manually test the UI, drive the dev app, verify in the real UI, agent dev mode, spawn the dev app, open the running app and check, inspect the live Tauri window.

Mini Diarium's opinionated security, encryption, and privacy stance. Load when touching crypto (src-tauri/src/crypto/), auth (src-tauri/src/auth/, commands/auth/), IPC boundaries (src/lib/errors.ts, tauri.ts), auto-lock (screen_lock.rs, App.tsx idle timer), database schema/migrations (db/schema.rs), backups (backup.rs), config.json / JournalConfig, import/export, plugin sandbox (Rhai), search (intentionally stubbed), debug dump, Tauri capabilities (src-tauri/capabilities/) or CSP (tauri.conf.json), E2E isolation env vars, or anything involving passwords, keys, nonces, zeroization, or entry persistence. Also load when reviewing or proposing new features to judge against the six PHILOSOPHY.md principles and five non-negotiables.

Pre-release checklist for Mini Diarium. Run before tagging a release: verifies version consistency, archives completed TODOs, generates latest-changelog.md, optionally adds a release notification, and stamps the CHANGELOG date. Use when preparing a feature branch for merge and tagging.

Captures lessons from completed tasks and turns them into concrete improvements. Triggers proactively after high-ceremony tasks (build failures, multi-hour sessions, production incidents) and on-demand when the user asks for "post-mortem", "reflect", "improve the skill", "lessons learned", "what went wrong". Covers skills, repo artifacts (scripts, CI, configs), and process changes. For small/obvious fixes, edits directly. For structural changes, produces a plan using the manual-planning format. Use this whenever a task surfaced gaps in tooling, documentation, or automation.

Create, update, review, and execute manual Markdown implementation plans when harness planning mode is not being used. Use when the user asks for a plan file, manual plan, implementation plan, execution plan, roadmap, task checklist, planning document, or agent-maintained plan with statuses, validations, milestones, approval gates, and cleanup steps.

Evaluate a subagent by running its scenario suite as parallel subagents, scoring results against observable criteria, and producing exact FIND/REPLACE edits for any failing behaviors. Use this skill whenever the user wants to evaluate, test, score, or quality-check a subagent — even if they don't use those exact words. Triggers on: "evaluate the agent", "run evals on [agent]", "assess agent performance", "score the agent", "check if the agent works", "run the eval suite", "test the agent", "quality-check [agent]", "is the agent working correctly", or after applying fixes "did that improve things?". Also triggers proactively after an agent file is edited and the user asks "does it work now?" or similar. Triggers: evaluate agent, run evals, assess agent, score agent, test agent, quality-check, eval suite, agent performance, agent working, improve agent, rerun evals, benchmark agent.

Port a repo-specific skill into a generic, reusable skill for the agent-skills library. Use this skill whenever the user asks to extract a skill from a project, generalize a skill, port a skill to another repo, convert a project-specific skill into a reusable one, or remove repo-specific context from a skill. Also use when the user mentions skill extraction, skill generalization, or creating a library skill from a project skill — even if they don't explicitly say "extract" or "generalize." If a skill exists in a project's `.agents/skills/` directory and the user wants to make it reusable across repositories, this skill should be used. Triggers: extract skill, generalize skill, port skill, convert skill, remove repo-specific, make skill reusable, skill extraction, skill generalization, library skill, repo-agnostic skill, skill from project.

End-to-end management of TODO items in a Markdown-based backlog. Covers creation with auto-assigned IDs, status tracking, archival of completed items, and format validation. Use this skill whenever the user asks to add a new TODO, check TODO status, archive completed items, validate the TODO system, or set up a new TODO backlog from scratch. Also use when the user mentions a task list, backlog, roadmap, or task tracking in a Markdown file — even if they don't explicitly say "TODO". If the repo has a `TODO.md` file or similar Markdown-based task tracking, this skill should be used to interact with it. Triggers: TODO, todo item, add todo, create todo, todo status, archive todo, validate TODO, TODO ID, TODO-0001, check TODO, todos, list todos, todo list, backlog, task tracking, roadmap, task list.

Captures lessons from completed tasks and turns them into concrete improvements. Triggers proactively after high-ceremony tasks (build failures, multi-hour sessions, production incidents) and on-demand when the user asks for "post-mortem", "reflect", "improve the skill", "lessons learned", "what went wrong". Covers skills, repo artifacts (scripts, CI, configs), and process changes. For small/obvious fixes, edits directly. For structural changes, produces a plan. Use this whenever a task surfaced gaps in tooling, documentation, or automation.

Create, update, review, and execute manual Markdown implementation plans when harness planning mode is not being used. Use when the user asks for a plan file, manual plan, implementation plan, execution plan, roadmap, task checklist, planning document, or agent-maintained plan with statuses, validations, milestones, approval gates, and cleanup steps.

Create, update, review, and execute manual Markdown implementation plans when harness planning mode is not being used. Use when the user asks for a plan file, manual plan, implementation plan, execution plan, roadmap, task checklist, planning document, or agent-maintained plan with statuses, validations, milestones, approval gates, and cleanup steps.