---
name: context_full_project_export
description: Use when the user explicitly asks to 导出尽可能详细的项目全量上下文, 全量上下文导出, 项目上下文全量导出, 项目整体上下文, full project context export, export full project context, project context export, project overall context, Source Pack export, source-pack export, code index export, task context export, 当前项目代码实现, 代码级实现导出, or code-level implementation export in a Minimal Context Harness project.
---

# Context Full Project Export

## Package-Managed Boundary

This Skill is generated by `ty-context sync` and owned by the Harness package. Do not edit the generated `context_full_project_export` Skill directly.

This Skill creates a temporary export artifact only. It does not author durable Context and does not change `project_context/context.toml`.

## Purpose

When the user needs a full project context export, project overall context export or external LLM handoff, create temporary export artifacts that collect project Context, key agent guidance, architecture/module facts, code navigation and bounded source support for copying into an external tool or one-off discussion.

When the user needs a code-level implementation export, create one temporary Markdown snapshot of current source and engineering configuration files for upload to Web GPT or another external model.

## Workflow

1. Prefer the bounded Source Pack for external LLM / Web GPT planning. It writes at most 5 files total under `tmp/ty-context/context-exports/latest/` and removes old timestamped export rounds:
   - `npx --yes --package project-tiny-context-harness@latest ty-context export-context --source-pack`
2. Use `--code-index` when implementation navigation is enough and full source bodies are not needed:
   - `npx --yes --package project-tiny-context-harness@latest ty-context export-context --code-index`
3. Use `--task-context <name>` for focused handoff, preferably with a profile or explicit include selectors:
   - `npx --yes --package project-tiny-context-harness@latest ty-context export-context --task-context <name> --profile <profile-id>`
   - `npx --yes --package project-tiny-context-harness@latest ty-context export-context --task-context <name> --include-context project_context/areas/main.md --include-code 'src/example/**'`
4. Use legacy `--all` when the user explicitly wants both old temporary artifacts in one command. Do not hand-write tracked export documents:
   - `npx --yes --package project-tiny-context-harness@latest ty-context export-context --all`
5. Use legacy `--full` when only the project Context bundle is needed:
   - `npx --yes --package project-tiny-context-harness@latest ty-context export-context --full`
6. Use legacy `--code` when only the full code-level implementation snapshot is needed. It generates one Markdown file by default and is the full fallback when Source Pack bundles are not enough:
   - `npx --yes --package project-tiny-context-harness@latest ty-context export-context --code`
7. Custom output paths are allowed only for legacy single-artifact modes and must stay under the temporary export directory. `--all` and Source Pack modes do not accept `--output`:
   - `npx --yes --package project-tiny-context-harness@latest ty-context export-context --full --output tmp/ty-context/context-exports/my-export.md`
   - `npx --yes --package project-tiny-context-harness@latest ty-context export-context --code --output tmp/ty-context/context-exports/my-code-export.md`
8. Use dry-run mode to inspect planned sources before writing:
   - `npx --yes --package project-tiny-context-harness@latest ty-context export-context --source-pack --check`
   - `npx --yes --package project-tiny-context-harness@latest ty-context export-context --code-index --check`
   - `npx --yes --package project-tiny-context-harness@latest ty-context export-context --task-context <name> --check`
   - `npx --yes --package project-tiny-context-harness@latest ty-context export-context --all --check`
   - `npx --yes --package project-tiny-context-harness@latest ty-context export-context --full --check`
   - `npx --yes --package project-tiny-context-harness@latest ty-context export-context --code --check`
9. After exporting, report artifact paths, source counts, recommended upload sets and warnings to the user. Do not summarize export contents back into Context.

## Output Boundaries

- Export artifacts must remain temporary export artifacts, not Context.
- `--source-pack` defaults to `tmp/ty-context/context-exports/latest/`, with `source-pack-manifest.json`, `full-project-context.md`, `code-index.md` and optional `code-bundle-core.md` / `code-bundle-extended.md`.
- `--source-pack` and `--task-context` are capped at 5 output files. `--max-pack-files` cannot exceed 5.
- `--code-index` creates a navigation index and manifest without complete source bodies.
- `--task-context <name>` creates `task-contexts/task-context-<name>.md` plus optional support bundle; profile verification entries are listed, not executed.
- `--full` defaults to `tmp/ty-context/context-exports/full-project-context-<timestamp>.md`.
- `--code` defaults to `tmp/ty-context/context-exports/code-level-implementation-<timestamp>/code-level-implementation.md`.
- `--all` generates both default artifacts with the same timestamp.
- `--all` does not accept `--output`; custom filenames are supported only for `--full` or `--code`.
- `--code` creates one Markdown file, not shards or `all.md`.
- Do not output to `project_context/**`.
- Do not modify `project_context/context.toml`.
- Do not register export artifacts as `[[context]]`, `implementation-index` or any Context graph node.
- Do not write tracked docs; if the user asks for an ordinary docs path, redirect to `tmp/ty-context/context-exports/**`.
- Export contents may include redaction warnings; do not bypass secret/token/cookie/password/api_key/credential/bearer/authorization filtering. Use `--redaction-strict` when the user wants the command to fail if any redaction occurred.
- Profiles under `<harnessRoot>/config.yaml` are export selectors only. They must not become durable Context facts or execute verification commands.

## Handoff

- Report `Export: generated <path>` or `Export: check completed; no files written`.
- If the CLI rejects an output path, explain that this prevents temporary exports from polluting durable fact sources and suggest `tmp/ty-context/context-exports/<name>.md`.
- Context drift check should be `Context: no durable project facts changed` unless the task also changes Harness rules.