aicade galaxy create app skill

Build general aicade application prompts by taking the user's base prompt plus the platform additions from the bundled 3.1 workflow reference, then assemblin...

Security Scan

The skill's files, runtime instructions, and minimal requirements are consistent with its stated purpose (building an aicade app prompt); it only needs Node and reads a local spec to produce a prompt.

Purpose & Capability

Name, description, and included files (prompt builder script, templates, and references) align with a tool that assembles an aicade-ready prompt. Required binary is only 'node' and no unrelated credentials or services are requested.

Instruction Scope

SKILL.md restricts behavior to collecting user prompt inputs, reading bundled reference files, and running the local Node script to output a combined prompt. One caution: the script reads the JSON file path supplied via --spec (resolved from process.cwd()), so if a user points it at a sensitive local file the script will parse and include its contents — this is expected for a prompt builder but worth noting as a potential data-exposure risk if mishandled.

Install Mechanism

Instruction-only skill with no install spec; it includes a local Node script and assets. No external downloads or arbitrary install steps are present.

Credentials

The skill declares no required environment variables or credentials. The docs reference AICADE_API_KEY / AICADE_API_SECRET_KEY / AICADE_API_APP_NO as platform-specific variables the user would obtain separately, but the skill does not require or request them to run.

Persistence & Privilege

always is false and disable-model-invocation is true (no autonomous model calls). The skill does not modify other skills or system-wide settings and does not request permanent presence or elevated privileges.

Assessment

This skill appears to do what it says: it runs a local Node script that reads a user-supplied JSON spec and prints an assembled prompt. Before using it: (1) ensure you run the script locally (it reads files relative to your working directory) and only pass a spec file you intend to share; do not point --spec at secrets or system files. (2) The README mentions AICADE_* env vars as platform credentials — only obtain and provide those from the official platform if you need to integrate with Aicade. (3) No network calls or uploads are present in the included files, but treat generated prompts as potentially sensitive if you paste them into external services. (4) Verify Node is from a trusted source on your machine and inspect the included script if you have any additional security concerns.

READ BEFORE INSTALL This skill follows the bundled prompt workflow reference exactly:

1. Collect the user's base business prompt
2. Add the aicade platform integration requirements from section 3.1
3. Assemble one final integrated prompt like section 3.2 READ BEFORE INSTALL

aicade-app-builder

Use this skill when you want to generate a final AI prompt for an aicade app and you want the result to match the bundled documented workflow.

Core Principle

This skill does not invent a new requirement structure.

It uses:

• 3.1 as the required input model
• 3.2 as the target output style

That means:

• the user provides a base business prompt
• the user provides or accepts the aicade platform additions
• the skill assembles the final integrated prompt

Quick Start

node {baseDir}/scripts/build-aicade-prompt.mjs \
  --spec {baseDir}/assets/app-spec.template.json \
  --lang zh-TW

Recommended Workflow

1. Confirm Platform Access First

Before collecting the final prompt inputs, first ask the user whether they have already applied for app access on:

• https://www.aicadegalaxy.com/

If the user has already applied and has app access, continue the workflow.

If the user has not applied yet, do not continue directly to environment variables or app integration. Point them to:

• https://docs.aicadegalaxy.com/white-paper/application-document

Explain briefly that only after obtaining app access can they get the three AICADE environment variables required for integration:

• AICADE_API_KEY
• AICADE_API_SECRET_KEY
• AICADE_API_APP_NO

2. Read Before Prompt Assembly

Read the bundled references first:

• references/sdk-capabilities.md
• references/prompt-workflow.md

3. Prepare Input In The 3.1 Shape

The user input should contain two parts:

1. Base business prompt
2. Platform integration additions

The platform additions should cover the same kind of information highlighted in 3.1, such as:

• SDK invocation requirements
• local storage replacement strategy
• wallet address display
• account and balance display
• ticket or payment access flow
• score, points, token, AI chat, NFT, or market-related capabilities when needed

Common SDK Capabilities

The platform can expose multiple SDK modules. Choose only the ones your app actually needs:

• Application: app metadata and lifecycle
• Ticket: access gate, subscription, or play/payment flow
• AppScore: score and leaderboard
• AicadeCurrency: point or platform currency operations
• AIChat: AI chat session and messages
• AICoinMarket: market assistant and streaming messages
• Token: token balance and swap flow
• NftOwner: NFT ownership and avatar
• LocalStorageTools: app-scoped storage instead of browser localStorage

4. Generate The Final Prompt

Run:

node {baseDir}/scripts/build-aicade-prompt.mjs --spec /path/to/spec.json --lang zh-TW

The script will output one final prompt that:

• keeps the user's base business prompt structure
• appends the aicade platform integration block
• keeps technical requirements and output requirements
• reads like the final integrated prompt shown in 3.2

5. Use The Prompt In Your IDE

Paste the generated prompt into Cursor, VS Code, or another AI IDE assistant.

6. Review Generated Code

Check these items before running the app:

• SDK initialization order is correct
• No unsupported SDK methods are called
• LocalStorageTools replaces localStorage
• Wallet address, balance, score, token, chat, or NFT UI is shown only when the selected SDK capabilities require it
• Exchange rules are enforced only when the app explicitly enables exchange-related capabilities
• Error handling exists around async SDK calls

7. Build And Upload

npm install
npm run dev
npm run upload

Script Input Spec

The prompt builder accepts a JSON file like this:

{
  "roleSetup": "你是一位資深全端產品開發工程師",
  "projectName": "AI 活動助手",
  "projectGoal": "開發一個用於活動報名、簽到和積分兌換的 aicade 應用",
  "basePromptSections": [
    {
      "title": "基礎業務需求",
      "items": [
        "這裡填寫你原本準備給 AI 的基礎業務 Prompt"
      ]
    }
  ],
  "platformIntegration": {
    "docPath": "references/sdk-capabilities.md",
    "createDocPath": "references/prompt-workflow.md",
    "sdkAlreadyIntegrated": true,
    "sdkCapabilities": [
      "Application",
      "LocalStorageTools"
    ],
    "replaceLocalStorageWith": "LocalStorageTools",
    "showWalletAddress": true,
    "showPointBalance": false,
    "pointBalanceLabel": "積分",
    "exchange": {
      "enabled": false,
      "ratio": "100:1",
      "dailyLimit": "100 個 Aicade Point",
      "trigger": "每次業務結算時"
    }
  },
  "technicalRequirements": [
    "基於目前專案環境生成"
  ],
  "outputRequirements": [
    "輸出完整可執行程式碼"
  ]
}

Use:

• {baseDir}/assets/app-spec.template.json for the minimal 3.1-style input
• {baseDir}/assets/app-spec.example.json for a fuller example

Files Included

• scripts/build-aicade-prompt.mjs
• assets/app-spec.template.json
• assets/app-spec.example.json
• references/sdk-capabilities.md
• references/prompt-workflow.md

Security And Permissions

This skill:

• runs a local Node.js script
• reads a local JSON spec file
• prints a generated prompt to stdout

This skill does not:

• modify source code automatically
• upload anything by itself
• invoke the model autonomously

Notes

• The input model is based on 3.1
• The output format is intentionally shaped like 3.2
• Ask about platform app access before discussing env vars
• If the docs change, update this skill accordingly