frontend-notifications

Select Drumr frontend feedback APIs for messages, modals, and notifications.

Updated Sep 16, 2025
One-click install
npx skills add https://github.com/slingr-stack/qa-test-drumr --skill frontend-notifications
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: frontend-notifications
Source: https://github.com/slingr-stack/qa-test-drumr/tree/main/project-management-app/.agents/skills/frontend-notifications
Command: npx skills add https://github.com/slingr-stack/qa-test-drumr --skill frontend-notifications

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill standardizes how Drumr frontend code shows success, warning, error, and confirmation feedback so teams avoid inconsistent notifications and unsafe bootstrapping patterns.

Core Features & Use Cases

  • Choose getApp() for services, utilities, and callbacks that run outside React render paths.
  • Choose App.useApp() inside function components and use the returned message, modal, and notification APIs in local handlers.
  • Replace direct antd feedback imports and manual bootstrap wiring with framework-aligned app access.
  • Use it when confirming destructive actions, reporting async outcomes, or surfacing validation and execution results in views and actions.

Quick Start

Tell the assistant to update your Drumr frontend code so it uses getApp() or App.useApp() for user feedback and removes any direct antd message, modal, or notification usage.

Frequently Asked Questions about frontend-notifications

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I show frontend notifications consistently in React without direct antd imports?

To show frontend notifications consistently, use the framework-aligned app access APIs instead of direct antd imports. Services, utilities, and callbacks should use getApp() to access message, modal, and notification APIs, while rendered function components should use App.useApp().

When do I use getApp versus App.useApp for modal and message feedback?

Use getApp() for runtime callbacks, services, and utilities that execute outside the React render path. Use App.useApp() inside rendered function components to locally access message, modal, and notification handlers for confirmations and async status updates.

Why should I avoid manual bootstrap wiring for antd message and modal notifications?

Avoiding manual bootstrap wiring for antd notifications prevents unsafe bootstrapping patterns and inconsistent feedback. Standardizing on getApp() or App.useApp() ensures safe, framework-aligned access to message, modal, and notification APIs across all views and component handlers.

Does this approach work for confirming destructive actions and async execution results?

Yes, this approach works for confirming destructive actions and surfacing async execution results. It standardizes how Drumr frontend code shows success, warning, error, and confirmation feedback by selecting the correct API for services, utilities, views, and component handlers.

What is the best way to replace direct antd feedback imports in Drumr frontend code?

The best way to replace direct antd feedback imports is to update your Drumr frontend code so it uses getApp() or App.useApp() for user feedback. This removes direct antd message, modal, or notification usage and manual bootstrap code.