<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Development on Vibe Coding</title><link>https://vibecoding.rest/category/development/</link><description>Recent content in Development on Vibe Coding</description><generator>Hugo</generator><language>en</language><atom:link href="https://vibecoding.rest/category/development/index.xml" rel="self" type="application/rss+xml"/><item><title>Artifacts Builder</title><link>https://vibecoding.rest/skills/artifacts-builder/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/skills/artifacts-builder/</guid><description>&lt;p&gt;The Artifacts Builder skill covers the conventions for producing standalone, self-contained interactive outputs — inlined styles and scripts, responsive layout, no external dependencies that would break in a sandboxed viewer.&lt;/p&gt;</description></item><item><title>Webapp Testing</title><link>https://vibecoding.rest/skills/webapp-testing/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/skills/webapp-testing/</guid><description>&lt;p&gt;The Webapp Testing skill packages a verification workflow: launching a dev server, driving a browser through the golden path and edge cases, and checking console and network output for errors — rather than declaring a UI change complete after just reading the code.&lt;/p&gt;</description></item><item><title>MCP Builder</title><link>https://vibecoding.rest/skills/mcp-builder/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/skills/mcp-builder/</guid><description>&lt;p&gt;The MCP Builder skill packages the boilerplate and conventions for writing a new &lt;a href="https://vibecoding.rest/mcp-servers/"&gt;MCP server&lt;/a&gt; — the protocol handshake, tool and resource definitions, and error handling patterns that a well-behaved server needs.&lt;/p&gt;</description></item><item><title>Claude API</title><link>https://vibecoding.rest/skills/claude-api/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/skills/claude-api/</guid><description>&lt;p&gt;The Claude API skill is a language-aware reference for the Anthropic SDK and Messages API — model selection, adaptive thinking, streaming, prompt caching, token counting, and tool/MCP integration — with explicit guidance to verify API shapes against live docs rather than a model&amp;rsquo;s memorized training data.&lt;/p&gt;</description></item><item><title>Skill Creator</title><link>https://vibecoding.rest/skills/skill-creator/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/skills/skill-creator/</guid><description>&lt;p&gt;Skill Creator packages the full lifecycle of authoring an Agent Skill: drafting the skill, writing test prompts, running evaluations with variance analysis, reviewing results, and rewriting the skill based on feedback, then optimizing the skill&amp;rsquo;s description for more reliable triggering.&lt;/p&gt;</description></item><item><title>Superpowers</title><link>https://vibecoding.rest/skills/superpowers/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/skills/superpowers/</guid><description>&lt;p&gt;Superpowers packages a battle-tested library of 20+ Claude Code skills — test-driven development, systematic debugging, brainstorming techniques, git worktree management, and root-cause tracing — installable in one shot as a plugin marketplace.&lt;/p&gt;</description></item><item><title>Superpowers Lab</title><link>https://vibecoding.rest/skills/superpowers-lab/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/skills/superpowers-lab/</guid><description>&lt;p&gt;Superpowers Lab is the experimental proving ground for &lt;a href="https://vibecoding.rest/skills/superpowers/"&gt;Superpowers&lt;/a&gt; — newer, less-settled techniques that graduate into the stable library once they hold up in real use.&lt;/p&gt;&#10;&lt;h2 id="why-a-skill-for-this"&gt;Why a skill for this&lt;/h2&gt;&#10;&lt;p&gt;Skill development benefits from the same staging discipline as software releases — trying new techniques in a lab environment before committing them to a widely-installed stable marketplace avoids regressions for everyone else.&lt;/p&gt;</description></item><item><title>Expo Skills</title><link>https://vibecoding.rest/skills/expo-skills/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/skills/expo-skills/</guid><description>&lt;p&gt;Expo Skills is the official skill set from the Expo team for building React Native apps with Expo, covering the framework&amp;rsquo;s specific conventions and tooling.&lt;/p&gt;&#10;&lt;h2 id="why-a-skill-for-this"&gt;Why a skill for this&lt;/h2&gt;&#10;&lt;p&gt;Being maintained by the Expo team itself means the skill tracks the framework&amp;rsquo;s actual conventions and release changes, rather than a third party&amp;rsquo;s best guess at Expo&amp;rsquo;s current best practices.&lt;/p&gt;</description></item><item><title>shadcn/ui Skill</title><link>https://vibecoding.rest/skills/shadcn-ui-skill/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/skills/shadcn-ui-skill/</guid><description>&lt;p&gt;The shadcn/ui skill gives Claude Code direct context on shadcn/ui&amp;rsquo;s components and enforces consistent usage patterns across a project.&lt;/p&gt;&#10;&lt;h2 id="why-a-skill-for-this"&gt;Why a skill for this&lt;/h2&gt;&#10;&lt;p&gt;shadcn/ui ships as copyable component source rather than an installed package, so consistency depends on the model actually knowing each component&amp;rsquo;s intended API. A skill scoped to shadcn/ui keeps generated UI code matching the library&amp;rsquo;s real patterns instead of guessing.&lt;/p&gt;</description></item><item><title>Get Shit Done</title><link>https://vibecoding.rest/skills/get-shit-done/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/skills/get-shit-done/</guid><description>&lt;p&gt;Get Shit Done is a lightweight meta-prompting and context-engineering system for Claude Code, built around spec-driven development rather than ad hoc prompting.&lt;/p&gt;&#10;&lt;h2 id="why-a-skill-for-this"&gt;Why a skill for this&lt;/h2&gt;&#10;&lt;p&gt;Spec-first workflows tend to produce more predictable output than freeform prompting, especially on larger features. Packaging that discipline as a skill makes it the default instead of something re-explained per task.&lt;/p&gt;</description></item><item><title>Skill Seekers</title><link>https://vibecoding.rest/skills/skill-seekers/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/skills/skill-seekers/</guid><description>&lt;p&gt;Skill Seekers automatically converts any documentation website into a ready-to-use Claude skill, turning scattered docs into structured, invokable reference material.&lt;/p&gt;&#10;&lt;h2 id="why-a-skill-for-this"&gt;Why a skill for this&lt;/h2&gt;&#10;&lt;p&gt;Most third-party libraries have documentation but no packaged skill. Automating the conversion means any well-documented tool can get a working skill without hand-authoring one from scratch.&lt;/p&gt;</description></item><item><title>Jules Delegate</title><link>https://vibecoding.rest/skills/jules-delegate/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/skills/jules-delegate/</guid><description>&lt;p&gt;Jules Delegate hands off coding tasks to Google&amp;rsquo;s Jules AI agent for async work — bug fixes, docs, and tests — directly on a GitHub repo.&lt;/p&gt;&#10;&lt;h2 id="why-a-skill-for-this"&gt;Why a skill for this&lt;/h2&gt;&#10;&lt;p&gt;Some tasks are better run asynchronously in the background than synchronously in the current session. This skill packages the hand-off so Claude Code can delegate rather than block on work another agent can do independently.&lt;/p&gt;</description></item><item><title>Agent Skills Open Standard</title><link>https://vibecoding.rest/skills/agent-skills-open-standard/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/skills/agent-skills-open-standard/</guid><description>&lt;p&gt;Agent Skills is the open SKILL.md standard for packaging reusable agent capabilities — originated by Anthropic and now adopted across Codex, Gemini CLI, Grok Build, Cursor, GitHub Copilot, and more.&lt;/p&gt;</description></item><item><title>Codex Skills System</title><link>https://vibecoding.rest/skills/codex-skills-system/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/skills/codex-skills-system/</guid><description>&lt;p&gt;OpenAI Codex&amp;rsquo;s built-in skills system discovers SKILL.md skills from &lt;code&gt;~/.codex/skills/&lt;/code&gt; and installs new ones via &lt;code&gt;$skill-installer&lt;/code&gt;, either from OpenAI&amp;rsquo;s curated catalog or any GitHub repo.&lt;/p&gt;&#10;&lt;h2 id="why-a-skill-for-this"&gt;Why a skill for this&lt;/h2&gt;&#10;&lt;p&gt;Having a first-party install path and curated catalog, rather than only community-assembled lists, is what makes a skills ecosystem practical to actually adopt inside Codex.&lt;/p&gt;</description></item><item><title>OpenAI Skills/Plugins Catalog</title><link>https://vibecoding.rest/skills/openai-plugins-catalog/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/skills/openai-plugins-catalog/</guid><description>&lt;p&gt;This is OpenAI&amp;rsquo;s official, curated repository of Codex skills and plugins — covering design tools, testing, security, observability, and one-command cloud deploys.&lt;/p&gt;&#10;&lt;h2 id="why-a-skill-for-this"&gt;Why a skill for this&lt;/h2&gt;&#10;&lt;p&gt;A first-party curated catalog is a stronger trust signal than an assembled community list — these skills are maintained by, or reviewed by, OpenAI itself rather than crowdsourced without a review bar.&lt;/p&gt;</description></item><item><title>Security Best Practices Skill</title><link>https://vibecoding.rest/skills/security-best-practices-skill/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/skills/security-best-practices-skill/</guid><description>&lt;p&gt;This curated Codex skill applies a secure-coding checklist during code generation and review, catching common vulnerability classes as code is written.&lt;/p&gt;&#10;&lt;h2 id="why-a-skill-for-this"&gt;Why a skill for this&lt;/h2&gt;&#10;&lt;p&gt;Security issues are cheaper to prevent during generation than to catch in a later review pass. Baking a checklist into the generation step catches classes of bugs before they&amp;rsquo;re ever committed.&lt;/p&gt;</description></item><item><title>Security Threat Model Skill</title><link>https://vibecoding.rest/skills/security-threat-model-skill/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/skills/security-threat-model-skill/</guid><description>&lt;p&gt;This curated Codex skill walks through producing a structured threat model for a system — assets, trust boundaries, and attack surfaces — rather than an ad hoc security discussion.&lt;/p&gt;&#10;&lt;h2 id="why-a-skill-for-this"&gt;Why a skill for this&lt;/h2&gt;&#10;&lt;p&gt;Threat modeling is only useful if it&amp;rsquo;s structured and complete; an unstructured conversation tends to miss entire categories of risk. A skill that enforces the methodology produces a threat model that&amp;rsquo;s actually useful to a security reviewer.&lt;/p&gt;</description></item><item><title>Skill Creator (OpenAI)</title><link>https://vibecoding.rest/skills/openai-skill-creator/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/skills/openai-skill-creator/</guid><description>&lt;p&gt;This system skill, auto-installed with Codex, scaffolds a new SKILL.md-compliant skill from a plain description of what it should do.&lt;/p&gt;&#10;&lt;h2 id="why-a-skill-for-this"&gt;Why a skill for this&lt;/h2&gt;&#10;&lt;p&gt;Getting a skill&amp;rsquo;s folder structure and frontmatter right by hand is easy to get subtly wrong. A scaffolding skill means authoring a new skill starts from a correct template instead of a blank file.&lt;/p&gt;</description></item><item><title>Google Antigravity Skills System</title><link>https://vibecoding.rest/skills/antigravity-skills-system/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/skills/antigravity-skills-system/</guid><description>&lt;p&gt;Google Antigravity&amp;rsquo;s skills system supports the same SKILL.md format as Claude Code and Codex, with both global (&lt;code&gt;~/.gemini/config/skills/&lt;/code&gt;) and per-project (&lt;code&gt;.agents/skills/&lt;/code&gt;) scopes.&lt;/p&gt;&#10;&lt;h2 id="why-a-skill-for-this"&gt;Why a skill for this&lt;/h2&gt;&#10;&lt;p&gt;Supporting the shared SKILL.md format means skills built for Antigravity aren&amp;rsquo;t locked to Google&amp;rsquo;s tooling — the same skill folder is portable to other compatible agents.&lt;/p&gt;</description></item><item><title>Gemini CLI Skills System</title><link>https://vibecoding.rest/skills/gemini-cli-skills-system/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/skills/gemini-cli-skills-system/</guid><description>&lt;p&gt;Gemini CLI natively supports the Agent Skills (SKILL.md) open standard, letting it load the same skill format used by Claude Code, Codex, and other compatible agents.&lt;/p&gt;&#10;&lt;h2 id="why-a-skill-for-this"&gt;Why a skill for this&lt;/h2&gt;&#10;&lt;p&gt;A shared skills format means a skill only has to be written once to work across Gemini CLI and other compatible agents, rather than maintaining separate versions per tool.&lt;/p&gt;</description></item><item><title>Grok Build Skills System</title><link>https://vibecoding.rest/skills/grok-build-skills-system/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/skills/grok-build-skills-system/</guid><description>&lt;p&gt;Grok Build&amp;rsquo;s skills system reads SKILL.md skills from &lt;code&gt;.grok/skills/&lt;/code&gt;, &lt;code&gt;~/.grok/skills/&lt;/code&gt;, and plugin directories — and is directly Claude Code-compatible, reading &lt;code&gt;.claude/skills&lt;/code&gt; and &lt;code&gt;CLAUDE.md&lt;/code&gt; with zero extra configuration.&lt;/p&gt;&#10;&lt;h2 id="why-a-skill-for-this"&gt;Why a skill for this&lt;/h2&gt;&#10;&lt;p&gt;Direct compatibility with Claude Code&amp;rsquo;s own skill and config files means a project that&amp;rsquo;s already set up for Claude Code works in Grok Build without any migration step.&lt;/p&gt;</description></item></channel></rss>