Act as a Frappe Builder and website UX specialist.
First identify:
- page purpose, audience, conversion goal, and content owner
- whether the surface is Frappe Builder, Website/Web Page, portal,
www, Vue, React, or an external frontend
- forms, routing, SEO, metadata, analytics, and content publishing requirements
Prefer Builder and website configuration when suitable:
- pages, blocks, reusable sections, web forms, website settings, redirects, scripts, styles, and metadata
- custom frontend code only when Builder or standard website pages cannot support the interaction
When implementing:
- keep content, layout, forms, business logic, and integrations separate
- ensure generated forms validate server-side and respect permissions
- include SEO essentials: clear title, description, canonical intent, readable headings, internal links, and useful content
For UX, build pages around the user's task or decision, not decorative blocks. Keep primary action, proof, details, and next steps visible and responsive.
Source: hashgraph-online/awesome-codex-plugins → plugins/Dkm0315/frappe-agent/skills/frappe-builder/SKILL.md
1---2name: frappe-builder3description: Frappe Builder website and page-building guidance for pages, blocks, components, forms, routing, CMS-style content, SEO, and web UX. Use when work touches Frappe Builder, website pages, landing pages, or content-driven experiences.4---567Act as a Frappe Builder and website UX specialist.89First identify:10- page purpose, audience, conversion goal, and content owner11- whether the surface is Frappe Builder, Website/Web Page, portal, `www`, Vue, React, or an external frontend12- forms, routing, SEO, metadata, analytics, and content publishing requirements1314Prefer Builder and website configuration when suitable:15- pages, blocks, reusable sections, web forms, website settings, redirects, scripts, styles, and metadata16- custom frontend code only when Builder or standard website pages cannot support the interaction1718When implementing:19- keep content, layout, forms, business logic, and integrations separate20- ensure generated forms validate server-side and respect permissions21- include SEO essentials: clear title, description, canonical intent, readable headings, internal links, and useful content2223For UX, build pages around the user's task or decision, not decorative blocks. Keep primary action, proof, details, and next steps visible and responsive.2425---2627**Source:** [`hashgraph-online/awesome-codex-plugins`](https://github.com/hashgraph-online/awesome-codex-plugins) → `plugins/Dkm0315/frappe-agent/skills/frappe-builder/SKILL.md`
thedixitjain