Run any Skill in Manus with one click

tuturuuu-web-release

Stars52

Forks32

UpdatedJuly 10, 2026 at 17:10

Apps/web release metadata and version-badge guidance for Tuturuuu platform work, including release-please-managed TUTURUUU_PLATFORM_VERSION metadata, blue/green runtime snapshot fallbacks, PLATFORM_BUILD metadata, and focused release verification.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

tutur3u

tutur3u/platform

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

File Explorer

3 files

SKILL.md

readonly

name	tuturuuu-web-release
description	Apps/web release metadata and version-badge guidance for Tuturuuu platform work, including release-please-managed TUTURUUU_PLATFORM_VERSION metadata, blue/green runtime snapshot fallbacks, PLATFORM_BUILD metadata, and focused release verification.

Tuturuuu Web Release

Use this skill when touching the apps/web version badge, platform release metadata, Docker blue/green deployment metadata, release docs, or release-please version metadata.

Core Rules

Treat TUTURUUU_PLATFORM_VERSION in @tuturuuu/utils/platform-release as the displayed platform badge version. Do not manually bump it for ordinary authored commits; Release Please updates it from platform-version.txt.
Keep the x-release-please-version comments on the platform version constant and matching test expectation. The monorepo release-please config also keeps platform-version.txt aligned for the platform release component.
Do not bump apps/web/package.json for badge/version display unless the user explicitly asks for package metadata changes.
Preserve the account gate: only exact @tuturuuu.com users can see/manage the badge, and the user setting remains opt-in.
Preserve the bottom-right compact badge and hover/focus details unless the user explicitly asks for a visual redesign.
Read only lightweight blue/green runtime files for self-hosted inference: prod/target-state.json, prod/active-color, prod/deployment-stamp, watch/blue-green-auto-deploy.status.json, and watch/blue-green-auto-deploy.history.json.

Metadata Precedence

For apps/web, keep metadata precedence stable:

Explicit PLATFORM_BUILD_* runtime environment values.
Mounted blue/green runtime snapshot via PLATFORM_BLUE_GREEN_MONITORING_DIR, with local tmp/docker-web fallbacks for development.
Generated Vercel/GitHub build metadata.
Existing local defaults.

Do not invent deployment URL, ref, or environment from active color, commit hash, or deployment stamp alone. Use those fields only when an explicit env, runtime row, status snapshot, or generated metadata provides them.

builtAt means the checked-out source commit timestamp. Do not populate it from deployment start, finish, activation, promotion, or wall-clock time. Keep those deployment timestamps in GitHub/Vercel records and blue/green history.

Implementation Checklist

Read references/web-release-checklist.md when implementing or reviewing release metadata changes. It lists the expected files, fallback selection order, and focused verification commands.

More from this repository

same repository

tuturuuu-mobile-task-board

tutur3u/platform

Tuturuuu Flutter mobile task-board workflow guidance. Use when Codex changes apps/mobile task board behavior, task detail routing, task dates, overdue labels, assignees, task description view/edit mode, task list refreshes, workspace-aware navigation, mobile BLoC/Cubit code, or release-please-managed mobile release metadata.

2026-07-1652

tuturuuu-cli-tasks

tutur3u/platform

Tuturuuu CLI task workflow guidance. Use when listing, reading, creating, templating, splitting, moving, closing, or marking Tuturuuu tasks through `ttr tasks` or `ttr task-templates`, including task board/list/label discovery, compact output, task mutation verification, and ttr-first task capture.

2026-07-1452

tuturuuu-browser-vercel-debugging

tutur3u/platform

Tuturuuu browser and Vercel CLI development, production troubleshooting, verification, performance, and product-improvement guidance. Use when reproducing a deployed UI or API bug, correlating browser failures with Vercel runtime/build logs, checking satellite-domain routing and authentication, auditing responsive or i18n behavior, investigating Vercel cost or latency, or verifying a fix without modifying customer data.

2026-07-1352

tuturuuu-development-tooling

tutur3u/platform

Tuturuuu development tooling and shared-learning guidance. Use when improving Codex skills, plugin behavior, repo automation, validation scripts, docs runbooks, developer experience, agent workflows, or recurring learnings that should benefit future Tuturuuu contributors and assistants.

2026-07-1352

tuturuuu-platform

tutur3u/platform

Tuturuuu platform monorepo workflow guidance. Use when Codex works in the tutur3u/platform repo or a local Tuturuuu platform checkout, especially for apps/web Next.js changes, packages/* shared code, apps/database Supabase migrations, apps/docs documentation, translations, navigation, TanStack Query data fetching, repo verification, or Conventional Commit/branch follow-through.

2026-07-1152

tuturuuu-agent-coordination

tutur3u/platform

Use when any harness (Codex, Claude Code, or another assistant) works in a dirty or shared Tuturuuu checkout, spans separate git worktrees or branches, encounters active or archived coordination notes, needs ownership context, has overlapping paths, is handing off work between agents or tools, must protect uncommitted work from concurrent destructive Git, must archive completed coordination notes, or must coordinate staged paths and commit windows.

2026-07-1152

name	tuturuuu-web-release
description	Apps/web release metadata and version-badge guidance for Tuturuuu platform work, including release-please-managed TUTURUUU_PLATFORM_VERSION metadata, blue/green runtime snapshot fallbacks, PLATFORM_BUILD metadata, and focused release verification.

Tuturuuu Web Release

Use this skill when touching the apps/web version badge, platform release metadata, Docker blue/green deployment metadata, release docs, or release-please version metadata.

Core Rules

Treat TUTURUUU_PLATFORM_VERSION in @tuturuuu/utils/platform-release as the displayed platform badge version. Do not manually bump it for ordinary authored commits; Release Please updates it from platform-version.txt.
Keep the x-release-please-version comments on the platform version constant and matching test expectation. The monorepo release-please config also keeps platform-version.txt aligned for the platform release component.
Do not bump apps/web/package.json for badge/version display unless the user explicitly asks for package metadata changes.
Preserve the account gate: only exact @tuturuuu.com users can see/manage the badge, and the user setting remains opt-in.
Preserve the bottom-right compact badge and hover/focus details unless the user explicitly asks for a visual redesign.
Read only lightweight blue/green runtime files for self-hosted inference: prod/target-state.json, prod/active-color, prod/deployment-stamp, watch/blue-green-auto-deploy.status.json, and watch/blue-green-auto-deploy.history.json.

Metadata Precedence

For apps/web, keep metadata precedence stable:

Explicit PLATFORM_BUILD_* runtime environment values.
Mounted blue/green runtime snapshot via PLATFORM_BLUE_GREEN_MONITORING_DIR, with local tmp/docker-web fallbacks for development.
Generated Vercel/GitHub build metadata.
Existing local defaults.

Implementation Checklist

Read references/web-release-checklist.md when implementing or reviewing release metadata changes. It lists the expected files, fallback selection order, and focused verification commands.