k-parent-mobile-agent

What problem does it solve?

Designing a user-friendly mobile parent agent for general users requires defining a clear product surface, mapping user commands to relevant domain-specific parenting skills, and implementing safety guardrails for write operations, which is time-consuming to build from scratch.

Core Features & Use Cases

• Product Surface Definition: Outlines the mobile home screen layout including daily child schedules, school notices, academy updates, upcoming application deadlines, and local event recommendations.
• Command Routing Mapping: Provides a pre-built mapping table to route common parent requests (e.g., "weekend plans", "homework check") to the correct k-parent domain skills.
• Safety Guardrails: Enforces a confirm-first workflow for all write actions like calendar updates, application submissions, and purchases to prevent unintended user actions.
• Use Case: A product team building a Korean parenting mobile app can use this skill to quickly define the agent's core structure, routing logic, and safety rules without building the entire workflow from scratch.

Quick Start

Use the k-parent-mobile-agent skill to design the product surface and command routing structure for a server-deployed mobile parent agent that serves general users with agentic parenting features.