skills.rest
jarrodmedrano
jarrodmedranoCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

solito

Consolidate Solito navigation guidance for Expo and Next.js monorepo projects.

2|Updated Jan 11, 2026
Search Tags:#routing#next.js#navigation#cross-platform#monorepo#expo#solito
One-click install
npx skills add https://github.com/jarrodmedrano/jarrod-claude-skills --skill solito
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: solito
Source: https://github.com/jarrodmedrano/jarrod-claude-skills/tree/main/.claude/skills/solito
Command: npx skills add https://github.com/jarrodmedrano/jarrod-claude-skills --skill solito

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides guidance and best practices for building cross-platform Solito apps (Expo + Next.js) with a single, shared codebase. It helps teams structure navigation, routing, and shared UI components to work seamlessly on web and native, reducing duplication and platform-specific bugs.

Core Features & Use Cases

  • Cross-platform navigation patterns: unified Link and router usage that works on both web and native.
  • Monorepo-friendly architecture: guidance for organizing apps/, packages/, and shared UI in a single repo.
  • Pitfall avoidance: patterns to prevent common navigation and platform issues, with examples.
  • Use Case: start with a shared navigation module and then extend to screens and dynamic routes across Expo and Next.js.

Quick Start

Describe your Solito project and request a cross-platform navigation blueprint, e.g., "Create a Solito navigation blueprint for an Expo + Next.js app with a shared app package and dynamic user screens."

Frequently Asked Questions about solito

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

FAQPage Schema
How do I set up unified cross-platform navigation between Expo and Next.js?▼

To set up unified cross-platform navigation between Expo and Next.js, use Solito's shared APIs like `solito/link` and `solito/router` to manage routing across web and native environments within a monorepo.

What is the best way to structure a Solito monorepo for shared UI components?▼

The best way to structure a Solito monorepo for shared UI components is to organize your project into dedicated `apps/` and `packages/` directories, ensuring a scalable shared codebase for both Expo and Next.js platforms.

Can I use Solito for dynamic routing across web and native platforms?▼

Yes, you can use Solito for dynamic routing across web and native platforms. It provides cross-platform navigation patterns that allow you to extend shared modules to screens and dynamic routes in Expo and Next.js.

How do I handle platform-specific code in a Solito universal app?▼

You handle platform-specific code in a Solito universal app by following its cross-platform patterns to prevent common navigation issues, ensuring consistent routing behavior while isolating native or web specific logic.

Why does my Solito navigation break when sharing components between web and native?▼

Solito navigation may break when sharing components if you deviate from its cross-platform APIs. Using standard Next.js or Expo routers instead of `solito/link` and `solito/router` causes platform-specific bugs.

Related Skills

Explore More Software Engineering Skills→
ZeroGravitySkin-RonZeroGravitySkin-Ron

shared-libraries-guidelines

Standardize TypeScript shared types, Zod schemas, and utilities across monorepo packages.

Community
Intermediate
MonumentalSystemsMonumentalSystems
17

cross-platform

Standardize cross-platform mobile development patterns for React Native and Flutter.

Official
Intermediate
tutur3ututur3u
53

vercel-react-native-skills

Codify React Native and Expo performance best practices for mobile apps.

Official
Advanced
Gentleman-ProgrammingGentleman-Programming
618

react-native

Implement React Native patterns with Expo Router, NativeWind, and TypeScript.

Official
Advanced