Communitygithub.com

NVlabs/Skill2Env

작업 공간 인식 선박을 위한 읽기 전용 대시보드 큐입니다. (gstack)

Skill2Env란 무엇인가요?

이 스킬은 `/landing-report` 명령을 통해 현재 브랜치와 PR 환경에 대한 종합적인 스냅샷을 제공하는 읽기 전용 버전 큐 대시보드입니다. 주로 어떤 VERSION 슬롯이 열린 PR에 의해 점유되어 있는지, 어떤 Conductor 작업 공간에서 곧 출시될 작업이 진행 중인지, 그리고 다음에 `/ship`이 선택할 슬롯이 무엇인지 보여줍니다. 특히 'landing report', '큐 보여줘', '열린 PR 확인'과 같은 요청에 응답할 때 유용합니다. 이 스킬은 Claude Code 환경에서 실행되며, 세션 종류(대화형/헤드리스)와 Conductor 연동 여부를 감지하여 적절히 동작합니다. 읽기 전용이므로 어떠한 변경도 수행하지 않고 단순히 현재 상태를 요약하여 보여주기 때문에, 팀의 출시 파이프라인 현황을 빠르게 파악하는 데 최적화되어 있습니다. gstack 도구 모음의 일부로, 다양한 환경 변수와 설정(gstack-config)을 통해 동작을 사용자 정의할 수 있습니다.

지원 대상✓Claude Code✓Codex CLI~Cursor
npx skills add https://github.com/NVlabs/Skill2Env/tree/HEAD/SkillHub/skills/garry-tan/gstack/landing-report

즐겨 사용하는 AI에게 물어보기

이 에이전트 스킬이 미리 로드된 새 채팅을 엽니다.

문서

이 스킬을 호출해야 하는 경우

현재 열린 PR이 요구하고 있는 VERSION 슬롯, 어떤 자매 Conductor 워크스페이스에서 곧 출시될 WIP 작업이 있는지, 그리고 /ship이 다음에 선택할 슬롯을 보여줍니다. 변경 사항은 없습니다. 단지 스냅샷일 뿐입니다. "landing report", "queue에 무엇이 있나요?", "열린 PR을 보여주세요", 또는 "다음에 어떤 버전을 요청해야 하나요?"와 같은 질문을 받았을 때 사용하세요.

/landing-report — 버전 큐 대시보드

서문 (먼저 실행)

_UPD=$(~/.claude/skills/gstack/bin/gstack-update-check 2>/dev/null || .claude/skills/gstack/bin/gstack-update-check 2>/dev/null || true)
[ -n "$_UPD" ] && echo "$_UPD" || true
mkdir -p ~/.gstack/sessions
touch ~/.gstack/sessions/"$PPID"
_SESSIONS=$(find ~/.gstack/sessions -mmin -120 -type f 2>/dev/null | wc -l | tr -d ' ')
find ~/.gstack/sessions -mmin +120 -type f -exec rm {} + 2>/dev/null || true
_PROACTIVE=$(~/.claude/skills/gstack/bin/gstack-config get proactive 2>/dev/null || echo "true")
_PROACTIVE_PROMPTED=$([ -f ~/.gstack/.proactive-prompted ] && echo "yes" || echo "no")
_BRANCH=$(git branch --show-current 2>/dev/null || echo "unknown")
echo "BRANCH: $_BRANCH"
_SKILL_PREFIX=$(~/.claude/skills/gstack/bin/gstack-config get skill_prefix 2>/dev/null || echo "false")
echo "PROACTIVE: $_PROACTIVE"
echo "PROACTIVE_PROMPTED: $_PROACTIVE_PROMPTED"
echo "SKILL_PREFIX: $_SKILL_PREFIX"
source <(~/.claude/skills/gstack/bin/gstack-repo-mode 2>/dev/null) || true
REPO_MODE=${REPO_MODE:-unknown}
echo "REPO_MODE: $REPO_MODE"
_SESSION_KIND=$(~/.claude/skills/gstack/bin/gstack-session-kind 2>/dev/null || echo "interactive")
case "$_SESSION_KIND" in spawned|headless|interactive) ;; *) _SESSION_KIND="interactive" ;; esac
echo "SESSION_KIND: $_SESSION_KIND"
# Conductor host: AskUserQuestion is unreliable here (native disabled, MCP
# variant flaky), so skills render decisions as prose instead of calling the
# tool. Gated on !headless so an eval/CI run INSIDE Conductor (GSTACK_HEADLESS)
# still BLOCKs rather than rendering prose to nobody.
if [ "$_SESSION_KIND" != "headless" ] && { [ -n "${CONDUCTOR_WORKSPACE_PATH:-}" ] || [ -n "${CONDUCTOR_PORT:-}" ]; }; then
  echo "CONDUCTOR_SESSION: true"
fi
_ACTIVATED=$([ -f ~/.gstack/.activated ] && echo "yes" || echo "no")
_FIRST_LOOP_SHOWN=$([ -f ~/.gstack/.first-loop-tip-shown ] && echo "yes" || echo "no")
echo "ACTIVATED: $_ACTIVATED"
echo "FIRST_LOOP_SHOWN: $_FIRST_LOOP_SHOWN"
# First-run project detection: run the detector ONLY on the first-ever skill run
# (ACTIVATED=no, interactive) so it stays off the hot path for every run after.
_FIRST_TASK=""
if [ "$_ACTIVATED" = "no" ] && [ "$_SESSION_KIND" != "headless" ]; then
  _FIRST_TASK=$(~/.claude/skills/gstack/bin/gstack-first-task-detect 2>/dev/null || true)
fi
echo "FIRST_TASK: $_FIRST_TASK"
_LAKE_SEEN=$([ -f ~/.gstack/.completeness-intro-seen ] && echo "yes" || echo "no")
echo "LAKE_INTRO: $_LAKE_SEEN"
_TEL=$(~/.claude/skills/gstack/bin/gstack-config get telemetry 2>/dev/null || true)
_TEL_PROMPTED=$([ -f ~/.gstack/.telemetry-prompted ] && echo "yes" || echo "no")
_TEL_START=$(date +%s)
_SESSION_ID="$$-$(date +%s)"
echo "TELEMETRY: ${_TEL:-off}"
echo "TEL_PROMPTED: $_TEL_PROMPTED"
_EXPLAIN_LEVEL=$(~/.claude/skills/gstack/bin/gstack-config get explain_level 2>/dev/null || echo "default")
if [ "$_EXPLAIN_LEVEL" != "default" ] && [ "$_EXPLAIN_LEVEL" != "terse" ]; then _EXPLAIN_LEVEL="default"; fi
echo "EXPLAIN_LEVEL: $_EXPLAIN_LEVEL"
_QUESTION_TUNING=$(~/.claude/skills/gstack/bin/gstack-config get question_tuning 2>/dev/null || echo "false")
echo "QUESTION_TUNING: $_QUESTION_TUNING"
mkdir -p ~/.gstack/analytics
if [ "$_TEL" != "off" ]; then
echo '{"skill":"landing-report","ts":"'$(date -u +%Y-%m-%dT%H:%M:%SZ)'","repo":"'$(_repo=$(basename "$(git rev-parse --show-toplevel 2>/dev/null)" 2>/dev/null | tr -cd 'a-zA-Z0-9._-'); echo "${_repo:-unknown}")'"}'  >> ~/.gstack/analytics/skill-usage.jsonl 2>/dev/null || true
fi
for _PF in $(find ~/.gstack/analytics -maxdepth 1 -name '.pending-*' 2>/dev/null); do
  if [ -f "$_PF" ]; then
    if [ "$_TEL" != "off" ] && [ -x "~/.claude/skills/gstack/bin/gstack-telemetry-log" ]; then
      ~/.claude/skills/gstack/bin/gstack-telemetry-log --event-type skill_run --skill _pending_finalize --outcome unknown --session-id "$_SESSION_ID" 2>/dev/null || true
    fi
    rm -f "$_PF" 2>/dev/null || true
  fi
  break
done
eval "$(~/.claude/skills/gstack/bin/gstack-slug 2>/dev/null)" 2>/dev/null || true
_LEARN_FILE="${GSTACK_HOME:-$HOME/.gstack}/projects/${SLUG:-unknown}/learnings.jsonl"
if [ -f "$_LEARN_FILE" ]; then
  _LEARN_COUNT=$(wc -l < "$_LEARN_FILE" 2>/dev/null | tr -d ' ')
  echo "LEARNINGS: $_LEARN_COUNT entries loaded"
  if [ "$_LEARN_COUNT" -gt 5 ] 2>/dev/null; then
    ~/.claude/skills/gstack/bin/gstack-learnings-search --limit 3 2>/dev/null || true
  fi
else
  echo "LEARNINGS: 0"
fi
~/.claude/skills/gstack/bin/gstack-timeline-log '{"skill":"landing-report","event":"started","branch":"'"$_BRANCH"'","session":"'"$_SESSION_ID"'"}' 2>/dev/null &
_HAS_ROUTING="no"
if [ -f CLAUDE.md ] && grep -q "## Skill routing" CLAUDE.md 2>/dev/null; then
  _HAS_ROUTING="yes"
fi
_ROUTING_DECLINED=$(~/.claude/skills/gstack/bin/gstack-config get routing_declined 2>/dev/null || echo "false")
echo "HAS_ROUTING: $_HAS_ROUTING"
echo "ROUTING_DECLINED: $_ROUTING_DECLINED"
_VENDORED="no"
if [ -d ".claude/skills/gstack" ] && [ ! -L ".claude/skills/gstack" ]; then
  if [ -f ".claude/skills/gstack/VERSION" ] || [ -d ".claude/skills/gstack/.git" ]; then
    _VENDORED="yes"
  fi
fi
echo "VENDORED_GSTACK: $_VENDORED"
echo "MODEL_OVERLAY: claude"
_CHECKPOINT_MODE=$(~/.claude/skills/gstack/bin/gstack-config get checkpoint_mode 2>/dev/null || echo "explicit")
_CHECKPOINT_PUSH=$(~/.claude/skills/gstack/bin/gstack-config get checkpoint_push 2>/dev/null || echo "false")
echo "CHECKPOINT_MODE: $_CHECKPOINT_MODE"
echo "CHECKPOINT_PUSH: $_CHECKPOINT_PUSH"
# Plan-mode hint for skills like /spec that branch behavior on plan-mode state.
# Claude Code exposes plan mode via system reminders; we detect best-effort
# from CLAUDE_PLAN_FILE (set by the harness when plan mode is active) and
# fall back to "inactive". Codex hosts and Claude execution mode both end up
# inactive, which is the safe default (defaults to file+execute pipeline).
if [ -n "${CLAUDE_PLAN_FILE:-}${GSTACK_PLAN_MODE_FORCE:-}" ]; then
  export GSTACK_PLAN_MODE="active"
elif [ "${GSTACK_PLAN_MODE:-}" = "active" ]; then
  export GSTACK_PLAN_MODE="active"
else
  export GSTACK_PLAN_MODE="inactive"
fi
echo "GSTACK_PLAN_MODE: $GSTACK_PLAN_MODE"
[ -n "$OPENCLAW_SESSION" ] && echo "SPAWNED_SESSION: true" || true

Plan Mode 안전 작업

Plan 모드에서는 계획을 수립하는 데 도움이 되므로 다음 작업이 허용됩니다: $B, $D, codex exec/codex review, ~/.gstack/에 쓰기, 계획 파일에 쓰기, 생성된 아티팩트에 open.

Plan 모드 중 스킬 호출

사용자가 plan 모드에서 스킬을 호출하면, 스킬이 일반적인 plan 모드 동작보다 우선합니다. 스킬 파일을 참고 자료가 아닌 실행 가능한 명령어로 취급하세요. 0단계부터 단계별로 따르세요. 첫 번째 AskUserQuestion은 워크플로우가 plan 모드로 진입하는 것이지, 이를 위반하는 것이 아닙니다. AskUserQuestion (모든 변형 — mcp__*__AskUserQuestion 또는 네이티브, "AskUserQuestion 형식 → 도구 해결" 참조)은 plan 모드의 종료 턴 요구 사항을 충족시킵니다. AskUserQuestion을 사용할 수 없거나 호출이 실패하면, AskUserQuestion 형식 실패 대체 방안을 따르세요: headless → BLOCKED; interactive → 산문 대체 방안 (이 역시 종료 턴 요구 사항 충족). STOP 지점에서 즉시 중지하세요. 거기서 워크플로우를 계속하거나 ExitPlanMode를 호출하지 마세요. "PLAN MODE EXCEPTION — ALWAYS RUN"으로 표시된 명령어는 실행합니다. 스킬 워크플로우가 완료된 후에만 ExitPlanMode를 호출하거나, 사용자가 스킬을 취소하거나 plan 모드를 종료하라고 지시하는 경우에만 호출합니다.

PROACTIVE가 "false"이면, 스킬을 자동으로 호출하거나 사전에 제안하지 마세요. 스킬이 유용해 보이면, "I think /skillname might help here — want me to run it?"라고 물어보세요.

SKILL_PREFIX가 "true"이면, /gstack-* 이름을 제안/호출하세요. 디스크 경로는 ~/.claude/skills/gstack/[skill-name]/SKILL.md로 유지됩니다.

출력에 UPGRADE_AVAILABLE <old> <new>가 표시되면: ~/.claude/skills/gstack/gstack-upgrade/SKILL.md를 읽고 "인라인 업그레이드 흐름"을 따르세요 (구성된 경우 자동 업그레이드, 그렇지 않으면 4가지 옵션과 함께 AskUserQuestion, 거부된 경우 snooze 상태 기록).

출력에 JUST_UPGRADED <from> <to>가 표시되면: "Running gstack v{to} (just updated!)"를 출력하세요. SPAWNED_SESSION이 true이면, 기능 발견을 건너뛰세요.

기능 발견, 세션당 최대 한 번 프롬프트:

  • ~/.claude/skills/gstack/.feature-prompted-continuous-checkpoint가 없는 경우: 연속 체크포인트 자동 커밋에 대해 AskUserQuestion. 수락되면 ~/.claude/skills/gstack/bin/gstack-config set checkpoint_mode continuous를 실행하세요. 항상 마커를 터치하세요.
  • ~/.claude/skills/gstack/.feature-prompted-model-overlay가 없는 경우: "Model overlays are active. MODEL_OVERLAY shows the patch."라고 알리세요. 항상 마커를 터치하세요.

업그레이드 프롬프트 후, 워크플로우를 계속하세요.

WRITING_STYLE_PENDING이 yes이면: 작성 스타일에 대해 한 번 물어보세요:

v1 prompts are simpler: first-use jargon glosses, outcome-framed questions, shorter prose. Keep default or restore terse?

옵션:

  • A) 새 기본값 유지 (권장 — 좋은 글쓰기는 모두에게 도움이 됩니다)
  • B) V0 산문 복원 — explain_level: terse 설정

A를 선택한 경우: explain_level을 설정하지 않은 상태로 둡니다 (기본값은 default). B를 선택한 경우: ~/.claude/skills/gstack/bin/gstack-config set explain_level terse를 실행하세요.

항상 실행 (선택과 관계없이):

rm -f ~/.gstack/.writing-style-prompt-pending
touch ~/.gstack/.writing-style-prompted

WRITING_STYLE_PENDING이 no이면 건너뛰세요.

LAKE_INTRO가 no이면: "gstack follows the Boil the Ocean principle — do the complete thing when AI makes marginal cost near-zero. Read more: https://garryslist.org/posts/boil-the-ocean"라고 말하고 열겠냐고 물어보세요:

open https://garryslist.org/posts/boil-the-ocean
touch ~/.gstack/.completeness-intro-seen

open은 예라고 답할 때만 실행하세요. touch는 항상 실행하세요.

TEL_PROMPTED가 no이고 LAKE_INTRO가 yes이면: AskUserQuestion을 통해 텔레메트리에 대해 한 번 물어보세요:

Help gstack get better. Share usage data only: skill, duration, crashes, stable device ID. No code or file paths. Your repo name is recorded locally only and stripped before any upload.

옵션:

  • A) Help gstack get better! (recommended)
  • B) No thanks

A를 선택한 경우: ~/.claude/skills/gstack/bin/gstack-config set telemetry community 실행

B를 선택한 경우: 후속 질문:

Anonymous mode sends only aggregate usage, no unique ID.

옵션:

  • A) Sure, anonymous is fine
  • B) No thanks, fully off

B→A인 경우: ~/.claude/skills/gstack/bin/gstack-config set telemetry anonymous 실행 B→B인 경우: ~/.claude/skills/gstack/bin/gstack-config set telemetry off 실행

항상 실행:

touch ~/.gstack/.telemetry-prompted

TEL_PROMPTED가 yes이면 건너뛰세요.

PROACTIVE_PROMPTED가 no이고 TEL_PROMPTED가 yes이면: 한 번 물어보세요:

Let gstack proactively suggest skills, like /qa for "does this work?" or /investigate for bugs?

옵션:

  • A) Keep it on (recommended)
  • B) Turn it off — I'll type /commands myself

A를 선택한 경우: ~/.claude/skills/gstack/bin/gstack-config set proactive true 실행 B를 선택한 경우: ~/.claude/skills/gstack/bin/gstack-config set proactive false 실행

항상 실행:

touch ~/.gstack/.proactive-prompted

PROACTIVE_PROMPTED가 yes이면 건너뛰세요.

첫 실행 안내 (일회성)

ACTIVATED가 no (이 머신에서 첫 스킬 실행)이고 서문이 비어 있지 않은 FIRST_TASK: 값을 출력했으며 nongit이 아닌 경우: 토큰에서 매핑된 짧은 프로젝트별 한 줄을 참고 삼아 표시한 다음, 사용자가 실제로 요청한 대로 계속 진행하세요. 작업을 중단하지 마십시오. 토큰 매핑: greenfield → "Fresh repo — shape it first with /spec or /office-hours." code_node/code_python/code_rust/code_go/code_ruby/code_ios → "There's code here — /qa to see it work, or /investigate if something's off." branch_ahead → "Unshipped work on this branch — /review then /ship." dirty_default → "Uncommitted changes — /review before committing." clean_default → "Pick one: /spec, /investigate, or /qa." 그런 다음 본 토큰을 TASK_TOKEN으로 대체하고 (최선의 노력으로) 실행한 다음, 활성화됨을 표시하세요:

~/.claude/skills/gstack/bin/gstack-telemetry-log --event-type first_task_scaffold_shown --skill "TASK_TOKEN" --outcome shown 2>/dev/null || true
touch ~/.gstack/.activated 2>/dev/null || true

ACTIVATED가 no이지만 FIRST_TASK:가 비어 있거나 nongit인 경우 (headless, 비-git, 또는 실행 가능한 항목 없음): 아무것도 표시하지 말고 touch ~/.gstack/.activated 2>/dev/null || true만 실행하세요.

그렇지 않고 ACTIVATED가 yes이고 FIRST_LOOP_SHOWN이 no인 경우: 참고 삼아 한 번 말한 다음 (계속 진행):

Tip: gstack pays off when you complete one loop — plan → review → ship. A common first loop: /office-hours or /spec to shape it, /plan-eng-review to lock it, then /ship.

그런 다음 touch ~/.gstack/.first-loop-tip-shown 2>/dev/null || true를 실행하세요.

ACTIVATED와 FIRST_LOOP_SHOWN이 모두 yes이면 이 섹션을 건너뛰세요.

HAS_ROUTING이 no이고 ROUTING_DECLINED이 false이며 PROACTIVE_PROMPTED가 yes인 경우: 프로젝트 루트에 CLAUDE.md 파일이 있는지 확인하세요. 없으면 생성하세요.

AskUserQuestion 사용:

gstack works best when your project's CLAUDE.md includes skill routing rules.

옵션:

  • A) Add routing rules to CLAUDE.md (recommended)
  • B) No thanks, I'll invoke skills manually

A를 선택한 경우: 이 섹션을 CLAUDE.md 끝에 추가하세요:


## Skill routing

When the user's request matches an available skill, invoke it via the Skill tool. When in doubt, invoke the skill.

Key routing rules:
- Product ideas/brainstorming → invoke /office-hours
- Strategy/scope → invoke /plan-ceo-review
- Architecture → invoke /plan-eng-review
- Design system/plan review → invoke /design-consultation or /plan-design-review
- Full review pipeline → invoke /autoplan
- Bugs/errors → invoke

...

Individual skills in this repo

This repo contains 13 individual skills — each has its own dedicated page.

NVlabs/Skill2Env

This skill should be used when the user asks about "digital portfolio", "portfolio website", "project description", "case study", "portfolio curation", "creative portfolio", "act as a portfolio curator", "portfolio curator mode", "portfolio review", "professional presentation", "portfolio architecture", "work samples", "portfolio bio", or needs expertise in building, structuring, and writing professional digital portfolios. Part of the AlterLab FC Skills collection (New Media & Communication department).

NVlabs/Skill2Env

This skill should be used when the user asks about "web content strategy", "SEO writing", "UX writing", "information architecture", "content architecture", "website structure", "act as a web content strategist", "web strategist mode", "site map", "content audit", "microcopy", "meta descriptions", "content hierarchy", "content governance", or needs expertise in planning, structuring, and writing content for websites and digital platforms. Part of the AlterLab FC Skills collection (New Media & Communication department).

NVlabs/Skill2Env

When the user wants to create, generate, or produce video content using AI tools or programmatic frameworks. Also use when the user mentions 'video production,' 'AI video,' 'Remotion,' 'Hyperframes,' 'HeyGen,' 'Synthesia,' 'Veo,' 'Sora,' 'Runway,' 'Kling,' 'Seedance,' 'Hailuo,' 'MiniMax,' 'Pika,' 'Hunyuan,' 'Wan,' 'video generation,' 'AI avatar,' 'talking head video,' 'programmatic video,' 'video template,' 'explainer video,' 'product demo video,' 'video pipeline,' or 'make me a video.' Use this for video creation, generation, and production workflows. For video content strategy and what to post, see social. For paid video ad creative, see ad-creative.

NVlabs/Skill2Env

Balance visual design with ATS compatibility for creative roles

NVlabs/Skill2Env

Build immersive, cinematic 2.5D interactive websites using scroll storytelling, parallax depth, text animations, and premium scroll effects — no WebGL required. Use this skill for any web design task: landing pages, product sites, hero sections, scroll animations, parallax, sticky sections, section overlaps, floating products between sections, clip-path reveals, text that flies in from sides, words that light up on scroll, curtain drops, iris opens, card stacks, bleed typography, and any site that should feel cinematic or premium. Trigger on phrases like "make it feel alive", "Apple-style animation", "sections that overlap", "product rises between sections", "immersive", "scrollytelling", or any scroll-driven visual effect. Covers 45+ techniques across 8 categories. Always inspects, judges, and plans assets before coding. Use aggressively for ANY web design task.

NVlabs/Skill2Env

Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.

NVlabs/Skill2Env

Audits any landing or service page across 48 checks in 10 categories for LLM/AI discoverability, GEO readiness, content clarity, schema markup, internal linking, freshness signals, and technical crawlability. Produces an overall score out of 100, a per-category score out of 100, pass/warn/fail/ manual counts, and a prioritised fix list — all rendered as a standalone HTML report saved to disk. Use when a user provides a URL and asks to audit it, score it, check its GEO readiness, test its AI discoverability, run a landing page audit, or evaluate it for LLM citation potential. Also trigger on phrases like "audit this page", "score this URL", "check GEO for", "is this page AI-ready", "run a GEO audit", "LLM page check", "how would AI read this page", or "landing page score".

NVlabs/Skill2Env

Generates a premium single-page HTML landing page with 3D CSS animations, GSAP scroll effects, and mouse-parallax depth. Forcing intake (product + elevator pitch, audience register, brand overrides, tone) locks down positioning before any copy or markup is written, so the page reflects the actual product rather than generic boilerplate. Use whenever the user says 'landing for X', 'create a landing page', 'build a landing page', 'make a landing page for X', 'I need a web page for Y', or provides product/service details and wants a polished website. Also triggers on 'promotional page', 'product page', 'one-pager', 'web presence', 'sales page'. Outputs a single self-contained HTML file (Claude Code) or HTML artifact (Claude.ai). Supports configurable brand colors via CSS custom property overrides.

NVlabs/Skill2Env

Use when a user asks to build, optimize, backtest, rebalance, or analyze a stock portfolio with Mean-CVaR, efficient frontiers, scenario generation, or NVIDIA cuOpt.

NVlabs/Skill2Env

Transform resume bullets into detailed portfolio case studies

NVlabs/Skill2Env

Generates high-converting landing pages as complete Next.js/React (TSX) components with Tailwind CSS. Creates hero sections, feature grids, pricing tables, FAQ accordions, testimonial blocks, and CTA sections using proven copy frameworks (PAS, AIDA, BAB). Outputs SEO meta tags, structured data, and performance-optimised code targeting Core Web Vitals (LCP < 1s, CLS < 0.1). Use when the user asks to create a landing page, marketing page, homepage, single-page site, lead capture page, campaign page, promo page, or conversion-optimised web page — or when they want to A/B test landing page variants or replace a static page with one designed to convert.

NVlabs/Skill2Env

> Visual design direction framework organized by emotional intent (Warm/Cold x Active/Calm). The first design reference system that categorizes sites by what they make you FEEL, not how they look. Includes 48 annotated public website references.

NVlabs/Skill2Env

Run a structured 5-pass finishing audit on any website before launch — scoring visual polish, technical foundation, UX completeness, content quality, and cross-device readiness on 100 points. Use when: **Pre-launch** - Final validation before going live; **Post-redesign** - Verify nothing broke during the overhaul; **Client handoff** - Structured proof that the site is ready; **Quarterly review** - Catch accumulated debt; **Single-pass focus** - Run just Pass 2 after a perf sprint

관련 스킬