원클릭으로
deploy-teal-app
Write Teal app code from cowork artifact to files and push to GitHub.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Write Teal app code from cowork artifact to files and push to GitHub.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Design or edit a Mediforce WorkflowDefinition package through a structured interview. Use when authoring a new workflow from an idea, editing an existing workflow folder, or reviewing whether a workflow follows the golden standards. Interviews the user, challenges the design toward the standards, generates the package, and validates the .wd.json against the current checkout. Triggers include "design a workflow", "author a workflow", "create a .wd.json", "build a workflow package", "edit this workflow", "new Mediforce workflow".
Review pull requests, branches, or your own pre-PR diff along three parallel axes — Standards (file-by-file conventions, dead code, DRY/KISS, comments), Spec (does it match the originating issue/PRD), and Big Picture (scope creep, removable features, duplicated mechanisms). Use when asked to review a PR, diff, branch, specific files, or your own changes before shipping.
Write a Discord update for the MediForce community from rough notes. Use when the user asks for a "Discord update", "Discord post", "community update", "weekly digest for Discord", or hands over bullet-point notes to turn into a community announcement. Produces two versions (short and detailed) in engineer-to-peers tone, no marketing language.
Write and run L4 UI E2E journey tests. Use when implementing UI features (TDD red-green), adding tests for existing features, or when E2E tests need updating. Handles the workflow: write test → run → green.
Write a new test for a feature, endpoint, handler, or pure function. Use when adding test coverage for new or changed code, or when starting a feature TDD-style (RED → GREEN). Triggers include "write a test for", "add unit test", "add integration test", "add API E2E", "TDD this", "red-green this", "cover X with a test", "test plan for". Decides the right level (L1 unit / L2 integration / L3 API E2E / L4 UI E2E / L5 external), scaffolds the file, and walks the RED-GREEN loop. Use `/e2e-test` instead for the L4 UI journey workflow.
Keep project documentation in sync with code changes. Detects stale docs in current worktree diff (default), a specific commit, a PR, or across all monitored files (--audit). Auto-fixes Tier 1 executable docs (commands, ports, env vars); proposes Tier 2 narrative doc updates as an editable git diff. Triggers: "sync docs", "update docs", "check docs", "are docs up to date", "docs stale", "documentation outdated".
| name | deploy-teal-app |
| description | Write Teal app code from cowork artifact to files and push to GitHub. |
Write app.R and data.R from the previous step's artifact, then push to GitHub. That's it.
Read from previous step outputs (available in your context as workflow variables):
build-app.appCode — R code for app.Rbuild-app.dataCode — R code for data.Rbuild-app.modules — list of modules (for commit message)build-app.summary — app description (for commit message)define-requirements.githubRepo — target repo (e.g. filipstachura/tealflow-demo-app)mkdir -p /output/app
Write the appCode content to /output/app/app.R.
Write the dataCode content to /output/app/data.R.
cd /output/app
git init
git checkout -b main
git add app.R data.R
git commit -m "feat: Teal app generated by TealFlow"
git remote add origin "https://x-access-token:${GITHUB_TOKEN}@github.com/REPO.git"
git push -u origin main --force
Replace REPO with the value from define-requirements.githubRepo.
Return the GitHub repo URL as your result.