open-accounting
open-accounting contiene 10 skills recopiladas de HMB-research, con cobertura ocupacional por repositorio y páginas de detalle dentro del sitio.
Skills en este repositorio
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.
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 when implementing or reviewing accounting-sensitive open-accounting workflows such as payment reversals, invoice paid-state changes, journal void/reopen flows, period locks, evidence blockers, or any change that could rewrite accounting history.
Use when adding, refactoring, or testing open-accounting external import formats, especially bank/provider-specific mappers, LHV statement samples, mapper registries, API/CLI format parity, and removal of legacy parser paths.
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.