<< All versions

Skill v1.0.2

currentAutomated scan100/100
janpereira-dev/ngautopilot/angular-architecture-micro-frontends-fallback-and-rollback

+4 new

──Details
PublishedNovember 5, 2026 at 09:57 PM
Content Hashsha256:348cdf3eec263a59...
Git SHA10fb3bd52589
Bump Typepatch
Compare with v1.0.1
──Files
Files (1 file, 2.3 KB)
SKILL.md2.3 KBactive
SKILL.md · 93 lines · 2.3 KB

name: angular-architecture-micro-frontends-fallback-and-rollback description: "Designs fallback and rollback behavior for Angular micro-frontends in Nx monorepos, focusing on remote load failure, safe degradation, retry flow, and release rollback readiness." license: MIT metadata: version: "1.0.2" ngautopilot-id: "angular.architecture.micro-frontends-fallback-and-rollback" ngautopilot-source: "skills/angular/architecture/micro-frontends-fallback-and-rollback/SKILL.md" ngautopilot-version: "0.11.0"


Micro-frontends Fallback and Rollback

Purpose

Use this skill to design fallback and rollback behavior for Angular micro-frontends.

Runtime composition makes failure a normal case, not an edge case. The shell must remain usable when a remote cannot load, and the release process must allow quick rollback when a bad remote slips through.

The core rule is simple:

txt
Assume remotes fail and plan for safe recovery.

When to Use

Use this skill when:

  • remote loading may fail at runtime
  • fallback UX is required
  • retry behavior needs to be defined
  • release rollback must be fast
  • a shell needs to degrade safely when a remote is unavailable

Do

Define fallback tiers:

txt
1. Inline retry
2. Safe fallback screen
3. Route redirect
4. Degraded shell mode

Keep fallback behavior user-centered:

txt
- explain the failure
- preserve navigation where possible
- avoid blank shells
- allow retry if the condition may self-resolve

Document rollback readiness:

txt
- last known good version
- rollback trigger
- rollback owner
- rollback window
- verification after rollback

Do Not

Avoid silent failures.

Avoid a blank screen when a remote dies.

Avoid rollback procedures that depend on manual tribal knowledge.

Avoid fallback behavior that hides the fact that a remote is broken.

Review Checklist

  • [ ] Fallback exists for remote load failure.
  • [ ] Retry behavior is defined.
  • [ ] Shell remains navigable under failure.
  • [ ] Rollback can be executed quickly.
  • [ ] The user gets a clear failure state.
  • [ ] Recovery steps are documented.

Expected Output

  1. Identify failure scenarios.
  2. Define fallback tiers.
  3. Specify rollback readiness requirements.
  4. Recommend UX that preserves shell usability.
  5. Produce a safe recovery plan.
← v1.0.1All versions