project-setup

A critical, read-only quality review of one blog post or draft. Checks whether the body delivers what the title promises, the logic, every heading against its section, a technical and a marketing read, and ends with a weighted 0-10 scorecard and the three fixes with the most impact, always in the same format so posts can be compared. Use when the user asks to "review this post", "score this article", "is this draft good", "check the quality of the blog post", or gives a post URL, file or pasted text to judge. Never edits the post.

Review one published blog post the user picked, on any site and any CMS, and propose the update without writing anything. Snapshot the post from its public URL (or an export), agree the scope, diagnose the drop proportionately from Search Console and GA4 (through an MCP server, the script's own Google access, or exports; none is required to start), audit the article as published, propose an intervention (no change / technical / consolidation / content), get the editor's approval at named gates, rewrite it in Markdown, render the images it needs (screenshots and HTML-built graphics through the installed Chrome), validate (links, protected passages, metadata, headings), show the whole change on an HTML review page, and hand the editor an approved change list to make in their CMS; `verify` then checks the live page. Not always a rewrite. Use when asked to "update a blog post", "refresh this article", "should we update this post", "why did this post drop", "which posts should we refresh", or given a published article URL to look at.

Use when asked to build, generate, or reverse-engineer a brand kit, brand foundations, brand voice profile, or content-platform onboarding profile for a company from its website URL — "zrób brand kit", "brand kit for <company>", "what does our site actually say about us", or when preparing a company's site for AI content production. Written for the team that owns the site; works on any company's site. Needs only a public URL to start. Also a starting point for the project's `BRAND.md`.

Create a new page section in this Next.js + Sanity starter, after first checking whether an existing section already covers it (reuse as-is, add a layout option or fields, or build a new type). Takes the look from DESIGN.md (plus any Figma link, screenshot or mockup the user gives) and the copy from BRAND.md (placeholder copy while it is still the template), models the code on the 2–3 closest sections in web/src/ui/sections/, and ships the schema, GROQ branch, component, gallery fixture, Markdown serializer, insert-menu entry and tile. Use when the user asks for a new band, block or section, or whether the site already has one that fits a design.

Write alt text for the images in the Sanity dataset. A script lists every image usage (document, field, current alt, the asset's title/description/alt text, a caption, the section heading and the text around it), downloads one small preview per asset into a local cache (`.alts/`, never the same image twice), the agent looks at each image and proposes one alt per usage in the site's content language (or marks it decorative), then the script builds an HTML page where the user reviews, edits and approves them and exports `approved.json`; approved alts go into drafts with a dry-run-first script (`--apply` to write). Use when the user asks to "generate/write/fill alt texts", "images without alt", "alt audit", "accessibility of images", "describe our images", after a content import or migration, or before an accessibility or SEO review. Works on Nexity projects (`img` objects) and on similar Sanity sites.

Find the internal links a site's articles are missing, on any site and any CMS; by default it writes nothing, and only when the user asks and gives access does it put the approved links into Sanity drafts (over the API with a token, or through a Sanity MCP server). A script crawls the published site (sitemap or a URL list), reads each article's content (not the navigation), finds the pages an article already names by their own titles (plus any phrases the rules file governs) and shortlists the pages it overlaps; the agent keeps the candidates that read naturally and proposes links to shortlisted pages with exact anchors; the checks drop anything that collides (already linked, anchor reused, heading, over the limit); the user approves each link on an HTML review page; the approved links become a list the editor adds in their CMS (or, on request, Sanity drafts an editor publishes), and `verify` re-reads the live pages afterwards. Use when the user asks to "add internal links", "fix internal linking", "find linking opportunities", "link this article to our service pages", "which pages are orphans", or gives a site or a list of posts to interlink.

Audit and fix the links stored in the Sanity dataset, three rules counted in one table first. own-domain turns links to the site's own domain (`https://example.com/pricing` or a bare `/pricing` in an external link, CTA, header/footer link or rich-text annotation) into references or internal paths. http upgrades `http://` links and URL fields to `https://` per host, optionally only where https answers. slash aligns internal paths, own-domain URLs and slugs with the trailing-slash convention in `web/next.config.*` and fixes double or missing slashes. The user picks the rules; a dry-run-first script writes them (`--apply`) and re-checks, then the code goes to `link-reviewer`. Use when the user asks to "fix links", "convert absolute URLs to relative", "editors pasted full URLs", "links to our own site open in a new tab", "replace http with https", "trailing slashes are inconsistent", "check our slugs", after a content import or migration, or before a domain change.

Walk a marketer with no terminal experience through setting up the marketing skills (brand-kit, site-contradictions, blog-post-quality-review, internal-links, blog-post-update, and source-review, which blog-post-update uses) step by step, by their preferences, whether they came as the Claude Code plugin `marketing-skills`, through `npx skills add Pagepro/nexity`, or in a downloaded ZIP of the repository. Checks where the skills are, says what to install and how (click by click), installs and builds what it can itself with permission, runs a short test of each chosen skill, and ends with what the person can now ask for. Use when someone says "Help me setup these skills for marketers", "set up the marketing skills", "skonfiguruj skille marketingowe", "pomóż mi to uruchomić", or has just installed the marketing skills and asks how to start.

Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.

No description in the SKILL.md.

Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.

React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.

Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".

tasteskill 2.5.1, the anti-slop frontend skill. Builds professional company websites at the level of figma.com and x.ai: plain copy in a voice of its own, one system, one section per screen, equal edges, real photographs and real product UI (licensed stand-in photographs when the client has none; a product render only when the brief asks for 3D), a hero entrance and one or two dealt moments on every page, shader effects and scenes only on tech, gaming and software pages, quiet micro-interactions, and a checker and finish gate that enforce it in a real browser. Use this whenever you build, design, redesign, restyle, polish or review a landing page, company, product, shop, cafe, hotel, studio, SaaS, AI, developer-tool or game site, as static HTML/CSS or inside an existing React, Next.js, Vue, Svelte, Astro or Tailwind project, or when the user says a page looks generic, templated or "AI-made".

React composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture. Includes React 19 API changes.

UI/UX design intelligence for web, mobile, and desktop. This skill should be used when designing, building, reviewing, or fixing interfaces, including pages, components, design systems, accessibility, interaction, responsive layout, typography, color, charts, and stack-specific UI implementation. Searchable local data: 80 searchable styles (51 active), 192 product palettes and reasoning profiles, 74 font pairings, 120 UX guidelines, 105 icons, 17 GSAP presets, 25 chart types, and 22 stacks.