feat: add Contentstack Studio agent skills - #13
Closed
saurav-cstk wants to merge 1 commit into
Closed
Conversation
Integrate the studio-docs skill pack into the shared agent-skills repo, converted to the target structure without touching the existing 21 skills. - Add 66 Studio skills as skills/<slug>/SKILL.md with name + description + allowed-tools frontmatter; sibling cross-links rewritten to ../<slug>/SKILL.md; external docs/scripts links de-linked. - Register all 66 in the skills/CLAUDE.md router and manifest.json (21 -> 87). - Declare "skills": "./skills/" in plugin.json so Claude Code loads the plugin's skills (a marketplace root source disables default skills/ auto-discovery). - build-cursor-rules.sh: preserve existing slug->NN numbering so adding skills is additive (no renumber churn) and idempotent. - Regenerate the codex/ and cursor/ trees. Existing 21 skills are byte-identical. Content matches studio-docs main. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
saurav-cstk
changed the title
saurav-cstk
changed the title
saurav-cstk
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Overview
Adds an agent skill pack for Contentstack Studio — Contentstack's visual, composable page-building experience. Studio lets teams register their own React components, compose them into reusable Sections, arrange those Sections into Templates that render live pages against a content type, bind CMS data visually on a canvas, preview in real time, and ship — all without hand-writing page code for every route.
These 66 skills teach an agent to guide a developer or content author through that entire journey, from a cold project to a deployed Studio-rendered site, and to diagnose it when something breaks.
What the skills help you do
Get started & understand the model
Onboard from zero, take a guided tour, and learn the core concepts — what a Section is, how Templates render against a content type, linked schemas, auto-binding, the canvas vs. component split, Section Slots, and headless authoring.
Install & configure Studio
Check project compatibility, install Studio + Live Preview + the Delivery SDK, wire the SDK init, enable Visual Experience at the stack level, configure the project (environment, language, Canvas URL), register breakpoints, and set up the canvas and template-preview routes.
Provision the backing content
Plan the Studio architecture (which pieces are Sections, which pages are Connected Templates, which content types and global fields), bootstrap the compositions content type, and seed the stack with page content types, entries, and assets.
Bring your own components (BYOC)
Register React components into the Studio palette (lazy by default), infer prop schemas, import design tokens from Tailwind/CSS/JSON, register a JSON RTE renderer, wire component default data, expose per-instance props, and generate components straight from Figma.
Build Sections
Author Sections bound to a structural schema, build repeating card/tile Sections, use Repeaters, Section Slots, and Condition Blocks, and derive Section shapes from existing JSX or a whole design/site decomposition.
Build Templates
Choose Connected vs. Freeform, scaffold Connected (content-type-bound) Templates and Freeform (one-off) Templates, and pin entries or CDA queries to Freeform pages.
Bind & source data
Author compositions via the API, author without code, bring in external (non-Contentstack) data, wire Personalize variant aliases, and import or migrate content and content-type schemas.
Render, embed & ship
Pick and wire CSR vs. SSR/RSC, embed a Studio-managed region inside a code-owned page, gate third-party scripts out of the canvas, deploy to Vercel/Netlify, migrate an existing route to Studio, and upgrade the Studio SDK.
Verify & troubleshoot
Run layered setup smoke tests, check visual parity against a production page, and diagnose canvas, data-binding, composition-resolution, and SSR-rendering failures with a symptom-first router.
Structure
Each skill is
skills/<slug>/SKILL.mdwithname,description, andallowed-tools, registered in theskills/CLAUDE.mdrouter andmanifest.json, and built into thecodex/andcursor/targets — the same shape as every existing skill in this repo. The existing 21 skills are unchanged.🤖 Generated with Claude Code