business-logic-guardian
SolidUse ONLY when a business-logic doc exists — docs/<app>/business-logic-index.md (AI-default retrieval index), docs/<app>/business-logic.md (human narrative), or docs/en/business-logic.md (the app-business-docs canonical for Fusebase CLI teams) — before fixes/improvements that touch business behavior. Treats the documented business logic as a guard layer — the fix must not silently break documented behavior. Pairs with FR-20 zoom-out. If none of these docs exist, this skill does nothing (silent no-op) — do NOT auto-create any of them. Not for net-new features with no documented logic.
Install
Quality Score: 83/100
Skill Content
Details
- Author
- fusebase-dev
- Repository
- fusebase-dev/fusebase-flow
- Created
- 4 months ago
- Last Updated
- 1 weeks ago
- Language
- Shell
- License
- MIT
Bundled in these plugins
Similar Skills
Semantically similar based on skill content — not just same category
logic-guardian
Protects complex business logic from accidental deletion or overwrite. Use when editing payment, trading, state-machine, or other load-bearing business logic where a single deleted line can cause silent data corruption. Maintains a logic manifest, enforces pre-edit gates, validates post-edit diffs.
app-business-docs
Maintain docs/en/business-logic.md in English — human-readable business logic, main user flows, scenarios, and edge cases. Use after domain or workflow code changes, or when revalidating the app during debugging.
business
Creates, maintains and audits BUSINESS.md — the project's business context (why it exists, for whom, its value, scope and non-goals). Works like /init, but for BUSINESS.md: it first establishes the project's ARCHETYPE (library / CLI / service / data-pipeline / AI-system / local-app), which selects a tailored template and a focused question set. Three modes: bootstrap (write the file in a new project), update (reconcile it against the project's state), and `audit` (check reality — code, commits, diff — against the declared non-goals and scope, read-only; in a project that did not install /compliance it also inherits the shared ladder's fallback row for regulated ground). Bootstrap and update end by making the compliance call — whether this project needs COMPLIANCE.md at all. Generic — usable in any project. Do NOT use it for live status (that belongs in PROGRESS.md) or for rules/conventions (they belong in CLAUDE.md).