forgecraft-mcp 1.2.0 → 1.3.2

package/templates/mobile/nfr.yaml

@@ -1,49 +1,49 @@
-tag: MOBILE
-section: nfr
-blocks:
-  - id: mobile-performance
-    tier: recommended
-    title: "Mobile Performance"
-    content: |
-      ## NFR: Mobile Performance
-
-      ### App Size
-      - Initial download: < {{app_size_mb | default: 30}} MB.
-      - On-demand asset downloading for heavy content (maps, ML models, media packs).
-      - Monitor app size in CI — PRs that increase binary > 5% require justification.
-
-      ### Startup
-      - Cold start to interactive: < {{cold_start_ms | default: 2000}} ms.
-      - Lazy-initialize non-critical services. Show skeleton UI immediately.
-      - Splash screen is not a crutch — measure time-to-interactive, not time-to-splash.
-
-      ### Battery & Network
-      - Background work budgeted. No unnecessary wake-locks, polling, or GPS.
-      - Network requests batched where possible. Respect low-data mode settings.
-      - Offline-first: core features work without connectivity. Sync on reconnect.
-
-      ### Runtime
-      - 60 FPS for scrolling and animations. Profile and fix jank.
-      - Memory budget per screen. Monitor for leaks (LeakCanary, Instruments).
-      - No main-thread blocking operations > 16ms.
-
-  - id: mobile-ux
-    tier: recommended
-    title: "Mobile UX Quality"
-    content: |
-      ## NFR: Mobile UX Quality
-
-      ### Platform Compliance
-      - Follow platform guidelines: Material Design (Android), Human Interface Guidelines (iOS).
-      - Support system dark mode, dynamic type / font scaling, and accessibility features.
-      - Deep links and universal links configured and tested.
-
-      ### Crash Rate
-      - Target crash-free rate: ≥ {{crash_free_target | default: 99.5%}}.
-      - Crash reporting (Crashlytics, Sentry) integrated. Crashes triaged within 24 hours.
-      - ANR (Application Not Responding) rate: < 0.5%.
-
-      ### Updates
-      - Over-the-air updates for JS layer (CodePush, Expo Updates) where appropriate.
-      - Force-update mechanism for critical security patches.
-      - Backward-compatible API versioning — old app versions must gracefully degrade.
+tag: MOBILE
+section: nfr
+blocks:
+  - id: mobile-performance
+    tier: recommended
+    title: "Mobile Performance"
+    content: |
+      ## NFR: Mobile Performance
+
+      ### App Size
+      - Initial download: < {{app_size_mb | default: 30}} MB.
+      - On-demand asset downloading for heavy content (maps, ML models, media packs).
+      - Monitor app size in CI — PRs that increase binary > 5% require justification.
+
+      ### Startup
+      - Cold start to interactive: < {{cold_start_ms | default: 2000}} ms.
+      - Lazy-initialize non-critical services. Show skeleton UI immediately.
+      - Splash screen is not a crutch — measure time-to-interactive, not time-to-splash.
+
+      ### Battery & Network
+      - Background work budgeted. No unnecessary wake-locks, polling, or GPS.
+      - Network requests batched where possible. Respect low-data mode settings.
+      - Offline-first: core features work without connectivity. Sync on reconnect.
+
+      ### Runtime
+      - 60 FPS for scrolling and animations. Profile and fix jank.
+      - Memory budget per screen. Monitor for leaks (LeakCanary, Instruments).
+      - No main-thread blocking operations > 16ms.
+
+  - id: mobile-ux
+    tier: recommended
+    title: "Mobile UX Quality"
+    content: |
+      ## NFR: Mobile UX Quality
+
+      ### Platform Compliance
+      - Follow platform guidelines: Material Design (Android), Human Interface Guidelines (iOS).
+      - Support system dark mode, dynamic type / font scaling, and accessibility features.
+      - Deep links and universal links configured and tested.
+
+      ### Crash Rate
+      - Target crash-free rate: ≥ {{crash_free_target | default: 99.5%}}.
+      - Crash reporting (Crashlytics, Sentry) integrated. Crashes triaged within 24 hours.
+      - ANR (Application Not Responding) rate: < 0.5%.
+
+      ### Updates
+      - Over-the-air updates for JS layer (CodePush, Expo Updates) where appropriate.
+      - Force-update mechanism for critical security patches.
+      - Backward-compatible API versioning — old app versions must gracefully degrade.

package/templates/mobile/structure.yaml

@@ -1,27 +1,27 @@
-tag: MOBILE
-section: structure
-entries:
-  - path: src/screens/
-    description: "Screen-level components — one directory per screen"
-  - path: src/components/
-    description: "Shared UI components: buttons, cards, inputs, modals"
-  - path: src/navigation/
-    description: "Navigation configuration: stack, tab, drawer navigators"
-  - path: src/services/
-    description: "API client, storage, auth, push notifications, analytics"
-  - path: src/hooks/
-    description: "Custom React Native hooks"
-  - path: src/store/
-    description: "State management: slices, selectors, async thunks"
-  - path: src/utils/
-    description: "Platform-agnostic utilities and helpers"
-  - path: src/theme/
-    description: "Design tokens, colors, typography, spacing"
-  - path: src/locales/
-    description: "Translation JSON files per locale"
-  - path: assets/
-    description: "Images, fonts, animations (Lottie)"
-  - path: __tests__/
-    description: "Unit and integration tests"
-  - path: e2e/
-    description: "End-to-end tests (Detox, Maestro, or Appium)"
+tag: MOBILE
+section: structure
+entries:
+  - path: src/screens/
+    description: "Screen-level components — one directory per screen"
+  - path: src/components/
+    description: "Shared UI components: buttons, cards, inputs, modals"
+  - path: src/navigation/
+    description: "Navigation configuration: stack, tab, drawer navigators"
+  - path: src/services/
+    description: "API client, storage, auth, push notifications, analytics"
+  - path: src/hooks/
+    description: "Custom React Native hooks"
+  - path: src/store/
+    description: "State management: slices, selectors, async thunks"
+  - path: src/utils/
+    description: "Platform-agnostic utilities and helpers"
+  - path: src/theme/
+    description: "Design tokens, colors, typography, spacing"
+  - path: src/locales/
+    description: "Translation JSON files per locale"
+  - path: assets/
+    description: "Images, fonts, animations (Lottie)"
+  - path: __tests__/
+    description: "Unit and integration tests"
+  - path: e2e/
+    description: "End-to-end tests (Detox, Maestro, or Appium)"

package/templates/mobile/verification.yaml

@@ -1,121 +1,121 @@
-tag: MOBILE
-section: verification
-title: "Mobile Navigational Path + Screenshot Verification"
-description: >
-  Mobile UI behavior has the same behavioral uncertainty as WEB-REACT but adds
-  platform-specific dimensions: touch targets, safe areas, OS permission dialogs,
-  hardware back button, deep links, and push notification appearance.
-  This strategy uses Playwright for React Native Web or Appium for native,
-  with Claude Vision assertions for screenshot-based behavioral contracts.
-uncertainty_levels:
-  - behavioral
-completeness_ceiling: 0.80
-
-phases:
-
-  - id: contract-definition
-    title: "Define Mobile Navigation Contracts"
-    rationale: >
-      Mobile UX contracts must account for both platforms (iOS + Android) and
-      at minimum two viewport sizes (phone + tablet). Navigation paths must account
-      for OS-level interruptions: permission dialogs, push notifications, app backgrounding.
-    steps:
-      - id: define-use-case-paths
-        instruction: >
-          For each screen flow, define a numbered navigational path:
-          1. Starting screen and initial state
-          2. User gestures (tap, swipe, long-press, pinch) in order
-          3. Expected screen and visible elements after each gesture
-          4. Platform-specific branches (iOS vs Android where behavior diverges)
-          5. Terminal state (e.g., "payment confirmation screen with order summary visible")
-          Store in docs/use-cases/{feature}-mobile.md.
-        contract: >
-          docs/use-cases/ has *-mobile.md files.
-          Each file documents iOS and Android paths separately where they diverge.
-        tools: ["filesystem"]
-        expected_output: "docs/use-cases/checkout-mobile.md with iOS and Android sections"
-        pass_criterion: "File count in docs/use-cases/ matching *-mobile.md ≥ number of screen flows"
-
-      - id: define-touch-target-contracts
-        instruction: >
-          For every interactive element, define:
-          - Minimum tap target size (Apple HIG: 44x44pt, Material: 48x48dp)
-          - Minimum spacing between adjacent targets (Apple: 8pt, Material: 8dp)
-          - Label text for accessibility (VoiceOver / TalkBack)
-          Store in docs/mobile-accessibility-contracts.md.
-        contract: "docs/mobile-accessibility-contracts.md with ≥1 row per interactive element type"
-        tools: ["filesystem"]
-        expected_output: "| primary-button | 44x44pt | 8pt | 'Submit order' |"
-        pass_criterion: "File exists with tap target sizes and accessibility labels"
-
-  - id: execution
-    title: "Run Automated Tests + Screenshot Assertions"
-    rationale: >
-      Playwright for RN Web or Appium for native drives real gestures on emulators.
-      Screenshots at each step are asserted via Claude Vision against the contracts.
-      Touch target sizes are measured programmatically — no manual measurement.
-    steps:
-      - id: run-navigation-tests
-        instruction: >
-          Write and execute one test per use-case path. Use Playwright (RN Web) or Appium (native).
-          Each test:
-          1. Launches the app in the correct initial state
-          2. Executes gestures in the contracted order
-          3. Takes a screenshot after each state transition
-          4. Asserts DOM/hierarchy elements visible at each step
-          Run on iOS Simulator + Android Emulator.
-        contract: >
-          Test files present per use case. All tests pass on both platforms.
-          Screenshots saved per step in test-results/mobile/screenshots/.
-        tools: ["npx playwright test", "appium", "xcrun simctl", "emulator -avd"]
-        expected_output: "Test results + screenshots in test-results/mobile/"
-        pass_criterion: "All tests pass on both platforms; 0 failing navigation assertions"
-
-      - id: assert-screenshots-with-vision
-        instruction: >
-          For each screenshot, call Claude Vision with:
-          - The screenshot
-          - The platform (iOS/Android) and viewport (phone/tablet)
-          - The visual contract for that state
-          - Prompt: "Assert this mobile screenshot against the contract. List any FAILS. If all pass: PASS."
-          Run on all platform + viewport combinations.
-        contract: "All vision assertions return PASS on both platforms and both viewports"
-        tools: ["claude --vision", "anthropic vision API"]
-        expected_output: "vision-results.json: [{platform, viewport, screen, result}]"
-        pass_criterion: "All result = PASS"
-        requires_human_review: true
-
-      - id: measure-touch-targets
-        instruction: >
-          Using the accessibility tree (iOS Accessibility Inspector or Android UIAutomator),
-          retrieve the bounding rect of every interactive element. Assert that each element
-          meets the tap target size in docs/mobile-accessibility-contracts.md.
-        contract: "All interactive elements meet minimum tap target size on both platforms"
-        tools: ["XCTest accessibilityFrame", "UIAutomator getBounds", "accessibility-inspector"]
-        expected_output: "touch-target-report.json: [{element, platform, size_pt, passes_contract}]"
-        pass_criterion: "All passes_contract = true"
-
-  - id: evidence
-    title: "Persist Screenshots and Platform Test Reports"
-    rationale: >
-      Mobile screenshots are the only reliable evidence of cross-platform visual fidelity.
-      They must be committed or archived per release so regressions are detectable.
-    steps:
-      - id: persist-screenshots
-        instruction: >
-          Save one screenshot per step per platform to test-results/mobile/screenshots/{platform}/{test}/{step}.png.
-          Compress to <500KB per screenshot. Include platform, OS version, and app version in filename.
-        contract: "Screenshots exist for all tests on all platforms"
-        tools: ["playwright screenshot", "appium driver.saveScreenshot"]
-        expected_output: "test-results/mobile/screenshots/ios/checkout/step-3-confirm.png"
-        pass_criterion: "Screenshot count matches steps × platforms"
-
-      - id: persist-platform-reports
-        instruction: >
-          Save the JUnit XML report from Playwright/Appium to test-results/mobile/.
-          Save vision-results.json and touch-target-report.json to the same directory.
-          Record platform and OS versions tested in test-results/mobile/environment.json.
-        contract: "test-results/mobile/ has report, vision-results, touch-target-report, environment"
-        tools: ["playwright --reporter=junit", "appium --reporter"]
-        expected_output: "All 4 files present in test-results/mobile/"
-        pass_criterion: "Files exist and parse as valid JSON/XML"
+tag: MOBILE
+section: verification
+title: "Mobile Navigational Path + Screenshot Verification"
+description: >
+  Mobile UI behavior has the same behavioral uncertainty as WEB-REACT but adds
+  platform-specific dimensions: touch targets, safe areas, OS permission dialogs,
+  hardware back button, deep links, and push notification appearance.
+  This strategy uses Playwright for React Native Web or Appium for native,
+  with Claude Vision assertions for screenshot-based behavioral contracts.
+uncertainty_levels:
+  - behavioral
+completeness_ceiling: 0.80
+
+phases:
+
+  - id: contract-definition
+    title: "Define Mobile Navigation Contracts"
+    rationale: >
+      Mobile UX contracts must account for both platforms (iOS + Android) and
+      at minimum two viewport sizes (phone + tablet). Navigation paths must account
+      for OS-level interruptions: permission dialogs, push notifications, app backgrounding.
+    steps:
+      - id: define-use-case-paths
+        instruction: >
+          For each screen flow, define a numbered navigational path:
+          1. Starting screen and initial state
+          2. User gestures (tap, swipe, long-press, pinch) in order
+          3. Expected screen and visible elements after each gesture
+          4. Platform-specific branches (iOS vs Android where behavior diverges)
+          5. Terminal state (e.g., "payment confirmation screen with order summary visible")
+          Store in docs/use-cases/{feature}-mobile.md.
+        contract: >
+          docs/use-cases/ has *-mobile.md files.
+          Each file documents iOS and Android paths separately where they diverge.
+        tools: ["filesystem"]
+        expected_output: "docs/use-cases/checkout-mobile.md with iOS and Android sections"
+        pass_criterion: "File count in docs/use-cases/ matching *-mobile.md ≥ number of screen flows"
+
+      - id: define-touch-target-contracts
+        instruction: >
+          For every interactive element, define:
+          - Minimum tap target size (Apple HIG: 44x44pt, Material: 48x48dp)
+          - Minimum spacing between adjacent targets (Apple: 8pt, Material: 8dp)
+          - Label text for accessibility (VoiceOver / TalkBack)
+          Store in docs/mobile-accessibility-contracts.md.
+        contract: "docs/mobile-accessibility-contracts.md with ≥1 row per interactive element type"
+        tools: ["filesystem"]
+        expected_output: "| primary-button | 44x44pt | 8pt | 'Submit order' |"
+        pass_criterion: "File exists with tap target sizes and accessibility labels"
+
+  - id: execution
+    title: "Run Automated Tests + Screenshot Assertions"
+    rationale: >
+      Playwright for RN Web or Appium for native drives real gestures on emulators.
+      Screenshots at each step are asserted via Claude Vision against the contracts.
+      Touch target sizes are measured programmatically — no manual measurement.
+    steps:
+      - id: run-navigation-tests
+        instruction: >
+          Write and execute one test per use-case path. Use Playwright (RN Web) or Appium (native).
+          Each test:
+          1. Launches the app in the correct initial state
+          2. Executes gestures in the contracted order
+          3. Takes a screenshot after each state transition
+          4. Asserts DOM/hierarchy elements visible at each step
+          Run on iOS Simulator + Android Emulator.
+        contract: >
+          Test files present per use case. All tests pass on both platforms.
+          Screenshots saved per step in test-results/mobile/screenshots/.
+        tools: ["npx playwright test", "appium", "xcrun simctl", "emulator -avd"]
+        expected_output: "Test results + screenshots in test-results/mobile/"
+        pass_criterion: "All tests pass on both platforms; 0 failing navigation assertions"
+
+      - id: assert-screenshots-with-vision
+        instruction: >
+          For each screenshot, call Claude Vision with:
+          - The screenshot
+          - The platform (iOS/Android) and viewport (phone/tablet)
+          - The visual contract for that state
+          - Prompt: "Assert this mobile screenshot against the contract. List any FAILS. If all pass: PASS."
+          Run on all platform + viewport combinations.
+        contract: "All vision assertions return PASS on both platforms and both viewports"
+        tools: ["claude --vision", "anthropic vision API"]
+        expected_output: "vision-results.json: [{platform, viewport, screen, result}]"
+        pass_criterion: "All result = PASS"
+        requires_human_review: true
+
+      - id: measure-touch-targets
+        instruction: >
+          Using the accessibility tree (iOS Accessibility Inspector or Android UIAutomator),
+          retrieve the bounding rect of every interactive element. Assert that each element
+          meets the tap target size in docs/mobile-accessibility-contracts.md.
+        contract: "All interactive elements meet minimum tap target size on both platforms"
+        tools: ["XCTest accessibilityFrame", "UIAutomator getBounds", "accessibility-inspector"]
+        expected_output: "touch-target-report.json: [{element, platform, size_pt, passes_contract}]"
+        pass_criterion: "All passes_contract = true"
+
+  - id: evidence
+    title: "Persist Screenshots and Platform Test Reports"
+    rationale: >
+      Mobile screenshots are the only reliable evidence of cross-platform visual fidelity.
+      They must be committed or archived per release so regressions are detectable.
+    steps:
+      - id: persist-screenshots
+        instruction: >
+          Save one screenshot per step per platform to test-results/mobile/screenshots/{platform}/{test}/{step}.png.
+          Compress to <500KB per screenshot. Include platform, OS version, and app version in filename.
+        contract: "Screenshots exist for all tests on all platforms"
+        tools: ["playwright screenshot", "appium driver.saveScreenshot"]
+        expected_output: "test-results/mobile/screenshots/ios/checkout/step-3-confirm.png"
+        pass_criterion: "Screenshot count matches steps × platforms"
+
+      - id: persist-platform-reports
+        instruction: >
+          Save the JUnit XML report from Playwright/Appium to test-results/mobile/.
+          Save vision-results.json and touch-target-report.json to the same directory.
+          Record platform and OS versions tested in test-results/mobile/environment.json.
+        contract: "test-results/mobile/ has report, vision-results, touch-target-report, environment"
+        tools: ["playwright --reporter=junit", "appium --reporter"]
+        expected_output: "All 4 files present in test-results/mobile/"
+        pass_criterion: "Files exist and parse as valid JSON/XML"

package/templates/observability-xray/instructions.yaml

@@ -1,40 +1,40 @@
-tag: OBSERVABILITY-XRAY
-section: instructions
-blocks:
-  - id: xray-lambda-instrumentation
-    tier: recommended
-    title: "Auto-Add X-Ray Instrumentation to Lambdas"
-    content: |
-      ## Auto-Add X-Ray Instrumentation to Lambdas
-
-      - Enable X-Ray active tracing on every Lambda function by default. Set `tracing: Active` in SAM/CloudFormation or `tracing_config { mode = "Active" }` in Terraform.
-      - Wrap the AWS SDK client with the X-Ray SDK to automatically trace all downstream AWS service calls (DynamoDB, S3, SQS, SNS).
-      - Add X-Ray middleware or decorators to every Lambda handler. No handler should execute without producing a trace segment.
-      - Include custom subsegments for business-critical operations: database queries, external API calls, heavy computations.
-      - Propagate trace headers across service boundaries: ensure `X-Amzn-Trace-Id` is forwarded in HTTP headers and SQS message attributes.
-      - Set sampling rules appropriate to traffic volume: 100% for low-traffic, reservoir-based for high-traffic. Document sampling decisions.
-
-  - id: xray-annotations-metadata
-    tier: recommended
-    title: "X-Ray Annotations & Metadata Standards"
-    content: |
-      ## X-Ray Annotations & Metadata Standards
-
-      - Add annotations for every trace: `service`, `environment`, `version`, `userId` (hashed), `correlationId`. Annotations are indexed and searchable.
-      - Use metadata for non-indexed debug data: request/response sizes, feature flags, cache hit/miss ratios.
-      - Define a standard annotation taxonomy across all services. No ad-hoc annotation keys — use a shared enum or constant file.
-      - Create X-Ray groups for critical paths: user-facing APIs, payment flows, data pipelines. Monitor group error rates and latency.
-      - Set up X-Ray insights for automated anomaly detection on critical service groups.
-      - Include X-Ray trace IDs in error responses and log entries for cross-referencing between traces and logs.
-
-  - id: xray-alerting
-    tier: optional
-    title: "X-Ray-Based Alerting & SLOs"
-    content: |
-      ## X-Ray-Based Alerting & SLOs
-
-      - Define SLOs per service using X-Ray latency and error rate data: p50, p95, p99 latency targets and error budget thresholds.
-      - Create CloudWatch alarms from X-Ray service maps: alert on elevated fault rates, latency spikes, or throttling.
-      - Monitor cold start impact via X-Ray initialization subsegments. Alert if cold start percentage exceeds threshold.
-      - Build dashboards combining X-Ray service map data with CloudWatch metrics for a unified observability view.
-      - Review X-Ray traces weekly for optimization opportunities: unnecessary downstream calls, serial-when-could-be-parallel patterns.
+tag: OBSERVABILITY-XRAY
+section: instructions
+blocks:
+  - id: xray-lambda-instrumentation
+    tier: recommended
+    title: "Auto-Add X-Ray Instrumentation to Lambdas"
+    content: |
+      ## Auto-Add X-Ray Instrumentation to Lambdas
+
+      - Enable X-Ray active tracing on every Lambda function by default. Set `tracing: Active` in SAM/CloudFormation or `tracing_config { mode = "Active" }` in Terraform.
+      - Wrap the AWS SDK client with the X-Ray SDK to automatically trace all downstream AWS service calls (DynamoDB, S3, SQS, SNS).
+      - Add X-Ray middleware or decorators to every Lambda handler. No handler should execute without producing a trace segment.
+      - Include custom subsegments for business-critical operations: database queries, external API calls, heavy computations.
+      - Propagate trace headers across service boundaries: ensure `X-Amzn-Trace-Id` is forwarded in HTTP headers and SQS message attributes.
+      - Set sampling rules appropriate to traffic volume: 100% for low-traffic, reservoir-based for high-traffic. Document sampling decisions.
+
+  - id: xray-annotations-metadata
+    tier: recommended
+    title: "X-Ray Annotations & Metadata Standards"
+    content: |
+      ## X-Ray Annotations & Metadata Standards
+
+      - Add annotations for every trace: `service`, `environment`, `version`, `userId` (hashed), `correlationId`. Annotations are indexed and searchable.
+      - Use metadata for non-indexed debug data: request/response sizes, feature flags, cache hit/miss ratios.
+      - Define a standard annotation taxonomy across all services. No ad-hoc annotation keys — use a shared enum or constant file.
+      - Create X-Ray groups for critical paths: user-facing APIs, payment flows, data pipelines. Monitor group error rates and latency.
+      - Set up X-Ray insights for automated anomaly detection on critical service groups.
+      - Include X-Ray trace IDs in error responses and log entries for cross-referencing between traces and logs.
+
+  - id: xray-alerting
+    tier: optional
+    title: "X-Ray-Based Alerting & SLOs"
+    content: |
+      ## X-Ray-Based Alerting & SLOs
+
+      - Define SLOs per service using X-Ray latency and error rate data: p50, p95, p99 latency targets and error budget thresholds.
+      - Create CloudWatch alarms from X-Ray service maps: alert on elevated fault rates, latency spikes, or throttling.
+      - Monitor cold start impact via X-Ray initialization subsegments. Alert if cold start percentage exceeds threshold.
+      - Build dashboards combining X-Ray service map data with CloudWatch metrics for a unified observability view.
+      - Review X-Ray traces weekly for optimization opportunities: unnecessary downstream calls, serial-when-could-be-parallel patterns.

package/templates/observability-xray/mcp-servers.yaml

@@ -1,15 +1,15 @@
-tag: OBSERVABILITY-XRAY
-section: mcp-servers
-servers:
-  - name: aws-cloudwatch
-    description: "AWS CloudWatch logs and metrics — query X-Ray traces, view Lambda logs, monitor alarms"
-    command: npx
-    args: ["-y", "mcp-server-cloudwatch"]
-    tags: [OBSERVABILITY-XRAY, INFRA]
-    category: monitoring
-    tier: recommended
-    env:
-      AWS_REGION: ""
-      AWS_ACCESS_KEY_ID: ""
-      AWS_SECRET_ACCESS_KEY: ""
-    url: "https://github.com/modelcontextprotocol/servers"
+tag: OBSERVABILITY-XRAY
+section: mcp-servers
+servers:
+  - name: aws-cloudwatch
+    description: "AWS CloudWatch logs and metrics — query X-Ray traces, view Lambda logs, monitor alarms"
+    command: npx
+    args: ["-y", "mcp-server-cloudwatch"]
+    tags: [OBSERVABILITY-XRAY, INFRA]
+    category: monitoring
+    tier: recommended
+    env:
+      AWS_REGION: ""
+      AWS_ACCESS_KEY_ID: ""
+      AWS_SECRET_ACCESS_KEY: ""
+    url: "https://github.com/modelcontextprotocol/servers"

package/templates/realtime/instructions.yaml

@@ -1,42 +1,42 @@
-tag: REALTIME
-section: instructions
-blocks:
-  - id: websocket-patterns
-    tier: recommended
-    title: "WebSocket & Connection Management"
-    content: |
-      ## WebSocket & Connection Lifecycle
-
-      - Implement automatic reconnection with exponential backoff and jitter (base 1s, max 30s). Track connection state (connecting, open, closing, closed) and expose it to the UI.
-      - Use heartbeat/ping-pong frames at regular intervals (every 30s) to detect dead connections. Close and reconnect if a pong is not received within the timeout window.
-      - Authenticate WebSocket connections during the handshake (via token in query param or first message). Reject unauthenticated connections immediately—do not allow message exchange before auth.
-      - Assign each connection a unique session ID. Map sessions to user identities server-side for targeted messaging, presence tracking, and connection auditing.
-      - Support graceful degradation: if WebSocket connections fail (corporate proxies, firewalls), fall back to Server-Sent Events or long polling automatically.
-      - Implement connection rate limiting per IP and per user to prevent resource exhaustion from misbehaving clients or attacks.
-      - Buffer outbound messages on the client during disconnection and replay them in order upon reconnection to avoid data loss.
-
-  - id: event-driven-architecture
-    tier: recommended
-    title: "Event-Driven Architecture"
-    content: |
-      ## Event-Driven & Pub/Sub Patterns
-
-      - Use a message broker (Redis Pub/Sub, NATS, Kafka) to fan out events across multiple server instances. Never rely on in-process state for multi-node real-time systems.
-      - Define a clear event schema with versioning. Every event must include: event type, version, timestamp, producer ID, correlation ID, and payload.
-      - Implement topic-based or channel-based subscriptions. Clients should subscribe only to the channels they need to minimize unnecessary message delivery.
-      - Use message acknowledgment for critical events: the consumer must explicitly ack after processing. Unacked messages are redelivered after a timeout.
-      - Deduplicate events on the consumer side using the event ID. Network retries and broker redelivery can produce duplicates that must not cause double-processing.
-      - Separate command messages (requests to change state) from event messages (notifications of state changes). Commands go to a single handler; events fan out to many subscribers.
-
-  - id: backpressure-scaling
-    tier: recommended
-    title: "Backpressure & Scaling"
-    content: |
-      ## Backpressure, Flow Control & Scaling
-
-      - Implement backpressure at every layer. If a consumer cannot keep up, signal the producer to slow down rather than buffering unboundedly and risking OOM.
-      - Set maximum buffer sizes for outbound message queues per connection. If the buffer fills (slow client), drop non-critical messages or disconnect the client with a warning.
-      - Use rate limiting on inbound messages per client (e.g., max 100 messages/second). Reject excess messages with an error code rather than silently dropping them.
-      - Design for horizontal scaling: use sticky sessions or a shared session store so that any server node can handle any client's messages after a reconnection.
-      - Monitor key metrics: active connections, messages per second (in/out), message latency p50/p95/p99, buffer utilization, and reconnection rate. Alert on anomalies.
-      - Load-test real-time features with realistic connection counts (10x expected peak) and message rates to identify bottlenecks before they appear in production.
+tag: REALTIME
+section: instructions
+blocks:
+  - id: websocket-patterns
+    tier: recommended
+    title: "WebSocket & Connection Management"
+    content: |
+      ## WebSocket & Connection Lifecycle
+
+      - Implement automatic reconnection with exponential backoff and jitter (base 1s, max 30s). Track connection state (connecting, open, closing, closed) and expose it to the UI.
+      - Use heartbeat/ping-pong frames at regular intervals (every 30s) to detect dead connections. Close and reconnect if a pong is not received within the timeout window.
+      - Authenticate WebSocket connections during the handshake (via token in query param or first message). Reject unauthenticated connections immediately—do not allow message exchange before auth.
+      - Assign each connection a unique session ID. Map sessions to user identities server-side for targeted messaging, presence tracking, and connection auditing.
+      - Support graceful degradation: if WebSocket connections fail (corporate proxies, firewalls), fall back to Server-Sent Events or long polling automatically.
+      - Implement connection rate limiting per IP and per user to prevent resource exhaustion from misbehaving clients or attacks.
+      - Buffer outbound messages on the client during disconnection and replay them in order upon reconnection to avoid data loss.
+
+  - id: event-driven-architecture
+    tier: recommended
+    title: "Event-Driven Architecture"
+    content: |
+      ## Event-Driven & Pub/Sub Patterns
+
+      - Use a message broker (Redis Pub/Sub, NATS, Kafka) to fan out events across multiple server instances. Never rely on in-process state for multi-node real-time systems.
+      - Define a clear event schema with versioning. Every event must include: event type, version, timestamp, producer ID, correlation ID, and payload.
+      - Implement topic-based or channel-based subscriptions. Clients should subscribe only to the channels they need to minimize unnecessary message delivery.
+      - Use message acknowledgment for critical events: the consumer must explicitly ack after processing. Unacked messages are redelivered after a timeout.
+      - Deduplicate events on the consumer side using the event ID. Network retries and broker redelivery can produce duplicates that must not cause double-processing.
+      - Separate command messages (requests to change state) from event messages (notifications of state changes). Commands go to a single handler; events fan out to many subscribers.
+
+  - id: backpressure-scaling
+    tier: recommended
+    title: "Backpressure & Scaling"
+    content: |
+      ## Backpressure, Flow Control & Scaling
+
+      - Implement backpressure at every layer. If a consumer cannot keep up, signal the producer to slow down rather than buffering unboundedly and risking OOM.
+      - Set maximum buffer sizes for outbound message queues per connection. If the buffer fills (slow client), drop non-critical messages or disconnect the client with a warning.
+      - Use rate limiting on inbound messages per client (e.g., max 100 messages/second). Reject excess messages with an error code rather than silently dropping them.
+      - Design for horizontal scaling: use sticky sessions or a shared session store so that any server node can handle any client's messages after a reconnection.
+      - Monitor key metrics: active connections, messages per second (in/out), message latency p50/p95/p99, buffer utilization, and reconnection rate. Alert on anomalies.
+      - Load-test real-time features with realistic connection counts (10x expected peak) and message rates to identify bottlenecks before they appear in production.

package/templates/realtime/mcp-servers.yaml

@@ -1,13 +1,13 @@
-tag: REALTIME
-section: mcp-servers
-servers:
-  - name: redis
-    description: "Redis key-value store management — pub/sub, streams, caching, and session management"
-    command: npx
-    args: ["-y", "mcp-server-redis"]
-    tags: [REALTIME]
-    category: database
-    tier: recommended
-    env:
-      REDIS_URL: "redis://localhost:6379"
-    url: "https://github.com/nicholasgriffintn/redis-mcp-server"
+tag: REALTIME
+section: mcp-servers
+servers:
+  - name: redis
+    description: "Redis key-value store management — pub/sub, streams, caching, and session management"
+    command: npx
+    args: ["-y", "mcp-server-redis"]
+    tags: [REALTIME]
+    category: database
+    tier: recommended
+    env:
+      REDIS_URL: "redis://localhost:6379"
+    url: "https://github.com/nicholasgriffintn/redis-mcp-server"