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.
Scanned 9/12/2026
Install to Claude Code
npx -y skills add thedixitjain/the-mega-skill-library --skill frappe-builder --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Frappe Builder?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/thedixitjain-frappe-builder)More formats (shields.io, HTML) on the badges page.
---
name: frappe-builder
description: "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."
category: ai-agents-and-harness
source_repo: hashgraph-online/awesome-codex-plugins
source_path: "plugins/Dkm0315/frappe-agent/skills/frappe-builder/SKILL.md"
source_url: https://github.com/hashgraph-online/awesome-codex-plugins/blob/HEAD/plugins/Dkm0315/frappe-agent/skills/frappe-builder/SKILL.md
---
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`](https://github.com/hashgraph-online/awesome-codex-plugins) → `plugins/Dkm0315/frappe-agent/skills/frappe-builder/SKILL.md`
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!