crafter-map-project

To generate context files for a codebase, this skill analyzes the repository structure, manifests, and documentation, then produces PROJECT.md, ARCHITECTURE.md, and STATE.md files. It validates outputs against rules and presents results for user approval before writing anything to the .crafter/ directory.

Mapping a repository structure into Crafter contexts is done by orchestrating an analysis workflow that translates directory layouts and manifests into .crafter/ context files. It delegates deep analysis to identify project state and architecture, surfacing results for approval before writing.

Codebase analysis keeps Crafter projects synchronized by identifying repository updates and generating updated .crafter/ context files. It analyzes directory layouts and documentation to produce PROJECT.md, ARCHITECTURE.md, and STATE.md, reducing manual setup and tracking project state.

Yes, user approval is required before writing any context files to your project. The skill validates the generated PROJECT.md, ARCHITECTURE.md, and STATE.md outputs against rules and presents the results for explicit approval to ensure safe synchronization.

Yes, you can analyze existing software projects by examining their directory layouts, manifests, and documentation. The skill processes these inputs to map the repository structure and generate the required .crafter/ context files for tracking project state.

Mapping a codebase into Crafter contexts produces three specific files: PROJECT.md, ARCHITECTURE.md, and STATE.md. These files are generated inside the .crafter/ directory to track project state, architecture, and changes.