<< All versions
Skill v1.0.1
Automated scan100/100wyyazlz/sheetnext/sheetnext-dev
+9 new
──Details
PublishedJuly 2, 2026 at 09:19 AM
Content Hashsha256:f8e3ea51088d8330...
Git SHAd35240a6fc3e
Bump Typepatch
──Files
Files (1 file, 2.1 KB)
SKILL.md2.1 KBactive
SKILL.md · 48 lines · 2.1 KB
version: "1.0.1" name: "sheetnext-dev" description: "Develop SheetNext spreadsheet apps and integrations. Use when building or debugging SheetNext workbook, sheet, cell, formula, event, import/export, JSON workbook data, template, AI relay, drawing, table, pivot, or slicer features."
SheetNext Development
Generated from SheetNext API docs on 2026-06-17.
Use the bundled references as the source of truth. Do not invent undocumented APIs.
Tool-specific setup notes live in adapters/; they are optional and do not change the API contract.
Read Order
- For normal spreadsheet development, read
references/core-api.md. - For events and hooks, read
references/events.md. - For constants and enum values, read
references/enums.md. - For JSON import/export data shape, read
references/json-format.md. - For built-in AI relay integration, read
references/ai-relay.md. - For common implementation patterns, read
references/recipes.md.
API Rules
- Public API is whatever appears in
references/core-api.md. - Deprecated APIs are excluded from the generated references; do not use undocumented old names.
- Internal SheetNext source members start with
_or#; avoid them unless the user is editing SheetNext internals. - Coordinates are zero-based when using numeric objects. A1 strings such as
"A1"are one-based Excel-style references. - Prefer existing SheetNext core APIs over direct DOM access or ad hoc state mutation.
- For templates, prefer
sheet.insertTemplate(...). - For import/export, use
SN.IO. - For events, use
SN.Event.
Workflow
- Identify the target object:
SN,Sheet,Cell,IO,Event, etc. - Search the reference docs for the exact method name and signature before coding.
- Generate the smallest working implementation first.
- State verification steps and any assumptions about the documented API.
Search Tips
- Method headings in
core-api.mdstart with####followed by the signature. - Class headings use
## ClassName. - Event names are grouped in
events.mdunder## Emitted events. - Enum names are under
## Enum Typesinenums.md.