메뉴
Understand what UI fragments are, browse existing fragments, and read their specs. Use when users ask what fragments are, want to list or inspect existing fragments, or need to understand the fragment system.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | fragments |
| description | Understand what UI fragments are, browse existing fragments, and read their specs. Use when users ask what fragments are, want to list or inspect existing fragments, or need to understand the fragment system. |
| tools | ["fragment_list","fragment_read"] |
Fragments are self-contained, versioned UI definitions built as json-render specs. They can be embedded anywhere in the Daycare app.
A fragment is a JSON-based component tree that describes a piece of UI. Each fragment has:
Fragments are stored server-side, versioned automatically, and rendered natively on iOS and Android.
The spec defines a tree of components. Each element has a type (from the widget catalog), props, and children. Elements are keyed by unique string IDs in an elements map, with a root field pointing to the top-level element.
Fragments can hold state via the /state field in the spec. Components read from state using { "$state": "/path" } and bind two-way with { "$bindState": "/path" }. State drives dynamic content, visibility conditions, and interactive behavior.
Optional spec.code adds interactivity. An init() function runs on load, and named action functions handle events. Code runs sandboxed with a 5s time limit and 10 MB memory cap.
The repeat field on elements renders children once per item in a state array, using { "$item": "field" } and { "$index": true } to access item data.
Elements can have a visible field (top-level, not inside props) to conditionally show/hide based on state comparisons.
fragment_list — list all fragments for the current userfragment_read — read a specific fragment's full spec by IDFor creating or modifying fragments, use the fragments-creator skill instead.
Create and update robust Daycare tasks (task_create/task_update + task_trigger_add) and permanent agents (create_permanent_agent) with minimal Python orchestration, explicit parameter schemas, reproducible exec/process usage, and performance-first skip() behavior. Use when users ask for cron/webhook automation, recurring checks, scheduled reports, permanent agents, or resilient background task workflows.
Create reusable Daycare voice agents with the hidden-by-default `voice_agent_create` tool. Use when users want a new voice persona, a realtime call prompt, client-side voice tools, or a saved voice agent that appears in the app Voice screen.
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Daycare's capabilities with specialized knowledge, workflows, or tool integrations.
Understand what Daycare tasks are, how cron and webhook triggers work, and when to use each. Use when users ask about tasks, scheduling, triggers, or want to inspect existing tasks.
Friendship mechanics for daycare agents. Use when the user wants to add friends, manage friend requests, send messages to friends, share or unshare subusers with friends, or understand what nametags are.
Work with user-scoped PostgreSQL databases (PGlite). Use when the user asks to store structured data, create tables, query rows, track records, build a database, or manage any tabular/relational information. Covers database creation, additive schema design, CRUD operations, and SQL queries.