メニュー
Frappe Gameplan guidance for team discussions, projects, tasks, notes, decisions, async collaboration, permissions, and workspace workflows. Use when work touches Gameplan or planning/collaboration features in the Frappe ecosystem.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
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.
Frappe CRM guidance for leads, deals, contacts, organizations, pipelines, activities, assignment, dashboards, and sales workflows. Use when work touches Frappe CRM or CRM-style sales processes in the Frappe ecosystem.
Frappe Drive guidance for files, folders, sharing, permissions, storage, previews, document workflows, and file-linked business processes. Use when work touches Frappe Drive or file management in the Frappe ecosystem.
ERPNext-aware reasoning for accounting, selling, buying, stock, manufacturing, projects, HR, support, education, CRM, and other ERPNext module work. Use when a task affects ERPNext module behavior, configuration, reports, dashboards, workflows, or customizations.
End-to-end Frappe and ERPNext implementation guidance spanning backend Python, backend JavaScript surfaces, Vue or React frontends, customizations, and bench-aware delivery. Use when the task crosses multiple Frappe layers.
Frappe Helpdesk implementation and customization guidance for ticket intake, SLAs, assignment, portals, knowledge base, notifications, and support workflows. Use when work touches the Frappe Helpdesk app or customer support operations.
| name | frappe-gameplan |
| description | Frappe Gameplan guidance for team discussions, projects, tasks, notes, decisions, async collaboration, permissions, and workspace workflows. Use when work touches Gameplan or planning/collaboration features in the Frappe ecosystem. |
Act as a Frappe Gameplan specialist.
First clarify:
Prefer configuration and metadata before code:
When implementing:
For UX, make ownership, due dates, blockers, recent decisions, and unread or pending activity easy to scan.
