CtrlK
BlogDocsLog inGet started
Tessl Logo

jazz-ui-development

Use this skill when building, debugging, or optimizing Jazz applications. It covers Jazz's bindings with various different UI frameworks, as well as how to use Jazz without a framework. Look here for details on providers and context, hooks and reactive data fetching, authentication, and specialized UI components for media and inspection.

61

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./packages/cursor-docs/.skills/jazz-ui-development/SKILL.md

The canonical home for this skill is jazz-ui-development in garden-co/classic-jazz

SKILL.md
Quality
Evals
Security

Quality

Content

78%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is well-structured, actionable, and uses progressive disclosure effectively with real one-level reference files for framework-specific guides. The main weakness is the lack of explicit validation/feedback checkpoints around write and merge operations.

Suggestions

Add a validation/feedback loop for writes and merges, e.g. after `unstable_merge()` or `applyDiff`, verify the result with `$jazz.waitForSync()` and check `loadingState`/`$isLoaded` before proceeding.

Provide a complete executable example for ImageDefinition writes (`createImage` from `jazz-tools/media`), currently only the read path is illustrated.

Tighten the Universal CoValue API metadata list by moving the less-central properties (createdAt/createdBy/lastUpdatedAt) into a reference file to reduce token load.

DimensionReasoningScore

Conciseness

The body is dense and mostly token-efficient: API tables, method lists, and inline code examples with little padding, though sections like the Universal CoValue API list many properties an experienced reader partly knows.

4 / 5

Actionability

Provides concrete executable patterns (e.g., `post.$jazz.ensureLoaded({ resolve: { comments: { $each: { author: true } } } })`, `feed.$jazz.push(...)`) and method signatures, with only minor gaps like the ImageDefinition write path lacking a full example.

4 / 5

Workflow Clarity

Troubleshooting sections give clear ordered steps (check `$isLoaded` -> deep loading -> provider check), but there are no explicit validation/feedback-loop checkpoints for the destructive write operations (set/delete/push/splice/merge).

4 / 5

Progressive Disclosure

Clear overview body with one-level-deep, well-signaled framework references (react.md, react-native.md, expo.md, svelte.md, vanilla.md), each a real file, with shared universal APIs kept inline and framework specifics offloaded appropriately.

5 / 5

Total

17

/

20

Passed

Description

63%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description gives a clear, third-person statement of what the skill covers and when to use it, with good coverage of the UI-specific domain. Trigger terms and distinctiveness could be sharpened by naming concrete frameworks and stronger trigger phrases.

Suggestions

Add explicit trigger phrases users would say, such as 'Use when rendering Jazz data in React/Svelte, wiring up JazzProvider, or debugging useCoState/subscription issues.'

Name concrete frameworks (React, Svelte, React Native, Expo) in the description to improve trigger-term coverage and reduce overlap with sibling Jazz skills.

Replace the generic 'various different UI frameworks' phrasing, which reads as filler, with the specific framework list.

DimensionReasoningScore

Specificity

Lists several concrete action areas ('building, debugging, or optimizing', 'providers and context, hooks and reactive data fetching, authentication') plus concrete UI topics (media, inspection), though actions are framed as coverage domains rather than discrete operations.

4 / 5

Completeness

Clearly states both what ('covers Jazz's bindings with various UI frameworks... providers and context, hooks...') and when ('Use this skill when building, debugging, or optimizing Jazz applications'); the 'when' is explicit but could name sharper trigger phrases.

4 / 5

Trigger Term Quality

Includes some natural terms ('building', 'debugging', 'optimizing', 'authentication', 'media') but is missing common user-facing variations and synonyms; no file extensions or framework names beyond generic 'UI frameworks' phrasing.

3 / 5

Distinctiveness Conflict Risk

The 'Do NOT Use' boundaries are not in the description, but the focus on UI bindings/providers/hooks/media is a fairly clear niche distinct from sibling Jazz skills, with only minor overlap risk.

4 / 5

Total

15

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
garden-co/classic-jazz
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.