원클릭으로 Manus에서 모든 스킬 실행

configure-environment

스타2

포크2

업데이트2026년 5월 28일 02:21

Configure or troubleshoot the development environment for this Sailwind Starter project. Delegates to the global "setup-sailwind" skill for full setup, or directs users to the UX Manual if that skill isn't installed. Use this skill when the user says "set up my environment", "configure my environment", "something's not working", "install dependencies", "I'm new — how do I get started", or reports "command not found" errors for node, pnpm, or brew.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

pglevy

pglevy/sailwind-starter

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Configure Environment

This skill handles environment configuration and troubleshooting for the Sailwind Starter project. The heavy lifting lives in the global setup-sailwind skill — this skill's job is to route there or help when things aren't working as expected.

Instructions

Step 1 — Check for the setup-sailwind skill

Look for the setup-sailwind skill in the user's global Kiro skills (typically ~/.kiro/skills/setup-sailwind/SKILL.md).

If the skill is available: activate it and follow its instructions. It covers the full setup flow — Homebrew, Node.js, pnpm, cloning, dependencies, and verification.

If the skill is NOT available: let the user know:

The setup-sailwind skill isn't installed on your machine yet. You can get it (along with the full suite of approved UX skills) from the UX Manual:

https://docs.appian-stratus.io/ux-sites/ux-manual/

There's a script on that site that installs everything in one go. Once installed, come back here and we'll pick up where we left off.

Step 2 — Quick diagnostics (if troubleshooting)

If the user already has things set up but something isn't working, run a quick health check:

echo "=== Environment Health Check ==="
echo "Shell: $SHELL"
which brew && brew --version || echo "❌ Homebrew not found"
which node && node --version || echo "❌ Node.js not found"
which pnpm && pnpm --version || echo "❌ pnpm not found"
echo "---"
ls package.json 2>/dev/null && echo "✓ In a project directory" || echo "❌ Not in a project directory"
ls node_modules/.pnpm 2>/dev/null && echo "✓ Dependencies installed" || echo "❌ Dependencies not installed"

Report findings in plain language and address each issue. Common fixes:

Symptom	Fix
`command not found: brew`	Re-run Homebrew install or add to PATH (`eval "$(/opt/homebrew/bin/brew shellenv)"`)
`command not found: node`	`brew install node`
`command not found: pnpm`	`corepack enable`
Dependencies not installed	`pnpm install`
Port 5173 in use	`lsof -ti:5173 \| xargs kill -9` then `pnpm run dev`
Module not found errors	`rm -rf node_modules && pnpm install`
Garbled terminal in Kiro	Add shell integration (see below)

Step 3 — Kiro shell integration (if needed)

Only if the user reports garbled terminal output in Kiro:

echo '[[ "$TERM_PROGRAM" == "kiro" ]] && . "$(kiro --locate-shell-integration-path zsh)"' >> ~/.zshrc
source ~/.zshrc

Step 4 — Verify

Once issues are resolved, confirm:

pnpm run dev starts without errors
Browser shows the project at http://localhost:5173
No errors in the browser console

Communication Style

The target user is a designer. Use plain language, explain what commands do, and don't assume terminal familiarity.

이 저장소의 다른 Skills

같은 저장소

upgrade-from-template

pglevy/sailwind-starter

Sync an existing Sailwind Starter project with the latest tooling from the template repo. Fetches files directly from GitHub so the skill never goes stale. Use this skill when the user says "upgrade from template", "sync with starter", "update tooling", or "check for template changes".

2026-06-232

security-audit

pglevy/sailwind-starter

Run a security audit on the Sailwind Starter project. Checks for exposed secrets, suspicious packages, misconfigured security settings, and common mistakes designers might not know to look for. Use this skill when the user asks to "check security", "run a security audit", "make sure nothing is exposed", or "check if my API keys are safe".

2026-05-282

connect-to-appian

pglevy/sailwind-starter

Rewrite the prototype's mock data layer (`src/db/`) to use real `fetch` calls against Appian Web API endpoints. Page components remain unchanged — only the function bodies in `src/db/` are replaced. Use this skill when the user says "connect to Appian", "switch to real APIs", "hook up the prototype to the backend", or "replace mock data with real API calls". Prerequisite: run `extract-prototype-contract` first and ensure the Appian app is imported.

2026-05-202

deploy-to-appian

pglevy/sailwind-starter

Deploy a generated Appian app package to a target environment using the Appian Deployment REST API (v2). Handles the full lifecycle: inspect, deploy (with DDL), and poll for results. Use this skill when the user says "deploy to Appian", "push this to my Appian environment", "import the app", or "run the deployment". Prerequisite: run `generate-appian-app` first.

2026-05-202

extract-prototype-contract

pglevy/sailwind-starter

Extract an API contract from the prototype's `src/db/` data layer, producing an `API_Contract` JSON that can be used to generate an importable Appian app package. Use this skill when the user says "extract the API contract", "generate the contract from the prototype", "what's the data model for this prototype?", or "prepare for Appian app generation".

2026-05-202

generate-appian-app

pglevy/sailwind-starter

Generate an importable Appian application package (ZIP) from an `API_Contract` JSON. The package includes record types, web APIs, groups, an application wrapper, DDL, and a manifest — everything needed to stand up the data model in an Appian environment. Use this skill when the user says "generate the Appian app", "create the Appian package", "build the app ZIP", or "hook this up to Appian". Prerequisite: run the `extract-prototype-contract` skill first.

2026-05-202

name	configure-environment
description	Configure or troubleshoot the development environment for this Sailwind Starter project. Delegates to the global "setup-sailwind" skill for full setup, or directs users to the UX Manual if that skill isn't installed. Use this skill when the user says "set up my environment", "configure my environment", "something's not working", "install dependencies", "I'm new — how do I get started", or reports "command not found" errors for node, pnpm, or brew.
metadata	{"title":"Configure Environment","prompt":"Help me configure my environment: ","human-reviewer":"Philip Levy","last-reviewed":"2026-05-27T00:00:00.000Z"}

Configure Environment

Instructions

Step 1 — Check for the setup-sailwind skill

Look for the setup-sailwind skill in the user's global Kiro skills (typically ~/.kiro/skills/setup-sailwind/SKILL.md).

If the skill is available: activate it and follow its instructions. It covers the full setup flow — Homebrew, Node.js, pnpm, cloning, dependencies, and verification.

If the skill is NOT available: let the user know:

The setup-sailwind skill isn't installed on your machine yet. You can get it (along with the full suite of approved UX skills) from the UX Manual:

https://docs.appian-stratus.io/ux-sites/ux-manual/

There's a script on that site that installs everything in one go. Once installed, come back here and we'll pick up where we left off.

Step 2 — Quick diagnostics (if troubleshooting)

If the user already has things set up but something isn't working, run a quick health check:

echo "=== Environment Health Check ==="
echo "Shell: $SHELL"
which brew && brew --version || echo "❌ Homebrew not found"
which node && node --version || echo "❌ Node.js not found"
which pnpm && pnpm --version || echo "❌ pnpm not found"
echo "---"
ls package.json 2>/dev/null && echo "✓ In a project directory" || echo "❌ Not in a project directory"
ls node_modules/.pnpm 2>/dev/null && echo "✓ Dependencies installed" || echo "❌ Dependencies not installed"

Report findings in plain language and address each issue. Common fixes:

Symptom	Fix
`command not found: brew`	Re-run Homebrew install or add to PATH (`eval "$(/opt/homebrew/bin/brew shellenv)"`)
`command not found: node`	`brew install node`
`command not found: pnpm`	`corepack enable`
Dependencies not installed	`pnpm install`
Port 5173 in use	`lsof -ti:5173 \| xargs kill -9` then `pnpm run dev`
Module not found errors	`rm -rf node_modules && pnpm install`
Garbled terminal in Kiro	Add shell integration (see below)

Step 3 — Kiro shell integration (if needed)

Only if the user reports garbled terminal output in Kiro:

echo '[[ "$TERM_PROGRAM" == "kiro" ]] && . "$(kiro --locate-shell-integration-path zsh)"' >> ~/.zshrc
source ~/.zshrc

Step 4 — Verify

Once issues are resolved, confirm:

pnpm run dev starts without errors
Browser shows the project at http://localhost:5173
No errors in the browser console

Communication Style

The target user is a designer. Use plain language, explain what commands do, and don't assume terminal familiarity.