despia-legacy/extension-skill

despia-v3-extensions

Write a Despia V3 Extension, native Swift (iOS) and Kotlin or Java (Android) code that a Despia V3 web-view app calls with extension:// / .

소스 보기

사용 방법

  1. 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
  2. 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
  3. 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/despia-legacy/extension-skill --skill despia-v3-extensions

시작 전 확인

  • 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
  • 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 Skill 문서

원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.

Despia V3 Extensions

For the Despia V3 runtime only, and experimental. You write native files, describe them in a JSON manifest, and serve them from the web app. Despia approves the files and compiles them into a new native build. The page then calls extension://<name>/<route>?<params>. All facts are in references/; read the file for the step you are on. Never invent manifest fields, types, hooks or error codes. If a fact is not in the references, say so and point to https://docs.despia.com/experiments/v3-extensions .

Workflow

  1. Confirm the app is on Despia V3 and the capability is not already a Despia feature. Read references/limits.md and tell the user the platform limits that apply.
  2. Lay out public/despia/extensions.json and public/despia/<name>/manifest.json with ios/ and android/ beside it (references/manifest.md). The folder name is the extension id and matches [a-z][a-z0-9]{1,23}.
  3. Declare each route, its typed parameters (string, int, bool, enum, https_url), its output variable and callback, and any events (references/manifest.md, references/routes-and-answers.md).
  4. Write the iOS handler (references/ios.md) and the Android handler (references/android.md). Answer every call once, with data or an error code and message.
  5. Declare native work as typed or custom (references/manifest.md). Dependencies must be pinned files in the approval; nothing is downloaded at build time.
  6. Write the web call and its answer handling (references/routes-and-answers.md).
  7. Copy the pattern from examples/recorder/ (the Background Recorder sample, notes in references/recorder-sample.md) when a complete template helps.
  8. Tell the user the approval flow: Despia approves extensions.json and every referenced file, each manifest.json included. Any change needs a new approval and a new native build, never over-the-air. Extensions are enabled per app by Despia. The user owns and maintains the native code; Despia does not support customised code.

Rules

  • Never set what the build owns (bundle id, versions, signing, URL types, App Transport Security, purpose strings and permissions set in Despia, push and associated-domain entitlements). See references/manifest.md.
  • Every file must be named in its manifest.json; hidden files are refused; keep large data native and pass identifiers through the bridge.
  • Do not claim V4 support. First-party V4 support comes through the new package registry.

Docs: https://docs.despia.com/experiments/v3-extensions and https://docs.despia.com/experiments/samples/recorder