Search: "router"

Builds with and operates Pi, the minimal terminal coding harness. Use for installing Pi, configuring providers/models/settings/environment variables, creating Pi skills/extensions/packages/themes/prompt templates, embedding Pi through the SDK, integrating over RPC or JSON event streams, parsing sessions, running local models through the llama.cpp router, developing custom Pi providers and TUI components, or using ecosystem packages such as pi-subagents (delegation/orchestration), pi-mcp-adapter (MCP servers), pi-interview (interactive forms), and pi-web-access (web search, fetching, video understanding).

Entry point and router for every Expo or EAS task. Load this skill first — before writing code and before choosing another expo-* / eas-* skill — when the request, PRD, or spec mentions Expo, EAS, Expo Go, or an expo-* package, or the project has an `expo` dependency in `package.json`. Within that gate it also covers app specs and designs to implement (tabs, stacks, maps, lists, navigation, building from a screenshot), and phrasings like 'implement a mobile app', 'make my app look native', 'add navigation', 'fetch some data', 'upgrade my SDK', 'add Expo to my existing native app', 'ship to the App Store', or 'I'm new to Expo, where do I start'. A fully specified request (SDK pinned, libraries named, layout given) still routes through here — the shared setup rules still apply. Do NOT load it when neither signal is present: a bare React Native project with no `expo` dependency is not Expo work. Detects the real goal, routes to the right expo-* / eas-* skill, and owns the shared setup rules.

Build beautiful, native-feeling Expo screens. Covers Apple HIG styling, semantic colors, native controls, SF Symbols, media, visual effects, gradients, storage, and responsive layout. For routing and navigation, use the expo-router skill; for motion and animation, use the expo-animation skill.

Navigation and routing for Expo Router. Covers file-based routes, groups and dynamic routes, folder organization, Link with previews and context menus, native Stack, page titles, modals and form sheets, NativeTabs, headers and toolbars, and header search bars.

External-model router for Codex with guided Kimi OAuth/API, DeepSeek, safe migration, and rollback.

Local-first AI model routing for serious agents. One endpoint. Any provider. The router figures out the rest.

Operating procedure for Adako, the MCP server and REST API that connects this assistant to the user's Google Ads, Meta Ads, LinkedIn Ads and ChatGPT Ads accounts (TikTok Ads tools are listed but not available yet). Use it whenever the user asks about ad spend, performance, campaigns, ad sets, ad groups, keywords, search terms, audiences, budgets, pixels, creatives, monitors or briefs on those platforms, and whenever they ask to create, pause, resume, re-budget or otherwise change anything in those accounts. It defines the safety contract (read before write, every write becomes a proposal the user approves, created objects are always paused), the tool-call contract (233 tools, read routers for lookups and _write routers for changes, ids are strings, budgets are decimals in the account currency, dates are YYYY-MM-DD or a preset), the tool map per platform, and the standard workflows for performance reviews, wasted-spend cleanup, campaign launches, monitors, approvals and error recovery. Do not use it for platforms Adako does not cover.

Operating procedure for Adako, the MCP server and REST API that connects this assistant to the user's Google Ads, Meta Ads, LinkedIn Ads and ChatGPT Ads accounts (TikTok Ads tools are listed but not available yet). Use it whenever the user asks about ad spend, performance, campaigns, ad sets, ad groups, keywords, search terms, audiences, budgets, pixels, creatives, monitors or briefs on those platforms, and whenever they ask to create, pause, resume, re-budget or otherwise change anything in those accounts. It defines the safety contract (read before write, every write becomes a proposal the user approves, created objects are always paused), the tool-call contract (233 tools, read routers for lookups and _write routers for changes, ids are strings, budgets are decimals in the account currency, dates are YYYY-MM-DD or a preset), the tool map per platform, and the standard workflows for performance reviews, wasted-spend cleanup, campaign launches, monitors, approvals and error recovery. Do not use it for platforms Adako does not cover.

Operating procedure for Adako, the MCP server and REST API that connects this assistant to the user's Google Ads, Meta Ads, LinkedIn Ads and ChatGPT Ads accounts (TikTok Ads tools are listed but not available yet). Use it whenever the user asks about ad spend, performance, campaigns, ad sets, ad groups, keywords, search terms, audiences, budgets, pixels, creatives, monitors or briefs on those platforms, and whenever they ask to create, pause, resume, re-budget or otherwise change anything in those accounts. It defines the safety contract (read before write, every write becomes a proposal the user approves, created objects are always paused), the tool-call contract (233 tools, read routers for lookups and _write routers for changes, ids are strings, budgets are decimals in the account currency, dates are YYYY-MM-DD or a preset), the tool map per platform, and the standard workflows for performance reviews, wasted-spend cleanup, campaign launches, monitors, approvals and error recovery. Do not use it for platforms Adako does not cover.