Resource Study Templates

Cross-pollination mapping generates structured mappings from a studied external resource into a target project. This enables effective knowledge reuse by capturing developer experience, governance rules, lifecycle hooks, and plugin manifests during resource ingestion.

Codebase learning scaffolds produce consistent study, extraction, audit, and teardown documents for a specific resource namespace. These templates serve as reference outputs to generate main study files and extraction tables for downstream governance and reuse.

Cross-pollination mapping generates structured mappings from a studied external resource into a target project. This enables effective knowledge reuse by capturing developer experience, governance rules, lifecycle hooks, and plugin manifests during resource ingestion.

Reference templates support audit reporting across resource namespaces by standardizing sidecar documentation artifacts. Running the resource workflow and selecting the corresponding templates under references generates consistent extraction tables for downstream governance and reuse.

Standardized sidecar documentation is needed when importing external codebases to prevent inconsistent, ad-hoc documentation. It enables repeatable study, cross-pollination mapping, and extraction of prompts, rules, tools, hooks, and plugins across resource namespaces.