| 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-07-10.
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.md start with #### followed by the signature.
- Class headings use
## ClassName.
- Event names are grouped in
events.md under ## Emitted events.
- Enum names are under
## Enum Types in enums.md.
