app-pages

Standardize top-level app views with a shared page blueprint and AppView routing.

2|Updated Jan 29, 2026
One-click install
npx skills add https://github.com/Clay-Ferguson/mkbrowser --skill app-pages
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: app-pages
Source: https://github.com/Clay-Ferguson/mkbrowser/tree/main/.claude/skills/pages
Command: npx skills add https://github.com/Clay-Ferguson/mkbrowser --skill app-pages

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Managing multiple top-level pages across an app often leads to inconsistent component patterns and navigation behavior. A shared page blueprint ensures uniform structure, predictable routing, and easier collaboration for developers.

Core Features & Use Cases

  • Reusable page pattern for top-level views (browser, search-results, settings) with a single source of truth for AppView-to-page mapping.
  • Clear guidelines for naming, routing, and tab integration.
  • Use case: onboarding a new feature page by following the pattern and wiring it to AppView.

Quick Start

Create a new page following the app-pages pattern, add a tab button in the top panel, and wire the page to the AppView type in src/store/types.ts.

Frequently Asked Questions about app-pages

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

FAQPage Schema
How do I standardize top-level views and routing in a React single-page application?

Standardize top-level views in a React single-page application by applying a reusable page blueprint that ensures consistent component structure, predictable AppView routing, and centralized navigation mapping across browser, search-results, and settings pages.

What is the best way to add a new feature page to an existing AppView routing setup?

The best way to add a new feature page is to follow the page component blueprint, wire the new page to the AppView type in the store, and add a corresponding tab button in the top navigation panel for consistent routing.

How does AppView mapping work for managing navigation across multiple application pages?

AppView mapping works by providing a single source of truth in the store that links top-level views to their corresponding page components, ensuring navigation remains predictable and consistent across the single-page application.

Can I integrate state management and tabs when standardizing application pages?

Yes, you can integrate state management and tabs by wiring page components to the store types and adding tab buttons in the top panel, ensuring new pages extend AppView routing without breaking existing navigation structures.

Do I need TypeScript to use this application page standardization pattern?

TypeScript is used to define the AppView routing types and store mappings, ensuring type-safe integration when onboarding new feature pages and extending the application's top-level navigation structure.

Why do my React application pages have inconsistent component patterns and navigation behavior?

Inconsistent component patterns and navigation behavior occur when multiple top-level pages lack a shared blueprint, which this pattern solves by enforcing uniform structure, predictable routing, and a single source of truth for AppView mapping.