architect

Generate platform-agnostic feature specifications with API mapping and UI wireframes.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/XiriGo/ecommerce-mobile --skill architect-xirigo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architect
Source: https://github.com/XiriGo/ecommerce-mobile/tree/main/.claude/skills/architect
Command: npx skills add https://github.com/XiriGo/ecommerce-mobile --skill architect-xirigo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the design and specification process for new mobile app features, ensuring platform consistency and detailed documentation.

Core Features & Use Cases

  • Platform-Agnostic Design: Creates feature specifications that apply equally to Android and iOS.
  • Comprehensive Documentation: Generates detailed specs covering API mapping, data models, UI components, navigation, and error handling.
  • Design System Integration: Ensures adherence to existing design tokens and component libraries.
  • Use Case: When a new feature like "user profile editing" is planned, this Skill will produce a complete blueprint for developers on both platforms, including all necessary UI elements, data structures, and API interactions, based on the project's design system.

Quick Start

Use the architect skill to design a new feature specification for 'user profile editing'.

Frequently Asked Questions about architect

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

FAQPage Schema
How do I create platform-agnostic feature specifications for a mobile app?

To create platform-agnostic feature specifications, you define shared UI components, data models, and API mappings that apply equally to Android and iOS without relying on platform-specific code. This ensures architectural consistency across both mobile platforms.

What is included in comprehensive mobile feature documentation for developers?

Comprehensive mobile feature documentation includes API mapping, data models, UI wireframes, component inventories, navigation flows, and error handling. This provides developers with a complete architectural blueprint for consistent implementation.

How do I integrate existing design systems into new mobile feature designs?

Integrating existing design systems into new mobile feature designs involves adhering to established design tokens and component libraries during the specification process. This ensures generated UI components match the current visual language and technical constraints.

Does this approach work for both Android and iOS mobile development?

Yes, this approach works for both Android and iOS mobile development by generating a single feature specification that maps shared data structures and UI components across both platforms. It guarantees consistency without requiring duplicate design effort.

Can I use this to map API contracts to mobile UI wireframes automatically?

Yes, you can map API contracts to mobile UI wireframes by generating feature specifications that connect API interactions directly with component inventories and data models. This aligns backend endpoints with frontend UI requirements.

What is the best way to document error handling in mobile feature specifications?

The best way to document error handling in mobile feature specifications is to include it within the comprehensive design blueprint alongside API mapping and navigation flows. This ensures developers anticipate edge cases during implementation.