Menü
Use when updating or creating open-accounting repo skills after workflow friction, repeated mistakes, user preference changes, staged PR learnings, or requests to improve the development flow.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
| name | open-accounting-skill-maintenance |
| description | Use when updating or creating open-accounting repo skills after workflow friction, repeated mistakes, user preference changes, staged PR learnings, or requests to improve the development flow. |
Use this with open-accounting-development when the user asks to update skills or a stage reveals guidance future agents should follow.
open-accounting-development or the nearest coordinator skill so future activation is discoverable.After skill edits:
git diff --check -- .agents/skills
If skill changes accompany code changes, include them in the same stage commit after the relevant product gates pass.
Use when migrating data from SmartAccounts.eu into open-accounting, preparing SmartAccounts CSV/XML export snapshots, validating SmartAccounts provider preset bundles, mapping missing feature coverage, or building migration runbooks/tools for SmartAccounts cutovers.
Use when advancing open-accounting in staged PR work, especially CLI/API/docs parity, UI workflow coverage, local validation gates, commits, pushes, and PR/CI follow-through.
Use when developing or debugging open-accounting - covers multi-tenant architecture, testing strategy (especially E2E for demo interface), and layer responsibilities. Activate for feature work, bug fixes, test writing, or demo mode issues.
Use when running or debugging open-accounting local demo Playwright E2E, including demo reset, auth setup, API/frontend ports, CORS, stale localhost servers, and branch-code verification.
Use when editing open-accounting Svelte routes, components, or frontend tests, especially form payloads, tenant-scoped UI, demo E2E assertions, Svelte MCP validation, and Playwright locator stability.
Use when an open-accounting PR has merge conflicts, conflicted frontend tests, stale branch state, or a pushed stage needs conflict resolution followed by local tests and PR check recovery.