frontend-helpers

Standardize Drumr frontend helper usage for navigation, toolbars, and queries.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Using frontend helper APIs incorrectly can break navigation, toolbar behavior, data extraction, and workflow interactions; this Skill provides the canonical Drumr patterns so implementation stays consistent, safe, and discoverable.

Core Features & Use Cases

  • Navigation helpers for opening and closing views, building breadcrumbs, and working with view container context.
  • Toolbar DSL support for CRUD actions, dropdown menus, row toolbars, and reusable header composition.
  • Utility coverage for UI object extraction, context access, authenticated requests, query builder operations, workflow registry management, and metadata-driven rendering.
  • Common use cases include modal view flows, view header toolbars, plain-value extraction from UI objects, paginated data queries, and branching logic based on model or action metadata.

Quick Start

Ask the AI to implement a Drumr frontend helper pattern for a specific view, toolbar, or query flow using only the public exports listed in this Skill.

Frequently Asked Questions about frontend-helpers

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

FAQPage Schema
How do I use frontend helpers for navigation and toolbar actions without breaking view behavior?

Frontend helpers for navigation and toolbars are applied by using canonical patterns for opening views, building breadcrumbs, and composing CRUD actions to keep UI behavior consistent and safe.

What is the correct way to extract plain values from UI objects in a frontend workflow?

Extracting plain values from UI objects requires using standard utility helpers that separate data modes from UI modes, ensuring safe data-to-UI conversion and metadata-driven rendering.

How do I build paginated data queries using frontend query builders?

Building paginated data queries involves applying the standard query builder operations to enforce pagination for list queries, preventing performance issues and incorrect data extraction.

Can I use internal non-exported framework helpers for custom modal view flows?

Internal non-exported framework helpers must be avoided when implementing modal view flows; only public exported APIs should be used to maintain safe and discoverable frontend integration.

When do I need metadata-driven rendering and context access in frontend views?

Metadata-driven rendering and context access are needed when branching logic based on model or action metadata, requiring standard utility coverage to access view container context safely.

Does the frontend workflow registry support branching logic based on action metadata?

Yes, the workflow registry supports branching logic based on action metadata by applying standard workflow registry management to control interactions and metadata lookups correctly.