Lightweight Git-backed CMS for static sites with 270+ fixes over Decap CMS.
Works with
Framework-agnostic setup for Hugo, Jekyll, 11ty, Astro, and Next.js; drop-in replacement for Decap CMS requiring only a single script tag change
Cloudflare Workers OAuth authentication (free tier, fastest option) or Vercel serverless functions; prevents 10 common errors including YAML parse failures, datetime timezone issues, and CORS/COOP blocking
Supports YAML, TOML, JSON, and Markdown formats with field-le
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionsveltia-cmsExecute the skills CLI command in your project's root directory to begin installation:
Fetches sveltia-cms from jezweb/claude-skills 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 sveltia-cms. Access via /sveltia-cms 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
1
total installs
1
this week
697
GitHub stars
0
upvotes
Run in your terminal
1
installs
1
this week
697
stars
Complete skill for integrating Sveltia CMS into static site projects.
DEPRECATION: The slug_length collection option is deprecated and will be removed in v1.0.
Migration:
# ❌ Deprecated (pre-v0.127.0)
collections:
- name: posts
slug_length: 50
# ✅ New (v0.127.0+)
slug:
maxlength: 50
Timeline: Will be removed in Sveltia CMS 1.0 (expected early 2026).
Source: Release v0.127.0
New Feature: Hidden widget now supports author template tags:
{{author-email}} - Signed-in user's email{{author-login}} - Signed-in user's login name{{author-name}} - Signed-in user's display nameUsage:
fields:
- label: Author Email
name: author_email
widget: hidden
default: '{{author-email}}'
Commit message templates also support {{author-email}} tag.
New Feature: Configuration files can now be written in TOML format (previously YAML-only).
Migration:
# admin/config.toml (NEW)
[backend]
name = "github"
repo = "owner/repo"
branch = "main"
media_folder = "static/images/uploads"
public_folder = "/images/uploads"
Recommendation: YAML is still preferred for better tooling support.
BREAKING: Renamed SiteConfig export to CmsConfig for compatibility with Netlify/Decap CMS.
Migration:
// ❌ Old (v0.117.x)
import type { SiteConfig } from '@sveltia/cms';
// ✅ New (v0.118.0+)
import type { CmsConfig } from '@sveltia/cms';
const config: CmsConfig = {
backend: { name: 'github', repo: 'owner/repo' },
collections: [/* ... */],
};
Impact: TypeScript users only. Breaking change for type imports.
New Features:
CmsConfig type for direct TypeScript importNew Feature: Override media_folder at the field level (not just collection level).
Usage:
collections:
- name: posts
label: Blog Posts
folder: content/posts
media_folder: static/images/posts # Collection-level default
fields:
- label: Featured Image
name: image
widget: image
media_folder: static/images/featured # ← Field-level override
public_folder: /images/featured
- label: Author Avatar
name: avatar
widget: image
media_folder: static/images/avatars # ← Another override
public_folder: /images/avatars
Use case: Different media folders for different image types in same collection.
DEPRECATION: logo_url option is now deprecated. Migrate to logo.src.
Migration:
# ❌ Deprecated
logo_url: https://yourdomain.com/logo.svg
# ✅ New (v0.113.5+)
logo:
src: https://yourdomain.com/logo.svg
BREAKING: sanitize_preview default changed to true for Markdown widget (XSS prevention).
Impact:
sanitize_preview: false (compatibility with Netlify/Decap CMS, but vulnerable to XSS)sanitize_preview: true (secure by default)Migration:
collections:
- name: posts
fields:
- label: Body
name: body
widget: markdown
sanitize_preview: false # ← Add ONLY if you trust all CMS users
Recommendation: Keep default (true) unless disabling fixes broken preview AND you fully trust all CMS users.
Configure slug generation behavior globally:
slug:
encoding: unicode-normalized
clean_accents: false
sanitize_replacement: '-'
lowercase: true # Default: convert to lowercase (v0.128.0+)
maxlength: 50 # Default: unlimited (v0.127.0+)
lowercase (v0.128.0+): Set to false to preserve original casing in slugs (e.g., "MyBlogPost" instead of "myblogpost").
Use case: Mixed-case URLs or file names where case matters.
Source: Release v0.128.0, GitHub Issue #594
New raw format allows editing files without front matter (CSV, JSON, YAML, plain text). Must have single body field with widget type: code, markdown, richtext, or text.
Use Cases:
Configuration:
collections:
- name: config
label: Configuration Files
files:
- label: Site Config
name: site_config
file: config.json
format: raw # ← NEW format type
fields:
- label: Config
name: body
widget: code
default_language: json
Restrictions:
body)code, markdown, richtext, or textSource: Release v0.126.0
New value_type option for Number field accepts int/string and float/string to save numbers as strings instead of numbers in front matter.
Use Case: Some static site generators or schemas require numeric values stored as strings (e.g., age: "25" instead of age: 25).
Configuration:
fields:
- label: Age
name: age
widget: number
value_type: int/string # Saves as "25" not 25
- label: Price
name: price
widget: number
value_type: float/string # Saves as "19.99" not 19.99
Source: Release v0.125.0, GitHub Issue #574
Override editor locale via URL query parameter ?_locale=fr to get edit links for specific locales.
Use Case: Generate direct edit links for translators or content editors for specific languages.
Example:
https://yourdomain.com/admin/#/collections/posts/entries/my-post?_locale=fr
Source: Release v0.126.0, GitHub Issue #585
Added richtext as an alias for markdown widget to align with Decap CMS terminology. Both work identically.
Configuration:
fields:
- label: Body
name: body
widget: richtext # ← NEW alias for markdown
Future: HTML output support planned for richtext field type.
Source: Release v0.124.0
All frameworks follow the same pattern:
Create admin directory in public/static folder:
static/admin/admin/admin/ (with passthrough copy)public/admin/public/admin/Create admin/index.html:
<!doctype html>
<html lang="en"✓Make data-driven prioritization decisions faster
Stakeholder Communication
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
Implementation Guide
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Steps
- 1Install product management skill
- 2Start with user story generation for known feature
- 3Progress to competitive analysis: research 2-3 competitors
- 4Use for roadmap prioritization: apply RICE/ICE scoring
- 5Draft stakeholder communications and refine based on feedback
- 6Build template library for recurring PM tasks
- 7Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This
✓ 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.
Learning Path
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Related Skills
wordpress-elementor
123jezweb/claude-skills
Productivitysame repogrill-me
646mattpocock/skills
Productivitysame categorypremortem
213parcadei/continuous-claude-v3
Productivitysame categorydeslop
159cursor/plugins
Productivitysame categorytravel-planner
136ailabs-393/ai-labs-claude-skills
Productivitysame categoryframer-motion
131pproenca/dot-skills
Productivitysame categoryReviews
4.5★★★★★57 reviews- HHana Garcia★★★★★Dec 28, 2024
sveltia-cms is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- SSoo Liu★★★★★Dec 20, 2024
Registry listing for sveltia-cms matched our evaluation — installs cleanly and behaves as described in the markdown.
- NNeel Johnson★★★★★Dec 4, 2024
sveltia-cms reduced setup friction for our internal harness; good balance of opinion and flexibility.
- AArya Bhatia★★★★★Nov 23, 2024
I recommend sveltia-cms for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- JJin Rao★★★★★Nov 19, 2024
Solid pick for teams standardizing on skills: sveltia-cms is focused, and the summary matches what you get after install.
- AAanya Sharma★★★★★Nov 15, 2024
sveltia-cms fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- AArjun Jackson★★★★★Nov 11, 2024
We added sveltia-cms from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- AAlexander Kim★★★★★Nov 11, 2024
Useful defaults in sveltia-cms — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- AArjun Harris★★★★★Oct 14, 2024
Useful defaults in sveltia-cms — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- AAarav Martinez★★★★★Oct 10, 2024
sveltia-cms has been reliable in day-to-day use. Documentation quality is above average for community skills.
showing 1-10 of 57
1 / 6Discussion
Comments — not star reviews- No comments yet — start the thread.