gmira-detail

Standardize product detail page architecture with strict content modeling and semantic layout patterns.

Updated Jul 25, 2026
One-click install
npx skills add https://github.com/OthmanAdi/gmira --skill gmira-detail
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gmira-detail
Source: https://github.com/OthmanAdi/gmira/tree/main/skills/gmira-detail
Command: npx skills add https://github.com/OthmanAdi/gmira --skill gmira-detail

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill addresses the common failure of product detail pages (PDPs) that prioritize generic layouts over structured, verifiable content, leading to poor decision-making for users.

Core Features & Use Cases

  • Content Modeling: Replaces vague sections like Features with specific, database-backed fields for vehicles, courses, or products.
  • Technical Data Handling: Implements accessible, scannable spec tables with tabular-nums and proper semantic markup.
  • State Management: Provides robust patterns for handling unavailable variants, sticky buy rails, and URL-based configuration state.
  • Use Case: Use this when building a vehicle listing or course page to ensure all technical specs, trust signals, and purchase actions are verifiable and accessible.

Quick Start

Use the gmira-detail skill to audit the current product detail page and refactor the spec table into a semantic table with tabular-nums.

Frequently Asked Questions about gmira-detail

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

FAQPage Schema
How do I structure a React product detail page for high conversion and accessibility?

Structure a React product detail page by enforcing strict content modeling with database-backed fields, semantic spec tables using tabular-nums, and verifiable trust signals to ensure user decision clarity. This approach replaces vague layouts with standardized architecture.

What is the best way to handle URL-based state synchronization for product variants in Next.js?

The best way to handle URL-based state synchronization for product variants is implementing robust patterns for unavailable variants, sticky buy rails, and URL-based configuration state. This ensures accessible markup and reliable state management on high-stakes listing pages.

How do I build an accessible spec table for technical product data in Next.js?

Build an accessible spec table by using proper semantic markup and applying tabular-nums for scannable technical data handling. This standardizes spec tables for vehicles, courses, or physical goods, ensuring data remains verifiable and accessible.

When do I need strict content modeling for a product detail page?

You need strict content modeling for a product detail page when building high-stakes listings like vehicles or courses where user trust is paramount. It replaces vague sections such as generic features with specific, database-backed fields to improve decision-making.

How do I manage a sticky buy rail and unavailable variants in a React PDP?

Manage a sticky buy rail and unavailable variants by applying robust state management patterns that synchronize URL-based configuration state. This handles variant availability directly within the semantic layout, ensuring purchase actions remain verifiable.

Does this product detail page architecture work for physical goods and course listings?

Yes, this product detail page architecture works for physical goods and course listings by applying standardized semantic layout patterns. It enforces verifiable trust content, accessible markup, and technical spec modeling specifically for vehicles, courses, and physical products.