strapi
- 39 skills
- 0 followers
- yesterday last updated
- ▌ Inki Outline UX Analyzer · strapiAnalyze the pedagogical UX of a documentation outline: progression from beginner to advanced, signposting, and reading flow.
- ▌ Inki Outline · strapiGenerate an outline for a new documentation page from a topic brief and the appropriate template.
- ▌ Inki Scripts · strapi bundleShell helpers shared by the inki-* skills: the deterministic style linter, temporary worktrees for main and for a PR, the root-refs sync, and the skills links. Load when another inki-* skill cites it, or when you need to lint a docs page or check the skills links.
- ▌ Inki Coverage · strapiAudit the documentation coverage of a Strapi feature or module: list what is documented vs missing.
- ▌ Inki Document · strapiEnd-to-end documentation orchestrator: chains all four inki phases (research, write, review, submit) for a single subject. Gates between each phase by default; --non-interactive chains without pauses and runs a review-fix loop. The simplest way to document a subject from scratch.
- ▌ Inki Research · strapiTop-level research orchestrator: combines exists, route, and coverage to give a complete picture before writing.
- ▌ Inki References · strapi bundleShared Strapi docs references for the inki-* skills: page templates, authoring guides per docs area, style rules, reviewer and drafter prompts, git and PR rules, logging and help conventions. Load when another inki-* skill cites it, or when you need a doc template or an authoring rule.
- ▌ Inki Code Verify · strapiVerify code blocks in a documentation file: check syntax, references, and consistency with the underlying Strapi APIs.
- ▌ Inki Style Check · strapiRun deterministic style checks on a documentation file or directory, then layer AI judgment on top using the migrated style-checker prompt.
- ▌ Inki Pitfalls Add · strapiAdd a new entry to the known-pitfalls catalog that pitfalls-check audits against. Verifies the correct pattern against the Strapi source before adding, and confirms with the user. Use when you have found a documentation mistake worth catching automatically in future reviews.
- ▌ Inki Outline Check · strapiCheck the structural outline of a documentation page: heading hierarchy, section order, completeness against the template.
- ▌ Inki Pitfalls Check · strapiAudit a documentation file against the known-pitfalls list: common mistakes, outdated patterns, deprecated APIs.
- ▌ Inki Interactive Demo · strapi bundleCreate or update an interactive demo (the clickable product tours that replaced Guideflow) from a plain-text description of its steps: finds the UI elements in a running Strapi demo app, writes the YAML scenario, captures it and checks the result.
- ▌ Inki Pr · strapiCreate a pull request on strapi/documentation following git-rules.md. Strict flat-text description, no headings, no test plan.
- ▌ Inki Draft · strapiDraft a documentation page from an approved outline, the matching template, and the relevant authoring guide.
- ▌ Inki Route · strapiGiven a strapi/strapi or strapi/cloud PR, identify which documentation pages and sections must be updated to cover the change.
- ▌ Inki Write · strapiTop-level write orchestrator: outline a new page, get user approval, then draft from the outline.
- ▌ Inki Branch · strapiCreate a new branch in strapi/documentation with auto-detected prefix (cms/, cloud/, repo/) based on the files that will be touched.
- ▌ Inki Commit · strapiStage and commit documentation changes in strapi/documentation. Enforces git-rules.md, protected paths, and branch prefix detection.
- ▌ Inki Exists · strapiCheck whether a documentation topic is already covered on strapi/documentation: searches llms.txt, doc files, sidebars, and open GitHub PRs.
- ▌ Inki Pr Fix · strapiRewrite the title or description/body of one or more open PRs on strapi/documentation to match git-rules.md. Strict one-by-one confirmation, or auto-edit with --non-interactive.
- ▌ Inki Review · strapiTop-level review orchestrator: runs style-check, outline-check, outline-ux-analyzer, code-verify, coherence-check, and pitfalls-check on a file, directory, or PR.
- ▌ Inki Submit · strapiTop-level orchestrator: branch (if needed), commit, push, then open a PR. Each step asks for confirmation before continuing, unless --non-interactive is passed.
- ▌ Create Issue · strapiUse when drafting or publishing an issue on strapi/strapi, including with `gh issue create`. Trigger whenever an agent is about to open a GitHub issue in this repo, even if the user only says "file a bug" or "open an issue for this".
- ▌ Git Conventions · strapiUse when writing any git commit message, PR title, or squash subject in the Strapi repo. Trigger whenever a commit/PR subject is being drafted, even if the user didn't say the word "commit".
- ▌ Contributor Docs · strapiUse when writing, updating, or reviewing Strapi contributor docs in `docs/`; when documenting a package or an internal mechanism; when changing code that a contributor doc describes; or when flagging stale docs. Trigger on any edit under `docs/docs/`, on a request to explain how a package or mechanism works, and on a code change in a package that has a page in `docs/docs/packages/`.
- ▌ Strapi Docs MCP · strapiQuery the official Strapi documentation through the strapi-docs MCP server (powered by Kapa). Use for any Strapi question — API syntax, configuration, features, plugins, upgrades, CLI. If the server is missing, instruct the user how to install it.
- ▌ Strapi Version Upgrade · strapi bundleUpgrade a Strapi application to a new version. ALWAYS reviews the relevant breaking changes first (via the strapi-docs MCP server, or by fetching the docs directly if the MCP is unavailable), then performs the upgrade using the official @strapi/upgrade tool. Use whenever the user wants to upgrade, update, or bump their Strapi version.
- ▌ Strapi MCP Capabilities · strapi bundleCreate custom MCP capabilities (tools, prompts, resources) in a Strapi 5 plugin via the strapi.ai.mcp service. Use when adding a custom MCP tool/prompt/resource to Strapi, extending the Strapi MCP server.
- ▌ Strapi Product Builder · strapi bundleRun a structured, business-value-first product-planning interview that turns a fuzzy idea into a build-ready spec — BEFORE any code is written. Use this the moment someone is still figuring out WHAT to build and says things like "I have an idea for an app, help me think it through", "help me plan/scope/design my product", "where do I start?", "let's spec this out before I write code", or "turn this into a PRD". Covers any new app, site, SaaS, MVP, marketplace, or feature. Trigger on the planning intent alone — the user need NOT mention Strapi, a CMS, or any tech; a Strapi v5 + Strapi Cloud backend (overridable, with your choice of frontend and auth) is assumed by default. It nails value, users, and requirements before any tech decision, then produces six markdown files ending in a build spec you can hand to any coding agent (Claude Code, Cursor, etc.). Do NOT use once a spec or project exists and the user wants to scaffold, configure, migrate, add pages, wire auth, or debug — those are build tasks, not idea-s
- ▌ Shadcn UI · strapiExpert guidance for integrating shadcn/ui components in this Next.js monorepo (apps/ui). Handles component discovery, installation via CLI, customization to local conventions (cn() in @/lib/styles, Tailwind v4, radix-ui primitives), and best practices. Use this skill whenever the user wants to add, install, customize, or troubleshoot a shadcn/ui component — even if they just say 'add a button' or 'install tabs'. Also triggers on: shadcn, radix, UI component, cn utility, component library.
- ▌ Add Locale · strapiAdds a new language/locale to the application. Involves Strapi admin config, Next.js i18n routing, and translation files. Use this skill whenever the user mentions adding a language, translation, i18n, multilingual support, locale, or internationalization — even if they don't explicitly say 'locale'. Also triggers on: add language, add locale, new language, new translation, support another language.
- ▌ Seed Content · strapiScrape a strapi.io page, extract content for specific components, transform to match local Strapi schemas, and seed into local Strapi via MCP. Schema-driven and resilient to evolving schemas. Triggers: seed content, scrape strapi, import content, seed page, seed component.
- ▌ Prd Component · strapi bundleCreate a structured PRD (Product Requirements Document) as a JSON task file with prioritized stories for automated execution. Ralph is the project's task runner script that processes stories sequentially. Use this skill whenever the user wants to plan work, break down a feature into stories, create a task plan, or prepare a batch of component migrations. Triggers: create PRD, plan tasks, break down work, create stories, task planning, batch migration, ralph, plan component work.
- ▌ Copy Component · strapi bundleCopy a component from strapi.io by extracting structure and computed styles via Playwright, mapping to local design tokens, and generating a full-stack component (Strapi schema + React + population config). Triggers: copy component, copy section from, replicate from strapi, clone component.
- ▌ Setup Strapi MCP · strapiOne-time setup of Strapi MCP server for the local Strapi instance. Configures @bschauer/strapi-mcp-server so Agent can read schemas and write content via MCP. Triggers: setup strapi mcp, configure strapi mcp, connect strapi.
- ▌ Consolidate Patterns · strapiReview recently created page-builder components, identify reusable JSX/Tailwind patterns, extract them into elementary components, and update the component registry. Use as a checkpoint between batches of copy-component migrations. Triggers: consolidate patterns, extract reusable, review components for patterns, checkpoint review.
- ▌ Migrate Strapi Content · strapi bundleBatch-migrate content from the old strapi.io Strapi instance (production-old MCP) to the current production Strapi (production MCP). Fully autonomous — paste URLs and nothing else is needed. Supports ALL content types — user-stories, blog-posts, news, jobs, pages (including cross-type migrations where old use-cases/universals map to new pages), comparators. Operates MCP-to-MCP (no HTML scraping). Triggers: migrate, batch migrate, migrate from production-old, bulk seed, batch seed urls, paste urls to migrate, migrate pages, migrate solutions, migrate user stories, migrate blog posts, migrate case studies, migrate comparators.
- ▌ Create Content Component · strapi bundleCreates a new page builder content component for both Strapi and the Next.js frontend. Use this skill whenever the user wants to add a new section, form, or component to the page builder — including creating Strapi schemas, dynamic zone registration, populate configs, and React wrappers. Triggers: add/create page component, new page section, page builder component, add form component, new strapi schema, add content type, new section component, add dynamic zone component, create strapi component.