app-business-docs

Keeping business logic documentation aligned with code changes requires syncing human-readable docs after modifications to routes, validation rules, permissions, and multi-step flows. This Skill maintains a canonical markdown file at docs/en/business-logic.md to eliminate context rot.

Documenting app user flows and edge cases is best handled by maintaining a single source of truth covering product overview, actor roles, main scenarios, edge case behavior, and high-level code maps. This produces a canonical markdown file reflecting observable implemented behavior.

Revalidating stale documentation during debugging is supported by comparing existing docs against current code to catch outdated information. This ensures team members and AI agents understand the application's purpose and domain rules without manually reviewing all underlying code.

Generating initial onboarding docs for a new application involves creating documentation once it reaches a coherent functional state. This Skill produces a canonical English business logic markdown file covering domain rules and user flows for both client-facing and internal applications built with FuseBase Flow.

This documentation approach works with both client-facing and internal applications built with FuseBase Flow. It maintains a canonical markdown file at docs/en/business-logic.md covering product overview, actor roles, main scenarios, edge case behavior, and high-level code maps.

You should update business logic documentation after making changes to core domain logic, user flows, or validation rules. This prevents context rot and misalignment during development and debugging by keeping the canonical markdown file synced with observable implemented behavior.