Automated summary
Documents the .boardkit file format — a ZIP archive holding package.json and board.json — along with its deterministic serialization, versioning and migration functions.
Strengths
- Precisely describes the ZIP layout and expected JSON schemas
- Includes a constraints table (50 MB max, DEFLATE level 6, UTF-8)
- Lists serialization rules plus atomic-write and transactional storage strategies
- Points to the key files for document types, migrations and storage backends
Limitations
- Tied to the Boardkit project; not reusable outside that repository
- Covers only import/export and persistence, not board content editing
- Schemas are shown as excerpts rather than a full formal validation spec
Use when changing the .boardkit format, import/export logic, persistence layers, or adding a document version migration.
Avoid it for work unrelated to the file format or storage, such as rendering widgets visually.
Security analysis
SafeThe skill is purely informational, describing a file format and related development practices. It only uses read-only tools (Read, Grep, Glob) and contains no executable commands, destructive actions, or data exfiltration.
No concerns found
How this analysis is madeExamples
Add a new formatVersion 3 that introduces a 'comments' array in board.json, write the migrateV2ToV3 function in packages/core/src/migrations/index.ts and add tests alongside the existing migration tests.The .boardkit importer in apps/web/src/utils/boardkitFile.ts accepts files over 50 MB — review the import validation checklist and make the size and ZIP structure checks fail cleanly.Our exported .boardkit files differ between runs. Check the serialization rules for key sorting and random IDs and make the export deterministic on both web and desktop.name: boardkit-file-format description: | .boardkit file format: ZIP structure, serialization, versioning, migrations. Use when working on import/export, persistence, or file format changes. allowed-tools: Read, Grep, Glob
Boardkit File Format
Structure
.boardkit = ZIP archive containing:
my-board.boardkit (ZIP)
├── package.json → Metadata
└── board.json → Document content
package.json
{
"name": "my-board",
"version": "1.0.0",
"boardkit": {
"formatVersion": 2
}
}
board.json
{
"version": 2,
"meta": {
"title": "My Board",
"createdAt": "2024-01-01T00:00:00Z",
"updatedAt": "2024-01-02T00:00:00Z"
},
"board": {
"viewport": { "x": 0, "y": 0, "zoom": 1 },
"widgets": [...],
"elements": [...],
"background": { "type": "dots", "color": "#f5f5f5" }
},
"modules": {},
"dataSharing": {
"permissions": [],
"links": []
}
}
Constraints
| Constraint | Value |
|------------|-------|
| Max file size | 50 MB |
| Compression | DEFLATE level 6 |
| Extension | .boardkit |
| JSON encoding | UTF-8 |
Document Versions
| Version | Changes |
|---------|---------|
| v0 | Initial: widgets only |
| v1 | Added: elements[], background |
| v2 | Added: dataSharing section |
Migration Functions
// packages/core/src/migrations/index.ts
function migrateV0ToV1(doc: V0Document): V1Document {
return {
...doc,
version: 1,
board: {
...doc.board,
elements: [],
background: { type: 'dots', color: '#f5f5f5' }
}
}
}
Serialization Rules
-
Deterministic - Same input = same output
- Sort object keys alphabetically
- No random IDs in output
-
Atomic writes (Desktop)
- Write to temp file first
- Rename to final path
-
Transactions (Web/IndexedDB)
- Use IDB transactions
- Rollback on error
Storage Implementations
Web (IndexedDB)
// packages/platform/src/storage/indexeddb.ts
Database: 'boardkit'
Stores: 'documents', 'history'
Autosave: 500ms debounce
History cap: 100 entries
Desktop (Tauri FS)
// apps/desktop/src/composables/usePersistence.ts
Autosave: 1000ms debounce
Atomic writes via temp file
Import Validation
// Required checks on import
1. File size < 50MB
2. Valid ZIP structure
3. package.json exists and valid
4. board.json exists and valid JSON
5. Version supported (migrate if needed)
6. Schema validation
Key Files
| Purpose | Path |
|---------|------|
| Document types | packages/core/src/types/document.ts |
| Migrations | packages/core/src/migrations/index.ts |
| Web import/export | apps/web/src/utils/boardkitFile.ts |
| Desktop import/export | apps/desktop/src/utils/boardkitFile.ts |
| IndexedDB storage | packages/platform/src/storage/indexeddb.ts |
| Migration tests | packages/core/__tests__/migrations.test.ts |
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/boardkit-file-format-mmh8qr08/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/boardkit-file-format-mmh8qr08' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/boardkit-file-format-mmh8qr08/download' --output '.skill-downloads/boardkit-file-format-mmh8qr08/SKILL.md.part' && mv '.skill-downloads/boardkit-file-format-mmh8qr08/SKILL.md.part' '.skill-downloads/boardkit-file-format-mmh8qr08/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
Tools declared by the author (check availability in your agent): Read, Grep, Glob
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/boardkit-file-format-mmh8qr08/SKILL.md' && test -s '.skill-downloads/boardkit-file-format-mmh8qr08/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/boardkit-file-format' && cp -R '.skill-downloads/boardkit-file-format-mmh8qr08' '.claude/skills/boardkit-file-format'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/boardkit-file-format-mmh8qr08'openskills read 'boardkit-file-format-mmh8qr08'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/boardkit-file-format-mmh8qr08/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.