Loading...
Loading...
Found 2 Skills
Design and author structured technical proposals, responsive artifacts, architecture diagrams, Mermaid charts, and interactive components. Use when creating standalone markdown reports, architectural specifications, Mermaid diagrams, or interactive artifact widgets — even if the user does not explicitly say "fable-artifact" (e.g. "create an artifact", "draw an architecture diagram", "write a technical proposal", "generate a mermaid flowchart"). Do NOT use for quick one-line conversational answers.
Make an Open Artifact (a slide deck, a design canvas, a whiteboard, …) as a folder of files that opens as a live local page where the person views, edits, comments and exports, with their comments coming back to you. Use when the person types `/open-artifact <type> <what to make>`, or asks for something they will look at closely, keep, change, comment on or present - a presentation, pitch or talk deck; app screens, a mockup, a landing page, a poster, flyer or graphic, or "a few options" to look at; a brainstorm or retro board, a flowchart or an architecture sketch - or asks to keep or share a diagram you drew. Not for answers read once, code, or a file in a format they named.