This skill documents proper Tiptap API usage patterns for vmark development. It helps distinguish when to use Tiptap's high-level API vs direct ProseMirror access.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versiontiptap-editorExecute the skills CLI command in your project's root directory to begin installation:
Fetches tiptap-editor from xiaolai/vmark and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate tiptap-editor. Access via /tiptap-editor in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
187
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
187
stars
This skill documents proper Tiptap API usage patterns for vmark development. It helps distinguish when to use Tiptap's high-level API vs direct ProseMirror access.
Always prefer Tiptap API for:
isActive, getAttributes)Tiptap patterns to use:
// Direct commands
editor.commands.toggleBold()
editor.commands.setHeading({ level: 2 })
editor.commands.setContent(doc, { emitUpdate: false })
// Chained commands (for multiple operations)
editor.chain().focus().setHeading({ level: 2 }).run()
editor.chain().focus().toggleMark("underline").run()
// State queries
editor.isActive("blockquote")
editor.isActive("heading", { level: 2 })
editor.getAttributes("link")
Use ProseMirror directly for:
proseMirrorToMdast.ts, mdastToProseMirror.ts)MultiSelection.ts)src/hooks/mcpBridge/cursorHandlers.ts uses doc.textContent which flattens the document and loses block boundaries. The correct approach is to use $pos helpers:
// WRONG - loses block structure
const text = doc.textContent;
// RIGHT - respects block boundaries
const $pos = doc.resolve(from);
const currentNode = $pos.parent;
const blockStart = $pos.before($pos.depth);
const blockEnd = $pos.after($pos.depth);
sourceLine attributes are only set on initial parse. After WYSIWYG edits that add/remove blocks, line numbers no longer match the source. This is a known limitation.
src/plugins/markdownArtifacts/HtmlNodeView.ts writes cursor info to wrong store.
references/patterns.md - Detailed API patterns and $pos usagereferences/examples.md - Real code examples from vmark codebaseeditor.commands.xxx() for single operationseditor.chain().focus().xxx().run() when focus is needed or chainingdoc.resolve(pos) to get $pos helperseditor.isActive() or editor.getAttributes()Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
mattpocock/skills
Registry listing for tiptap-editor matched our evaluation — installs cleanly and behaves as described in the markdown.
tiptap-editor fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Solid pick for teams standardizing on skills: tiptap-editor is focused, and the summary matches what you get after install.
We added tiptap-editor from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
tiptap-editor reduced setup friction for our internal harness; good balance of opinion and flexibility.
I recommend tiptap-editor for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
We added tiptap-editor from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Solid pick for teams standardizing on skills: tiptap-editor is focused, and the summary matches what you get after install.
I recommend tiptap-editor for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
tiptap-editor reduced setup friction for our internal harness; good balance of opinion and flexibility.
showing 1-10 of 45