@qvac/skills 0.1.6 → 0.1.8

package/skills/diagrams/references/gantt.md

@@ -1,38 +0,0 @@
-# Gantt Chart
-
-For a schedule or plan with durations.
-
-Budget: 12 tasks across 4 sections.
-
-```mermaid
-gantt
-  title MVP delivery
-  dateFormat YYYY-MM-DD
-  excludes weekends
-  section Planning
-    Requirements      :a1, 2026-09-01, 5d
-    Design            :a2, after a1, 7d
-  section Build
-    Core platform     :b1, after a2, 21d
-    API               :b2, after a2, 17d
-  section Launch
-    Release           :c1, after b1, 2d
-```
-
-Rules:
-
-- The only header lines are `title`, `dateFormat YYYY-MM-DD`, `axisFormat`,
-  `excludes weekends`, and `section Name`. Nothing else is a header.
-- EVERY other line is a task and must be `Name :id, start, duration` - start
-  is a date or `after otherId`, duration is like `5d` or `2w`. A line that is
-  not one of these fails with `Expecting 'taskData'`.
-- No colons inside task names, no quotes, no arrows.
-- Ids are unique short tokens (`a1`, `b2`); `after` may name several ids
-  separated by spaces.
-
-## Now draw
-
-This recipe is all you need. Your next output is the reply itself: one fenced
-Mermaid code block (fence language `mermaid`), then one sentence. Do not call
-any tool - not `exec`, not `skill` again, not an image tool. A tool call here
-means the diagram was never drawn.

package/skills/diagrams/references/mindmap.md

@@ -1,35 +0,0 @@
-# Mindmap
-
-For a brainstorm or idea tree around one topic. Not for people in a hierarchy
-- that is a `flowchart TD`.
-
-Budget: 3 levels, 10 nodes, 2-4 balanced top-level branches.
-
-```mermaid
-mindmap
-  root[Launch plan]
-    Marketing
-      Blog post
-      Social campaign
-    Engineering
-      Release build
-      Monitoring
-```
-
-Rules:
-
-- The first line is `mindmap`; the second is the rectangular `root[Topic]`.
-- One node per line, two more spaces of indentation per level; the tree shape
-  comes only from indentation. Every line after `root[...]` is indented deeper
-  than the root - a line at the root's indentation is a second root and fails
-  with `There can be only one root`.
-- Labels are unquoted plain text with no ids, no quotes, no arrows,
-  no brackets except the `root[...]` form.
-- One node per item with its details in that node; no attribute leaves.
-
-## Now draw
-
-This recipe is all you need. Your next output is the reply itself: one fenced
-Mermaid code block (fence language `mermaid`), then one sentence. Do not call
-any tool - not `exec`, not `skill` again, not an image tool. A tool call here
-means the diagram was never drawn.

package/skills/diagrams/references/pie.md

@@ -1,27 +0,0 @@
-# Pie Chart
-
-For shares of a whole: hours in a day, budget split, percentages.
-
-Budget: 8 slices; combine the remainder as `"Other"`.
-
-```mermaid
-pie title Time spent
-  "Coding" : 60
-  "Review" : 25
-  "Meetings" : 15
-```
-
-Rules:
-
-- The first line is `pie title Your title` (or just `pie`).
-- Every slice is `"Label" : number` - the label in plain double quotes typed
-  directly (never unquoted, never with a backslash in front), then a
-  space-colon-space, then a plain number with no unit or `%` sign.
-- One slice per line; values need not add up to 100.
-
-## Now draw
-
-This recipe is all you need. Your next output is the reply itself: one fenced
-Mermaid code block (fence language `mermaid`), then one sentence. Do not call
-any tool - not `exec`, not `skill` again, not an image tool. A tool call here
-means the diagram was never drawn.

package/skills/diagrams/references/sequence.md

@@ -1,32 +0,0 @@
-# Sequence Diagram
-
-For who calls whom over time: requests and replies between an app, a server,
-a browser, a service.
-
-Budget: 5 participants and 12 messages.
-
-```mermaid
-sequenceDiagram
-  participant App
-  participant Server
-  App->>Server: POST /login
-  Server-->>App: 200 with token
-  Note over App: stores the token
-```
-
-Rules:
-
-- Declare every `participant` first, as a bare name without quotes.
-- A call is `A->>B: message`; a reply is `B-->>A: message`. Never use the
-  flowchart `-->` arrow here.
-- A note is `Note over A: text` (or `Note over A,B: text`).
-- Message text follows the colon unquoted; keep it short. No backslashes anywhere.
-- No ids, no brackets, no `end` except to close a Mermaid `loop`/`alt` block
-  you opened.
-
-## Now draw
-
-This recipe is all you need. Your next output is the reply itself: one fenced
-Mermaid code block (fence language `mermaid`), then one sentence. Do not call
-any tool - not `exec`, not `skill` again, not an image tool. A tool call here
-means the diagram was never drawn.

package/skills/diagrams/references/state.md

@@ -1,30 +0,0 @@
-# State Diagram
-
-For modes and transitions: a device, a job, a session moving between states.
-
-Budget: 8 states.
-
-```mermaid
-stateDiagram-v2
-  [*] --> Idle
-  Idle --> Running : start
-  Running --> Idle : stop
-  Running --> [*] : shutdown
-```
-
-Rules:
-
-- The first line is exactly `stateDiagram-v2`.
-- `[*]` is both the start and the end marker.
-- A transition is `From --> To : label`; the label is optional and follows a
-  colon, unquoted.
-- State names are single words or `snake_case`; for a spaced display name use
-  `state "Waiting for input" as Waiting` once, then `Waiting` everywhere.
-- No backslashes, no `classDef`, no `%%` lines.
-
-## Now draw
-
-This recipe is all you need. Your next output is the reply itself: one fenced
-Mermaid code block (fence language `mermaid`), then one sentence. Do not call
-any tool - not `exec`, not `skill` again, not an image tool. A tool call here
-means the diagram was never drawn.

package/skills/diagrams/references/timeline.md

@@ -1,28 +0,0 @@
-# Timeline
-
-For dated events in order: a history, a roadmap already dated.
-
-Budget: 8 events.
-
-```mermaid
-timeline
-  title Product history
-  2024 : Prototype
-  2025 : Public beta : First paying customers
-  2026 : Version 1.0
-```
-
-Rules:
-
-- `title` first, then one line per period as `period : event`, with another
-  ` : event` for each extra event in the same period.
-- Periods are years, dates, or short phase names; events are short unquoted
-  text.
-- No arrows, no ids, no quotes.
-
-## Now draw
-
-This recipe is all you need. Your next output is the reply itself: one fenced
-Mermaid code block (fence language `mermaid`), then one sentence. Do not call
-any tool - not `exec`, not `skill` again, not an image tool. A tool call here
-means the diagram was never drawn.