xinetzone/SpecWeave / .agents/skills/iga-pages
iga-pages
VerifiedDeploy frontend and full-stack projects to IGA Pages. Use when the user mentions IGA Pages or requests deployment ("deploy my app", "publish this site", "push this live", "deploy and give me the link", "create a preview deployment", "deploy to IGA Pages", "ship to production"), or wants to develop an API ("write an API", "create an endpoint", "build a backend service").
IGA Pages Skill
Two areas: CLI (iga tool for auth, link, dev, build, deploy) and Project development (functions, API routes).
Run iga <command> -h for full flag details.
Critical: CLI Version
The @iga-pages/cli version must be >= 1.0.5. Check with iga --version; if it's older (or not installed), upgrade before running any other command:
npm i -g @iga-pages/cli@latest
Critical: Framework Compatibility
Supported frameworks: Next.js, Vite, Vue CLI, Create React App, Angular, Hexo, Docusaurus, VitePress, VuePress, Hugo. Frameworks not in this list (e.g. Nuxt, Remix, Astro) are unsupported — proactively inform the user before proceeding.
Pure static assets (plain HTML/JS/CSS) can also be deployed — the project root is used as the output directory by default.
Critical: Login Authentication
Before any deploy or link command, authenticate with iga login. The login method depends on the environment:
-
Local IDE (VS Code, TRAE desktop, etc.) → browser login:
iga login
Wait for the user to complete browser auth. The CLI prints a success message when done.
- Remote / headless environment (SSH, Cowork, CI/CD, cloud dev container, etc.) → AK/SK login:
Browser-based login is unavailable in headless environments; AK/SK is the only option. Obtain AK/SK from the Volcengine IAM console.iga login --accessKey <YOUR_AK> --secretKey <YOUR_SK>
To determine the environment: if the session has no display or browser access (e.g., $SSH_CONNECTION is set, running inside a container, or the user mentions they are on a remote machine), default to AK/SK login. Otherwise, prefer browser for its simplicity.
Critical: Working Directory
All iga commands must run inside the project root. Scaffolding tools (create-next-app, npm create vite, hugo new site, etc.) create a subdirectory — you must cd into it before any iga command:
npx create-next-app@latest my-app --yes
cd my-app && iga pages deploy --name my-app
Quick Reference
npm i -g @iga-pages/cli
iga login # local IDE: opens browser
iga login --accessKey <AK> --secretKey <SK> # remote/headless: AK/SK login
## new project
iga pages deploy --name <my-app> # deploy (auto-creates project on first run)
## project already linked
iga pages deploy
iga pages link # link to existing project without deploying
iga pages dev # local dev server (REQUIRED when api/ exists — serves framework + /api/* together)
iga pages build # build for production
- deploy auto-detects GitHub remote → Git deploy; otherwise → upload deploy. Only GitHub is supported for Git integration.
- If deploy output includes a preview URL with
?iga_token=...&iga_time=..., share that full URL (query included); omitting it can break access.
Anti-Patterns
CLI
- Running
igacommands outside the project directory → alwayscdinto the scaffolded subdirectory first - Deploy without login → always
iga loginfirst - Committing
.iga/→ it's auto-gitignored, don't remove the entry provider: "upload_v2"with GitHub remote → delete.iga/project.jsonand redeploy to switch to Git deploy- Starting local dev with
npm run dev/vite/next dev/npm startwhenapi/exists → useiga pages devso serverless functions are served - Setting
package.json"scripts.dev"toiga pages dev→ infinite loop, sinceiga pages devitself invokes thedevscript frompackage.json. Keep"scripts.dev"as the framework's own dev command (e.g.next dev,vite)
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |