Generate state machine logic for Frappe DocTypes. Use when implementing complex status workflows, state transitions, or document lifecycle management.
Generates state machine logic for Frappe DocTypes with validation and state-dependent actions.
/plugin marketplace add Venkateshvenki404224/frappe-apps-manager/plugin install frappe-apps-manager@frappe-marketplaceThis skill inherits all available tools. When active, it can use any tool Claude has access to.
Generate state machine logic for managing complex document states and transitions in Frappe DocTypes.
Claude should invoke this skill when:
Order Status State Machine:
class SalesOrder(Document):
def validate(self):
self.validate_state_transition()
def validate_state_transition(self):
"""Validate allowed state transitions"""
if not self.is_new():
old_status = frappe.db.get_value('Sales Order', self.name, 'status')
# Define allowed transitions
allowed_transitions = {
'Draft': ['Pending', 'Cancelled'],
'Pending': ['Confirmed', 'Cancelled'],
'Confirmed': ['In Progress', 'Cancelled'],
'In Progress': ['Completed', 'On Hold'],
'On Hold': ['In Progress', 'Cancelled'],
'Completed': [], # Terminal state
'Cancelled': [] # Terminal state
}
if old_status != self.status:
allowed = allowed_transitions.get(old_status, [])
if self.status not in allowed:
frappe.throw(
_(f'Cannot transition from {old_status} to {self.status}')
)
def on_submit(self):
self.status = 'Confirmed'
def on_cancel(self):
self.status = 'Cancelled'
Actions Based on State:
class PaymentEntry(Document):
def validate(self):
if self.status == 'Draft':
self.validate_draft_entry()
elif self.status == 'Submitted':
self.validate_submitted_entry()
def before_submit(self):
# Actions before state change
if self.payment_type == 'Pay':
self.validate_sufficient_balance()
self.status = 'Submitted'
def on_cancel(self):
# Reverse actions
if self.status == 'Submitted':
self.reverse_gl_entries()
self.status = 'Cancelled'
State Management Examples:
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.