gmira-brief

Extract factual product requirements and content models for web surface development.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill solves the problem of generic, uninspired web development by forcing the definition of a rigorous product brief before any code is written, preventing the AI from defaulting to repetitive, low-quality design patterns.

Core Features & Use Cases

  • Truth Extraction: Systematically identifies what is factually true versus aspirational, preventing the invention of fake data like prices or customer names.
  • Content Modeling: Forces a detailed breakdown of the content model, including field lists and min/typical/max ranges, which dictates the actual layout.
  • Use Case: Use this when starting a new landing page or feature to ensure the design is grounded in the specific business reality of the project rather than generic template aesthetics.

Quick Start

Run the gmira-brief skill to extract the product truth and generate the initial surface brief for the current page.

Frequently Asked Questions about gmira-brief

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

FAQPage Schema
How do I prevent generic design patterns when building new web surfaces?

To prevent generic design patterns, extract a rigorous product brief before writing any code. This grounds web surface development in specific business reality by defining factual constraints, visitor scenes, and uninventable content models rather than defaulting to template aesthetics.

What is content modeling for web development and when do I need it?

Content modeling for web development is the process of breaking down page content into specific field lists with min, typical, and max ranges. You need it for greenfield projects and redesigns where defining content fields dictates the actual layout and avoids generic design.

How do I extract factual product requirements for a NextJS landing page?

Extract factual product requirements by systematically identifying what is factually true versus aspirational. This truth extraction prevents the invention of fake data like prices or customer names, ensuring your NextJS landing page adheres to actual business constraints.

Can I use this product brief approach for redesigning existing web features?

Yes, you can use this product brief approach for redesigning existing web features. It applies to both greenfield projects and redesigns, ensuring the updated design is grounded in specific business reality and avoids repetitive, low-quality design patterns.

What are uninventable constraints in a product brief?

Uninventable constraints in a product brief are the factual boundaries established during truth extraction that prevent the AI from inventing fake data. They enforce adherence to the gmira doctrine, ensuring web surfaces reflect actual business reality rather than aspirational or generic content.