Skip to content
cccskills
FreePublished on GitHub

svg

Author and edit `.svg` files in a Grida editor session — live-canvas binding, SVG output style, and parse-error recovery. Use when creating or modifying an SVG document.

The English summary is being prepared. Showing the original description.

gridaco/grida
See how to install

Files included (1)

  • SKILL.md2.4 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

When you operate on .svg files inside a Grida editor session:

  • Writes are reflected on the canvas instantly if the human is currently viewing that document. Treat the canvas as a live render of what you wrote.
  • You may create and edit non-SVG files (e.g. /notes/draft.md) for your own scratch work — they persist across turns but do NOT render on the canvas.
  • On edit_file reason="parse_error", your output broke the SVG. Re-read and fix.

Show the result

  • Treat presentation as the first production milestone, not the final "validate and open" step. For a new standalone SVG, write a meaningful valid first frame with the intended dimensions and basic visible composition, call surface_open immediately with its workspace-rooted path (for example, /poster.svg), then continue adding and refining details while the user can watch. Do not wait for complete content, polish, preview generation, exhaustive validation, or task completion. For nontrivial work, intentionally start with the basic frame instead of authoring the finished SVG before opening it.
  • Never open an empty or invalid SVG. For an existing primary SVG, open it before substantial edits.
  • Open a standalone SVG by its file path. When the SVG belongs to a .canvas board or deck, the board/deck skill owns presentation: open the .canvas bundle directory once its manifest references a valid document, never the internal SVG or .canvas.json manifest.
  • If the standalone SVG or .canvas bundle is already mounted at the dedicated file surface's root, it is already presented; do not call surface_open just to reopen it.
  • Treat presentation as auxiliary: continue regardless of the result, never retry based on presentation status, and do not call surface_open after every write.
  • Use surface_list_open only when the current host surface state is materially useful. It is not required before surface_open.

SVG style

When you produce SVG:

  • Keep xmlns="http://www.w3.org/2000/svg" on the root element.
  • Preserve existing viewBox, width, height unless asked.
  • Preserve unrelated nodes and attributes (ids, classes, transforms).
  • Match the existing formatting (one element per line, 2-space indent).

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

agent-system

Free

Grida AI agent system work: `@grida/daemon` (DaemonServer, loopback HTTP perimeter, files/workspaces, secrets store, daemon discovery) and `@grida/agent` (the agent tenant: sessions, providers/BYOK, runtime/tool execution, skills discovery, prompts, tiers, sandbox hosts). Use for `packages/grida-daemon/**`, `packages/grida-ai-agent/**`, desktop sidecar protocol changes, agent chat transport, and bugs in agent state or streams. For pure Electron window, preload, menu, deep-link, or CDP work, use `desktop`.

The English summary is being prepared. Showing the original description.

gridaco/grida2.7KUpdated Oct 15, 2026

ai-models

Free

Research, compare, and update shared AI model JSON for TypeScript, web, and Rust consumers. Covers text model tiers, image and video generation models, image tool models, release provenance, pricing data sourcing, and product-side catalogue cost estimates. Use when bumping model versions, adding new models, updating pricing, or auditing model specs against provider documentation.

The English summary is being prepared. Showing the original description.

gridaco/grida2.7KUpdated Oct 15, 2026

code-react

Free

React-specific code shape in the Grida editor. Hooks cannot be tested or benchmarked and silently break tuned UX under layered composition, so they are barred from the engine and main system — load-bearing logic lives in classes and namespaces, hooks only as thin edge wires. `data-testid` follows component-root discipline: one per significant component, not scattered. Use when authoring React in `editor/grida-canvas-react/`, `editor/components/`, `editor/scaffolds/`, or `editor/app/*`.

The English summary is being prepared. Showing the original description.

gridaco/grida2.7KUpdated Oct 15, 2026

code-ts

Free

TypeScript code shape inside a well-named module — taste, not lint. Prefer one class or namespace per file (the unit a test targets) over scattered free exports; consolidate related code, don't fragment. The unit of code should be the unit of spec. Use when authoring TS in `editor/grida-canvas*`, `editor/lib/`, or `packages/*`. Sibling to the `naming` skill; React-specific shape lives in `code-react`.

The English summary is being prepared. Showing the original description.

gridaco/grida2.7KUpdated Oct 15, 2026

database

Free

Use BEFORE editing any file in `supabase/migrations/` or `supabase/schemas/`, OR when the user runs a `/database` subcommand (`compact local migration`, `rls scenarios`, `align`). Encodes the three contracts that protect the Grida database layer: applied migrations are immutable, RLS implementation mirrors tests (never the reverse), `schemas/*.sql` is the human-readable end-state. Companion to `supabase/AGENTS.md` (RLS, grants, security boundaries).

The English summary is being prepared. Showing the original description.

gridaco/grida2.7KUpdated Oct 15, 2026

desktop

Free

Grida Desktop Electron shell and release-impact work: BrowserWindow, preload, `window.grida`, menus, protocol/deep links, file associations, Forge, path-scoped bridge security, Electron-only UI bugs, and CDP / Playwright verification. Use for `desktop/`, `editor/app/desktop/**`, `editor/scaffolds/desktop/**`, `editor/lib/desktop/**`, `/desktop/*` CSP, GRIDA-SEC-004, and deciding whether linked-package or hosted-renderer changes require a native Desktop version bump or coordinated release. For implementing daemon/agent-tenant core behavior, use `agent-system` as well.

The English summary is being prepared. Showing the original description.

gridaco/grida2.7KUpdated Oct 15, 2026

See all skills by gridaco

Report a problem with this skill