How to use the CLAUDE.md templates
What is in the collection, how the files are split between CMS, e-commerce and headless, how to install a template in a project and which placeholders to fill in.
Guidelines
Configs, AI skills and templates for license holders
A knowledge base for developers working with ContextAdmin: ready-made CLAUDE.md templates for CMS and shop platforms, shared rules for SEO, GEO, performance and accessibility, and configurations to download.
Available to license holders
Log in to the account you used to buy your ContextAdmin license. Downloads and full guides unlock as soon as you are signed in.
Start here
How the templates are built, how to install one in a project and what to fill in.
CMS
Content management systems: WordPress, Joomla, Drupal, Ghost and TYPO3. Each system has a full theme variant, a zero-JS variant and an extension variant.
- WordPressSix front-end variants for one CMS: expert site, vanilla JS, Alpine, React with the Interactivity API, Vue islands and zero JS. All share the WordPress base rules.7 guidelines
- Joomla 5Site template on Cassiopeia or from scratch, a zero-JS template and a namespaced extension package.4 guidelines
- Drupal 10/11Theme with Single Directory Components, zero JS for anonymous users, a custom module and a JSON:API back end for Next.js.5 guidelines
- GhostHandlebars theme with members and newsletter, a publishing-only zero-JS theme and the Content API behind Astro or Next.js.4 guidelines
- TYPO3 12/13Site package with Fluid, Site Sets and Content Blocks, a zero-JS site package and a custom extension.4 guidelines
E-commerce
Shop platforms: WooCommerce, PrestaShop, Magento, OpenCart, Shopware, Sylius and Shopify. Themes, modules and headless setups.
- WooCommerceShop on WordPress. An add-on that you append to any WordPress variant except zero JS.1 guideline
- PrestaShopChild themes of classic (PS 1.7/8) and hummingbird (PS 8/9) plus a custom module with back-office configuration.4 guidelines
- Magento 2Hyvä theme for new shops, Luma theme for existing ones and a custom module that works with both front-end stacks.4 guidelines
- OpenCart 4Theme as an extension with Twig overrides and extensions: module, payment, shipping, feed.3 guidelines
- Shopware 6Storefront theme with Twig blocks, a plugin with entities and an admin module, and the Store API behind Shopware Frontends or Next.js.4 guidelines
- Sylius 2Shop theme with Twig Hooks and Symfony UX, and a plugin for resources, grids and API Platform.3 guidelines
- ShopifyOnline Store 2.0 theme in Liquid. Hosted platform, so only the theme repository applies.1 guideline
Headless and static
Front ends that take content from an API or build it into static files: Next.js in front of a CMS or shop, and Astro.
Shared rules
Rules every template imports: SEO and GEO, Core Web Vitals, accessibility, unslop, security and no-JS patterns. Copied to .claude/rules/ in the project.
SEO and GEO: technical SEO, content for intent, structured data, AI visibility
Technical SEO, content written for intent, structured data, GEO (visibility in AI answers), AI bots and multilingual sites.
Performance: Core Web Vitals, budgets, images, fonts, cache
Core Web Vitals, performance budgets, images, fonts, CSS, JS, cache and how to measure.
Accessibility: WCAG 2.2 AA in practice
Semantics, keyboard, ARIA, forms and motion. The rules that make a page usable with a screen reader and without a mouse.
Unslop: how not to build a site that looks and reads as generated
Design brief, the list of AI tells in layout and copy, rules for text, including Polish-language patterns.
Security: escaping, forms, headers, secrets, uploads, dependencies
Escaping output, protecting forms, HTTP headers, where secrets live, safe uploads and dependency hygiene.
Zero-JS patterns: menu, FAQ, tabs, carousel, form, lightbox, dark mode
Menu, FAQ, tabs, carousel, form, lightbox, video, map, dark mode and analytics without JavaScript. Imported by every zero-JS variant.