By default, code2skill writes artifacts under .code2skill/ inside the target repository.
This directory is the default artifact bundle root for the repository workflow. It groups the structural analysis outputs, planning outputs, generated Skills, diagnostics, and incremental state under one predictable location.
Within this bundle, code2skill treats generated Skills as the final product layer. The other files remain important, but they are intermediate artifacts that support generation, review, reporting, and incremental CI refresh.
.code2skill/
project-summary.md
skill-blueprint.json
skill-plan.json
report.json
references/
architecture.md
code-style.md
workflows.md
api-usage.md
skills/
index.md
*.md
state/
analysis-state.json
skills/index.mdandskills/*.md: grounded AI-consumable Skill documents
project-summary.md: human-readable project overviewskill-blueprint.json: structural analysis output from Phase 1skill-plan.json: LLM-planned Skill inventoryreport.json: execution metrics, cost estimates, and impact summariesreferences/*.md: supporting architectural and workflow referencesstate/analysis-state.json: incremental execution cache
When write_state is enabled, both report.json accounting and ScanExecution.output_files include state/analysis-state.json in this intermediate layer.
In product terms, .code2skill/ is the workspace-local artifact bundle. The final repository-local product is the generated Skill set, while adapt publishes that Skill layer into the repository locations where each AI tool expects to read it.
The adapt command writes target-specific files under the repository root:
AGENTS.mdCLAUDE.md.cursor/rules/*.github/copilot-instructions.md.windsurfrules
These files are not written into .code2skill/; they are written where the target tool expects to read them.