agntcms-init

Automating agntcms project setup involves wiping demo content, integrating design bundles, migrating tokens, and populating page JSONs. The agntcms-init skill orchestrates these tasks by coordinating specialized dependencies to populate headers, footers, and site metadata efficiently.

Design token migration extracts styling tokens from a design bundle and applies them to an agntcms project's theme file. This process ensures the newly initialized project matches the design specifications by translating design variables into usable theme configurations.

Yes, you can integrate a Claude Design bundle to populate agntcms page JSONs. The initialization process lifts content directly from design mocks, automatically filling in headers, footers, and site metadata to create a fully populated project structure.

Yes, project initialization requires multiple agntcms dependencies. The setup process relies on specialized skills like agntcms-structure, agntcms-sections, agntcms-content-fs, and agntcms-git-publish to handle specific tasks such as content freezing, section validation, and publishing.

Demo wipe clears the default placeholder content from a newly scaffolded agntcms project. This prepares a clean environment for integrating actual design bundles and migrating real content tokens without leftover demo data interfering with the new structure.

Content migration from design mocks to agntcms relies on automated extraction, which may require manual adjustments for complex layouts. The process populates standard elements like headers and footers but might need validation via agntcms-section-validate to ensure structural integrity.