Stashiro

View saved version →

---
name: compose-stashiro-board
description: Use when Stashiro is selected or mentioned to present, plan, analyze, compare, create, save, add, edit, move, connect, or organize visual board content.
---

# Compose a Stashiro board

Stashiro organizes content as Space > Board > Card. A canvas board supports freely positioned visual cards; a list board supports a linear bento-style collection.

1. Choose the mode from the request. When Stashiro is selected for a plan, analysis, comparison, research synthesis, or another multi-item answer, the answer is the native card presentation; do any needed research first, then present it without saving instead of returning the deliverable only as prose. For an explicit create or save request, prepare the same reviewable composition and let the user confirm its destination in the Stashiro UI. Use direct write tools only for a small targeted change to an existing board.
2. Choose one primary organizing axis: time, topic, entity, workflow stage, audience, location, or another relation the user will navigate. Make one named `section` for each useful unit. A table may compare units, but does not replace sections people need separately.
3. Make each note about one subject. Keep an ordinary note under 60 words. Split independent resources, facts, decisions, or actions. A resource note describes one resource and sits with its link. Use a short overview only for synthesis that applies to the whole result.
4. Build one section at a time in reading order. Put its note, source link, native card, and action together before starting the next section. Never batch cards by type or move all links to the end. Use every card index in exactly one section.
5. For a new multi-card answer or composition, call `present_stashiro_cards` once with the final ordered cards and sections. This is the final native Stashiro answer after any research, not an intermediate reasoning step or an optional duplicate of a prose answer. It does not save until the user confirms the destination in its UI.
6. For a small direct edit or addition, use `create_card` for short headings and notes. Use `create_link_card`, `create_table_card`, `create_chart_card`, `create_flight_card`, `create_map_card`, `upload_image_card`, and `create_connector` for their native content. Prefer a table for comparable records and a chart when the visual pattern matters more than exact lookup.
7. A flight-tracking URL requires a flight card with the original URL in `sourceUrl`. Use sourced offset timestamps and live status only when provided. Never infer flight status.
8. Use an image card only for a user-requested attached or generated image. Ask which image when several candidates match. Never pass a local path or add decorative media without a request.
9. Use a connector only when direction, sequence, dependency, or another relation should remain visible after cards move. Use `arrow` for direction, `plain` for a neutral relation, and `dashed` for a tentative or indirect relation.
10. For direct canvas writes, use `layout-stashiro-board` before supplying geometry and verify the result afterward. `present_stashiro_cards` and `save_capture` preserve section grouping without model-supplied coordinates.
11. Resolve a destination only for persistent work. Use `search` for a named destination and accept a unique match only when its subject fits. Never treat the only match as relevant by default. Ask for an existing Space or permission before `create_space`. Use `create_board` with the exact Space reference. Default to `canvas`; use `list` only for a linear collection.
12. Use `update_card`, `move_card_to_board`, `reorder_cards`, or `delete_card` only for the requested direct change. Before moving a connected card, inspect its connectors and preserve only relationships that still make sense.
13. Use `show_selected_stashiro_cards` for existing identified cards that have not appeared in the current response and `show_stashiro_board` for an unfiltered board page. Return exact board links after writes.

View saved version →

---
name: convert-to-stash
description: Use when the prompt contains /convert-to-stash, or the user explicitly asks to convert an existing answer or conversation into reviewable native Stashiro cards.
---

# Convert conversation content to Stashiro

The literal `/convert-to-stash` token converts content already present in the conversation. It does not request new research, search saved Stashiro content, or authorize saving.

1. When the user sends `/convert-to-stash`, immediately call `present_stashiro_cards` with useful completed content from the conversation. If the command asks for a specific focus or identifies a message or range, answer that request from the existing conversation. Otherwise produce a concise answer-shaped summary of the conversation, using the latest substantive completed answer as the primary source. Do not repeat the analysis outside the tool, browse the web, call `search`, or add facts. If no substantive prior content exists, ask which content to convert.
2. Build ordered `sections` so the result reads as one coherent answer. Give each section only the heading and connecting prose it needs, then place the relevant zero-based `cardIndexes` directly after that prose. Use every card index exactly once. Do not repeat full card details in the prose.
3. Preserve the source content and its organizing axis. Keep an ordinary note under 60 words and about one subject; split independent facts, resources, decisions, or actions. Create each source link in the same section, immediately with the item it supports, rather than batching links after notes. Use a table or chart for structured comparisons, a map only when coordinates exist, a flight only when its required details exist, and an image only for supplied files. When a specialized card lacks required data, use a note or table instead of researching or inventing it.
4. Pass `preferredBoardId` only when the destination is known. Use returned Spaces to suggest a clearly relevant destination, or suggest a new Space name when none fits.
5. Call `save_capture` only with the exact board, cards, and sections confirmed in the capture UI. Reuse its payload and a stable `requestId` so retries remain idempotent and semantic groups survive saving.
6. Report `savedCount`, the destination board name, and the exact `boardUrl`. Do not expose temporary image download URLs or internal file identifiers.

View saved version →

---
name: find-stashiro-content
description: Use when Stashiro is selected, mentioned, or already active and the user asks to find, retrieve, browse, or display saved information; locate a Space, board, card, media item, or flight; or continue a Stashiro retrieval task.
---

# Find Stashiro Content

Stashiro organizes content as Space > Board > Card. Spaces group boards; boards hold notes, tables, charts, images, links, flights, and other native cards.

1. Use saved-content search only when the user explicitly asks to find, show, read, retrieve, or inspect existing Stashiro content. A new analysis, plan, comparison, or recommendation does not belong to saved-content search. A `/convert-to-stash` request belongs to `convert-to-stash` unless it also explicitly asks to read saved content. Continue related retrieval follow-ups without requiring another tag.
2. While active, unqualified names and `Space`, `board`, or `card` refer to Stashiro. Interpret `A > B` or `A / B` as Space `A`, board `B`.
3. Use `search` to locate saved Stashiro content by name or content. It returns matching Spaces and boards and renders matching cards in their native UI. Use optional Space or board scope when supplied. Use returned IDs and card data as inputs to any remaining steps in the user's request. Act on a unique match; otherwise present relevant matches or ask a focused question. When `isPartial` is true, say the results are partial and narrow the next search.
4. Do not present the same card twice: `search` already renders its card matches. Use `show_selected_stashiro_cards` when card IDs or opaque references are already known and those cards have not appeared in the current response. Present cards from different boards in separate calls.
5. Use `fetch` only with an ID returned by `search` when full data is needed for reasoning. Use `get_space`, `get_board`, or `get_card` when an exact resource ID is already known.
6. Use `browse_all_stashiro_spaces_and_boards` for the workspace or `browse_one_stashiro_space` for one Space only when the user asks to browse. Follow every returned cursor until the requested scope is complete. Never browse to resolve a destination for a write.
7. Use `list_cards` for lightweight summaries, `show_stashiro_board` for an unfiltered board page, and `show_selected_stashiro_cards` for a requested subset. Continue board pages while `isDone` is false.
8. Use `get_card_media` only when the user needs the underlying image or audio. Its URL is short-lived; do not present it as permanent.
9. Do not infer that content is absent outside the searched scope. Report what was searched and return exact `boardUrl` links when available.

View saved version →

---
name: layout-stashiro-board
description: Use whenever a Stashiro canvas operation must choose, verify, or change card coordinates, dimensions, spacing, alignment, or layers; when adding or editing near existing content; when repeated additions may overlap; or when asked to arrange, distribute, tidy, or stop cards from hiding each other.
---

# Layout a Stashiro board

Use this skill for direct canvas geometry. Content skills decide what to create or change; this skill decides where it fits and verifies the result. A reviewed multi-card composition saved through `save_capture` already uses its semantic sections for collision-free placement. List boards use distribution order instead.

1. Before supplying or changing `x`, `y`, `width`, or `height`, call `list_cards` on the destination board and follow `cursor` until `isDone` is true. Use every non-connector card's returned geometry as an occupied rectangle.
2. Identify the content groups and their reading order before choosing coordinates. Preserve an established grouping when editing. Give every time period, topic, entity, stage, or other independently useful unit its own bounding area; do not substitute a card-type row for those groups.
3. Lay out one complete group before the next. Mix card types inside it: put each source link beside or below the note, comparison, map, or action it supports. Keep alternatives with their comparison. Never create a board-wide link row, note row, image row, or table row unless card type is itself the subject.
4. Keep 40 to 64 pixels between cards in one group and at least 112 pixels between groups. Use a short text heading when a group boundary would otherwise be unclear. Preserve user-supplied coordinates unless they hide another card or break an explicit group.
5. When dimensions are absent, estimate a conservative footprint: text 240 x 48, note 220 x 220, link 400 x 280, image 320 x 240, table 440 x 240, chart 440 x 300, and flight 460 x 280. Size cards for readable content and consistent peers. Do not shrink a card to force it into a gap.
6. Never reuse a generic origin or board-center position without checking collisions. Continue an existing group for repeated additions. Place a new group beside or below occupied board bounds without moving unrelated cards.
7. After each group and again after the full write, call `list_cards` through completion. Fail the layout when cards overlap substantially, one card hides another, a group mixes unrelated subjects, or a supporting card is visually closer to unrelated content than to its subject. Also fail when cards were arranged by type instead of by meaning.
8. Fix a failed layout by moving or resizing new and modified cards first. Preserve unrelated positions and `stackIndex` values. Use `reorder_cards` only when layer order is part of the requested arrangement. Recheck until cards are readable and the spatial grouping matches the content structure.

View saved version →

---
name: manage-stashiro-workspace
description: Use when the user asks to organize Stashiro workspace content by renaming, moving, pinning, reordering, trashing, restoring, or permanently deleting a Space, board, or card.
---

# Manage a Stashiro Workspace

Use this workflow for workspace organization and lifecycle changes, not for reading or composing card content.

1. Resolve named targets with `search`. Use an exact known ID directly. Never browse solely to validate a write destination, and never guess between duplicate names.
2. Use `rename_space`, `set_space_icon`, and `reorder_spaces` for Space metadata and sidebar order. Use `rename_board`, `move_board`, `set_board_pinned`, `reorder_pinned_boards`, and `reorder_boards_in_space` for board organization.
3. Use `move_card_to_board` for one card and `reorder_cards` for canvas layers or list distribution. Whenever a move or resize needs canvas geometry, also use the `layout-stashiro-board` skill and verify the result. Preserve every unrelated card and ordering value.
4. Prefer `trash_board` for removable boards because it is recoverable. Use `restore_board` to undo that operation.
5. Before `delete_board_permanently`, restate the exact board and that every card will be irreversibly deleted. Call it only after the user clearly confirms permanent deletion.
6. Before `delete_card`, restate the exact card when identity is not already unambiguous. The deletion is permanent.
7. Before `delete_space`, restate the exact Space and ask for confirmation. Explain that the Space is removed and every board still inside it moves to Trash. Boards moved elsewhere first are preserved.
8. After successful board or card changes, return exact `boardUrl` or `affectedBoards` links. Report deleted IDs without inventing links to deleted resources.