full_unpackd_rep

To convert a local reference repository into navigable HTML topic pages, the skill unpacks inputs under reference/ and generates structured site/topic-*.html files. It identifies stable structural layers, classifies content, and updates site navigation files to ensure traceable topic page generation.

A deconstruction note is a reusable markdown document detailing a repository's structural layers, dates, and rationale. You need it to document the architecture for future maintenance, ensuring the knowledge captured during topic page generation remains traceable and reusable over time.

Yes, you can generate both formats when deconstructing a reference repo. The workflow produces cohesive topic pages by creating site/topic-*.html for site navigation and site/md/*.md for markdown content, linking both together for structured site wiring and traceability.

To identify structural layers for a topic page, the skill analyzes the reference repository and extracts four to six stable architectural layers, such as the product shell, scheduling kernel, and runtime protocols. It classifies repository content according to these layers to build cohesive navigational pages.

Yes, the skill updates site navigation files automatically when adding new topic pages. It enforces a workflow step that modifies the navigational wiring under the site/ directory, ensuring newly generated topic pages are linked, date-stamped, and traceable within the site structure.

The limitation of this deconstruction workflow is its strict dependency on specific directory structures, requiring inputs under reference/ and site structure under site/. It is tailored for generating Chinese topic pages and may not apply to arbitrary repository layouts or unrelated site architectures.