[ VIBRISSE CORE ] — NAKED & AI-READY
Status: V1 Stable

IT SHIPS NAKED.

Built for a DA → Dev → Delivery workflow.
Zero bloat. Zero hard-coded styles.

[ Quick Start ]
/* Clone the skeleton */
git clone https://github.com/QuentinMerle/vibrisse-core.git wp-content/themes/vibrisse-core
/* Build the engine */
cd wp-content/themes/vibrisse-core
npm install && npm run dev

Don't change your habits.
Let the AI adapt.

Agencies don't have time to step back from production and learn "Prompt Engineering". vibrisse-core reverses the dynamic.

The repository is the prompt. You don't adapt to the AI; the AI adapts to your agency's standards. By reading the .ai/ folder, the AI natively enforces your strict boundaries: ACF Pro blocks, Tailwind v4, and native HTML architecture.

It's an incomplete skeleton, deliberately engineered so that AI can generate compliant business blocks in seconds, without you having to change how you work.

[ The Guardrails ]
  • 1
    Zero Native Gutenberg React. Use exclusively ACF Blocks architecture.
  • 2
    Zero hard-coded colors. Everything routes through theme.json.
  • 3
    Web-First Principle. Native HTML/CSS APIs > External libraries.
[ Proof of Concept: IDE Chat Log ]
Vibrisse Agent / Cursor Terminal
User Read the .ai/ context files. What are your operational constraints for this WordPress project?
⚡ Vibrisse AI

I have analyzed AGENTS.md and CONTEXT.md. My operational guardrails are incredibly strict:

  • Architecture: Zero native Gutenberg React. I must exclusively use the ACF Blocks architecture and enforce Local JSON syncing.
  • Design System: I am forbidden from using hard-coded hex colors or fonts. Every style must route through theme.json and Tailwind classes.
  • Web-First Principle: Before suggesting heavy JS libraries, I must use native HTML APIs (<details>, <dialog>).

Under these constraints, I am physically unable to generate "junk AI code". I am locked into your production-ready standards.

User Understood. Now, generate a 'Team Member' block. We need a photo, name, role, and a repeater for social links.
⚡ Vibrisse AI

Executing new-block skill strictly following guidelines...

  • ✔
    Created blocks/custom/team-member/block.json
  • ✔
    Created render.php using semantic <article> tag and wp_get_attachment_image() for lazy loading.
  • ✔
    Created style.css mapping BEM classes to Tailwind CSS variables.
  • ✔
    Generated acf-json/group_team_member.json with the requested Repeater field.

The block is automatically registered and restricted to your theme.json color palette. It is ready for the Gutenberg editor.

❯
[ Workflow Automation ]

1. Design Hydration

The DA delivers a Figma file. Trigger the AI to analyze the assets and instantly update theme.json and CLIENT.md. Zero manual CSS variables.

2. Block Generation

Need a custom block? "Create a Team block". The AI generates block.json, PHP render, styles, and the ACF Local JSON group instantly.

3. Smart Scaffolding

Run the new-cpt skill to generate a Custom Post Type, its Taxonomies, ACF relationships, and Full Site Editing HTML templates.

4. Headless Ready

WP as a pure backend. Trigger the export-headless skill to instantly convert any ACF FSE block into a React/Vue component fed by the REST API.

[ UNIVERSAL BLOCKS ]

The core covers 80% of brochure needs out of the box:

  • + Hero (Split & Centered)
  • + Media & Text
  • + Features Grid
  • + Call to Action
  • + Native HTML FAQ (Zero JS)
  • + Testimonials

[ PREDEPLOY PIPELINE ]

You don't ship until it's perfect.

Running npm run predeploy chains our strict quality contract before pushing to production:

1. Build & Optimize (Vite)
2. Lint (ESLint + Stylelint)
3. WP-CLI validation (ACF JSON)
4. Auto-generate llms.txt
CMS Engine
WP 6.4+ (FSE)
Architecture
ACF Pro + JSON
Design System
Tailwind v4
Build Tool
Vite 6 HMR