Skip to content

hgxszhj/https-github.com-zhaoxuya520-reverse-skill / CTF-Sandbox-Orchestrator/competition-template-render-path

competition-template-render-path

Unverified

Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for SSR, template rendering, route loaders, hydration payloads, server-client render boundaries, and template-to-handler enforcement gaps. Use when the user asks to inspect SSR or template routes, trace render context or hydration data, compare template gating with handler enforcement, explain preview or hidden-route rendering, or connect render pipeline behavior to the decisive branch. Use only after `$ctf-sandbox-orchestrator` has already established sandbox assumptions and routed here.

Competition Template Render Path

Use this skill only as a downstream specialization after $ctf-sandbox-orchestrator is already active and has established sandbox assumptions, node ownership, and evidence priorities. If that has not happened yet, return to $ctf-sandbox-orchestrator first.

Use this skill when the decisive bug or artifact lives in route resolution, server render context, template data, or hydration handoff rather than in a plain JSON API alone.

Reply in Simplified Chinese unless the user explicitly requests English.

Quick Start

  1. Map the render chain in order: route resolution, loader or data fetch, template or component context, response HTML, hydration payload, and client takeover.
  2. Record host, route params, preview toggles, tenant or host switches, and server-only variables before mutating anything.
  3. Compare template gating with loader or handler enforcement.
  4. Preserve one successful render and one failing render path with the smallest delta.
  5. Reproduce the smallest request-to-render branch that proves the decisive behavior.

Workflow

1. Map Route To Render Context

  • Record host, path, route match, loader, template, layout, hydration blob, and client boot chunk for the active view.
  • Note whether the response is SSR HTML, static HTML plus hydration, edge-rendered content, or a template fragment used by another route.
  • Keep server-only context and client-visible context separate.

2. Trace Template And Enforcement Boundaries

  • Show where permissions, feature flags, preview state, tenant selection, or host-based switches are applied.
  • Compare template-level gating, loader-level gating, and backend handler enforcement instead of trusting any one layer.
  • Record hidden fields, inline data, hydration JSON, meta tags, or alternate partials that expose the decisive branch.

3. Reduce To The Decisive Render Path

  • Compress the result to the smallest sequence: request -> route match -> loader or template context -> rendered output or hidden data -> resulting effect.
  • State clearly whether the decisive weakness lives in route selection, template context construction, server-client hydration handoff, or mismatched enforcement between render and handler.
  • If the task becomes mostly emitted bundle recovery or source map reconstruction, hand off to the tighter bundle skill.

Read This Reference

  • Load references/template-render-path.md for the render checklist, hydration checklist, and evidence packaging.

What To Preserve

  • Route names, loader names, templates, layouts, hydration keys, and host or preview switches
  • One success or failure pair that shows where render-layer behavior diverges
  • One minimal request-to-render sequence that reaches the decisive branch
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 319kUpdated Claude CodeCodexVerifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 196kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 118kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 117kUpdated Claude CodeCodexVerifiedInstall