business-logic-guardian

Solid

Use 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.

AI & Automation 9 stars 0 forks Updated 1 weeks ago MIT

Install

View on GitHub

Quality Score: 83/100

Stars 20%
33
Recency 20%
90
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# Business Logic Guardian > **Style:** Mode-B-lite. **Artifact-gated** — inert unless a business-logic doc exists at ANY path in § Doc-path resolution. ## Purpose Protect documented business logic during fixes and improvements. The business-logic doc is a fast navigation/verify layer: confirm a change does not silently break documented behavior before committing. Complements FR-20 (zoom-out) and FR-10 (reproduce-before-fix). > Consumes whichever business-logic doc exists. Per FR-23 (`flow-skills/documentation-budget/SKILL.md`), the AI-default authoring format is the retrieval index `templates/business-logic-index.md` (tables + source paths); the narrative `templates/business-logic.md` is the explicit human-readable option. This skill reads either as the guard layer. ## Doc-path resolution (the gate checks ALL of these) | Doc | Path | Role | |---|---|---| | Retrieval index (AI-default, FR-23) | `docs/<app>/business-logic-index.md` | primary guard layer when present | | Flow narrative (human option) | `docs/<app>/business-logic.md` | guard layer; supplementary if index exists | | CLI-edition narrative (`app-business-docs` canonical) | `docs/en/business-logic.md` | guard layer for Fusebase CLI teams using the provider skill | If several exist: index first, narratives supplementary. The gate no-ops only when **none** of the three exists. ## When to invoke - Any doc in § Doc-path resolution exists — `docs/<app>/business-logic-index.md` (AI-default), `docs/<app>/business-l...

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

AI & Automation Solid

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.

88 Updated 1 months ago
Rune-kit
AI & Automation Listed

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.

9 Updated 1 weeks ago
fusebase-dev
Data & Documents Listed

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).

0 Updated today
radozaprazny