تشغيل أي مهارة في Manus بنقرة واحدة

freed-build-www

النجوم٧

التفرعات١

آخر تحديث١٣ يوليو ٢٠٢٦ في ٢٠:٤١

Build Freed marketing-site work in a worktree based on origin/www, verify the website, and publish a pull request to www. Use for freed.wtf pages, marketing copy, legal pages, public changelog presentation, and public roadmap presentation. Use roadmap mode only from an approved docs/roadmap-status.json source commit, never by inferring status from prose or by merging dev into www.

التثبيت

التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.

تشغيل في Manus

المصدر

freed-project

freed-project/freed

فتح مستودع GitHub عرض مستودعات المنشئ

تنزيل

تشغيل في Manus

المهن ذات الصلةSOC

استنادا إلى تصنيف SOC المهني

مطوّرو البرمجياتمهن الحاسوب والرياضيات·SOC 15-1252

مستكشف الملفات

2 ملفات

SKILL.md

readonly

name	freed-build-www
description	Build Freed marketing-site work in a worktree based on origin/www, verify the website, and publish a pull request to www. Use for freed.wtf pages, marketing copy, legal pages, public changelog presentation, and public roadmap presentation. Use roadmap mode only from an approved docs/roadmap-status.json source commit, never by inferring status from prose or by merging dev into www.
disable-model-invocation	true

Build WWW

Build one website change in the www lane and preserve its source identity through preview and review.

Establish the contract

Confirm the destination is www. Route product code and product documentation to freed-build-feature.
Record the source request, allowed authority, and source commit SHA. Preparing a PR does not grant deployment authority.
Fetch remote refs, then create the worktree with ./scripts/worktree-add.sh ../freed-<slug> -b <branch> origin/www --install full --target website.
Keep changes within website and marketing-owned paths unless the user explicitly changes scope.

Roadmap mode

Require an approved product source commit containing docs/roadmap-status.json.
Record the source commit SHA and manifest digest in the task and PR body.
Run node scripts/validate-roadmap-status.mjs in the source checkout before editing the website.
Map the manifest status exactly into website/src/app/roadmap/RoadmapContent.tsx. Do not infer status from phase prose, commit messages, or checkboxes outside the canonical manifest.
Reconcile the public phase description whenever the approved source commit changed that phase document, even when its status stayed the same.
Never merge or fast-forward www to dev. Transfer only the approved roadmap presentation change through this lane.

Verify and publish

Run website commands from website/, with the worktree root node_modules/.bin on PATH when a hoisted binary is needed.
Run npm run build from website/.
Launch ./scripts/worktree-preview.sh website on a fresh port returned by scripts/lib/find-free-port.mjs.
Use browser automation only when the task requires browser inspection. Keep the preview alive while the user is reviewing it.
Deploy a shareable preview only when requested, using ./scripts/vercel-deploy-preview.sh website.
Publish with ./scripts/worktree-publish.sh --title "<conventional title>" --base www --summary "<change>" --test "cd website && PATH=../node_modules/.bin:$PATH npm run build" --ready using the caller's existing GitHub authentication. Omit --ready while work remains. A deliberately provisioned unattended host may use FREED_TRUSTED_PUBLISHER as an optional wrapper around the same helper. Missing broker provisioning does not block the normal website PR path.
Confirm the PR targets www, the exact head SHA passed validation, and the PR state matches the granted authority.
Report the source commit, website commit, local preview URL, and remote preview deployment ID when one exists.

المزيد من هذا المستودع

نفس المستودع

freed-build-feature

freed-project/freed

Build governed Freed product work in a worktree based on origin/dev, verify the runnable slice, and publish a correctly staged pull request to dev. Use for Desktop, PWA, shared packages, sync, capture, release tooling, product behavior, and product documentation. Also use for stability tasks that require a stable task identity, a measurable counter, native validation, or an installed-build verification handoff. Do not use for public website work targeting www.

2026-07-247

freed-ship-build

freed-project/freed

Ship and verify a versioned Freed Desktop build through GitHub Actions. Use when asked to cut a dev or production release, publish a reviewed build, or repair a failed release pipeline. Preserve source and installed build identity, require exact-head validation including native tests, and create a governed post-install verification task.

2026-07-247

freed-stability-controller

freed-project/freed

Reconcile Freed stability observations, tasks, approvals, releases, soaks, and outcomes into one governed lifecycle. Use when coordinating the continuous background agents, deduplicating repeated findings, selecting the next stability action, advancing task state, or deciding that no fresh actionable work exists. This skill coordinates authority and handoffs but does not implement product code.

2026-07-247

freed-triage

freed-project/freed

Reconcile fresh Freed stability evidence into governed, deduplicated GitHub debt issues. Use after runtime alarms, soak verdicts, canary results, or CI failures, and when deciding what to fix next. Require healthy evidence sources, temporal and build matching, issue identity, atomic evidence generations, explicit authority, and instrumentation-first handling of contradictory metrics.

2026-07-247

freed-soak

freed-project/freed

Run and judge an installed-build soak of Freed Desktop from terminal evidence. Use for release observation, overnight stability windows, or post-change verification. Require the canonical release-verifier lease, the exclusive collector session lock, event-derived build identity, immutable time bounds, source-health checks, comparable process generations, and explicit inconclusive results when identity or coverage is insufficient.

2026-07-227

freed-provider-risk-review

freed-project/freed

Prepare and verify both owner gates for any Freed change that could alter behavior visible to X, Facebook, Instagram, LinkedIn, or another provider. Use before implementation that changes WebView loads, navigation, requests, retries, cadence, cookies, headers, scrolling, clicking, extraction scripts, media loading, login behavior, or provider timing, and again before making the pull request ready. Preparing a review never grants approval.

2026-07-167

name	freed-build-www
description	Build Freed marketing-site work in a worktree based on origin/www, verify the website, and publish a pull request to www. Use for freed.wtf pages, marketing copy, legal pages, public changelog presentation, and public roadmap presentation. Use roadmap mode only from an approved docs/roadmap-status.json source commit, never by inferring status from prose or by merging dev into www.
disable-model-invocation	true

Build WWW

Build one website change in the www lane and preserve its source identity through preview and review.

Establish the contract

Confirm the destination is www. Route product code and product documentation to freed-build-feature.
Record the source request, allowed authority, and source commit SHA. Preparing a PR does not grant deployment authority.
Fetch remote refs, then create the worktree with ./scripts/worktree-add.sh ../freed-<slug> -b <branch> origin/www --install full --target website.
Keep changes within website and marketing-owned paths unless the user explicitly changes scope.

Roadmap mode

Require an approved product source commit containing docs/roadmap-status.json.
Record the source commit SHA and manifest digest in the task and PR body.
Run node scripts/validate-roadmap-status.mjs in the source checkout before editing the website.
Map the manifest status exactly into website/src/app/roadmap/RoadmapContent.tsx. Do not infer status from phase prose, commit messages, or checkboxes outside the canonical manifest.
Reconcile the public phase description whenever the approved source commit changed that phase document, even when its status stayed the same.
Never merge or fast-forward www to dev. Transfer only the approved roadmap presentation change through this lane.

Verify and publish

Run website commands from website/, with the worktree root node_modules/.bin on PATH when a hoisted binary is needed.
Run npm run build from website/.
Launch ./scripts/worktree-preview.sh website on a fresh port returned by scripts/lib/find-free-port.mjs.
Use browser automation only when the task requires browser inspection. Keep the preview alive while the user is reviewing it.
Deploy a shareable preview only when requested, using ./scripts/vercel-deploy-preview.sh website.
Publish with ./scripts/worktree-publish.sh --title "<conventional title>" --base www --summary "<change>" --test "cd website && PATH=../node_modules/.bin:$PATH npm run build" --ready using the caller's existing GitHub authentication. Omit --ready while work remains. A deliberately provisioned unattended host may use FREED_TRUSTED_PUBLISHER as an optional wrapper around the same helper. Missing broker provisioning does not block the normal website PR path.
Confirm the PR targets www, the exact head SHA passed validation, and the PR state matches the granted authority.
Report the source commit, website commit, local preview URL, and remote preview deployment ID when one exists.