docs-ia

Define URL structure, navigation patterns, and page layouts for MC-ORG.

Updated Jun 26, 2022
One-click install
npx skills add https://github.com/evengul/mc-org --skill docs-ia
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: docs-ia
Source: https://github.com/evengul/mc-org/tree/main/.claude/skills/docs-ia
Command: npx skills add https://github.com/evengul/mc-org --skill docs-ia

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides the definitive Information Architecture (IA) for the MC-ORG application, ensuring a consistent and user-friendly experience across all features and platforms.

Core Features & Use Cases

  • Definitive IA Specification: Acts as the single source of truth for product and UX decisions.
  • URL Structure Definition: Outlines the complete URL hierarchy for navigation.
  • Navigation & UI Patterns: Details mobile and desktop chrome, breadcrumbs, and the plan/execute toggle.
  • Page-Specific Layouts: Describes the content and structure for Project List, Project Detail, Production Path, Roadmap, and Idea Hub pages.
  • User Persona Guidance: Defines how different user types interact with the application.
  • Build Phase Roadmapping: Outlines feature development across phases.

Quick Start

Load this skill when evaluating feature scope, URL structure, navigation behavior, or user personas for MC-ORG.

Frequently Asked Questions about docs-ia

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

FAQPage Schema
How do I define information architecture for a product application?

Information architecture for a product application defines the complete URL structure, navigation patterns, and page layouts. It establishes core principles for feature design and progressive disclosure to ensure a consistent user experience.

What is the best way to structure navigation and page layouts for user personas?

Structuring navigation and page layouts for user personas involves detailing mobile and desktop chrome, breadcrumbs, and specific page content. It defines how different user types interact with the application across distinct features.

How do I create a build phase roadmap for feature development?

Creating a build phase roadmap for feature development outlines progressive feature releases across distinct phases. It acts as a single source of truth for product decisions, ensuring consistent scope evaluation and phased delivery.

Does this information architecture specification support both mobile and desktop navigation patterns?

Yes, this information architecture specification supports both mobile and desktop navigation patterns. It explicitly details the mobile and desktop chrome, breadcrumbs, and the plan/execute toggle for consistent cross-platform interactions.

When do I need progressive disclosure in product design?

Progressive disclosure in product design is needed when managing complex feature interactions across multiple user personas. It is a core principle of this information architecture, ensuring a user-friendly experience by revealing information contextually.