Run any Skill in Manus with one click

granite-routing

Stars0

Forks0

UpdatedMarch 28, 2026 at 01:51

Use when you are changing Granite route paths, page entries, params, or navigation flow in the MiniApp frontend. Do not use for capability lookup, provider runtime work, or TDS component selection.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

jingjing2222

jingjing2222/create-rn-miniapp

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

File Explorer

4 files

SKILL.md

readonly

name	granite-routing
description	Use when you are changing Granite route paths, page entries, params, or navigation flow in the MiniApp frontend. Do not use for capability lookup, provider runtime work, or TDS component selection.
compatibility	Intended for create-rn-miniapp repositories. Assumes the generated frontend workspace, Granite router conventions, and docs under docs/engineering/*.
metadata	{"create-rn-miniapp.agentsLabel":"route / page / navigation 패턴","create-rn-miniapp.category":"core","create-rn-miniapp.order":"2"}

Granite Routing Skill

이 Skill은 frontend의 route, page entry, navigation 흐름을 설계하거나 수정할 때 사용합니다.

Use when

route path, page file, params 설계를 결정할 때
createRoute, validateParams, navigation usage 예시가 필요할 때
entry layer와 implementation layer를 어떻게 나눌지 정할 때

Do not use for

MiniApp/AppInToss capability / 공식 API 탐색: docs-search 또는 공식 문서
TDS component 선택과 UI boundary: tds-ui
tRPC contract/app-router 변경 순서: trpc-boundary

읽는 순서

references/patterns.md에서 route/page/navigation 패턴을 확인한다.
강제 규칙과 금지 import는 references/frontend-policy.md를 기준으로 본다.
기능 존재 여부와 공식 API lookup은 docs-search 또는 Granite/AppInToss 공식 문서로 확인하고, UI 선택은 tds-ui로 넘긴다.

핵심 원칙

규칙 요약은 references/frontend-policy.md가 소유한다.
이 Skill은 구현 패턴과 예시를 제공하고, 규칙의 근거 문서를 대체하지 않는다.
route 설계 전에는 entry file, impl file, params 흐름, router.gen.ts 동기화까지 같이 본다.

More from this repository

same repository

tds-ui

jingjing2222/create-rn-miniapp

Decision skill for choosing TDS React Native components and UI boundaries in MiniApp screens. Use when translating product requirements into TDS components, reconciling public docs with actual exports, or deciding controlled/uncontrolled state patterns. Do not use for route design, capability lookup, provider/runtime work, or non-TDS native module decisions.

2026-04-090

backoffice-react

jingjing2222/create-rn-miniapp

Decide how to structure an optional backoffice React screen: pick list, detail, form, dashboard, or bulk-action archetypes; place query, component, and form state; split search, table, confirm, and export boundaries; and validate loading, error, empty, disabled, and permission states. Do not use for MiniApp route design, server-provider diagnosis, or shared contract changes.

2026-03-280

cloudflare-worker

jingjing2222/create-rn-miniapp

Diagnose a Cloudflare Worker-backed server workspace: classify runtime, binding, env, local dev, and client-linkage drift; check D1/R2 and base URL alignment; and separate local diagnosis from remote-state or shared-boundary work. Do not use for deploy-only repair or generic UI work.

2026-03-280

firebase-functions

jingjing2222/create-rn-miniapp

Diagnose a Firebase-backed server workspace: choose callable, HTTP, or trigger surfaces; check project, region, emulator, and client-linkage drift; and distinguish local linkage from remote readiness or shared-boundary work. Do not use for deploy, seed, or repair procedures.

2026-03-280

supabase-project

jingjing2222/create-rn-miniapp

Diagnose a Supabase-backed server workspace: separate DB, RLS, Edge Function, env, and project-ref drift; check frontend and backoffice alignment; and distinguish local linkage from remote project state or shared-boundary work. Do not use for remote db apply/deploy or generic route/UI work.

2026-03-280

trpc-boundary

jingjing2222/create-rn-miniapp

Use when you are changing tRPC contracts, app-router shape, or client and server import order across the shared boundary. Do not use for provider runtime layout, remote operations, or generic route and UI work.

2026-03-280

name	granite-routing
description	Use when you are changing Granite route paths, page entries, params, or navigation flow in the MiniApp frontend. Do not use for capability lookup, provider runtime work, or TDS component selection.
compatibility	Intended for create-rn-miniapp repositories. Assumes the generated frontend workspace, Granite router conventions, and docs under docs/engineering/*.
metadata	{"create-rn-miniapp.agentsLabel":"route / page / navigation 패턴","create-rn-miniapp.category":"core","create-rn-miniapp.order":"2"}

Granite Routing Skill

이 Skill은 frontend의 route, page entry, navigation 흐름을 설계하거나 수정할 때 사용합니다.

Use when

route path, page file, params 설계를 결정할 때
createRoute, validateParams, navigation usage 예시가 필요할 때
entry layer와 implementation layer를 어떻게 나눌지 정할 때

Do not use for

MiniApp/AppInToss capability / 공식 API 탐색: docs-search 또는 공식 문서
TDS component 선택과 UI boundary: tds-ui
tRPC contract/app-router 변경 순서: trpc-boundary

읽는 순서

references/patterns.md에서 route/page/navigation 패턴을 확인한다.
강제 규칙과 금지 import는 references/frontend-policy.md를 기준으로 본다.
기능 존재 여부와 공식 API lookup은 docs-search 또는 Granite/AppInToss 공식 문서로 확인하고, UI 선택은 tds-ui로 넘긴다.

핵심 원칙

규칙 요약은 references/frontend-policy.md가 소유한다.
이 Skill은 구현 패턴과 예시를 제공하고, 규칙의 근거 문서를 대체하지 않는다.
route 설계 전에는 entry file, impl file, params 흐름, router.gen.ts 동기화까지 같이 본다.