Plugins
3 pluginscurated
Design System Foundation
Create design tokens, principles, and naming conventions for a new design system.
16 skills · plugin
curated
n8n Workflow Automation
For n8n users building modular, reusable workflows with sub-workflows, error handling, and naming conventions.
7 skills · plugin
@owl-listener
Design Systems
Design system skills: component specs, design tokens, naming conventions, spacing and grid systems, accessibility standards, and documentation.
11 skills · plugin
Results for “naming-conventions”
7 skills
bytesagain Sku
Reference for designing SKU naming conventions, product hierarchies, and inventory classification schemes.
12 · bundle
tools-only 180 Name Aa5fe744
Guides the agent through structured protocols for writing technical specifications, implementation plans, and summaries, with file naming and task directory conventions.
7 · bundle
More results
czlonkowski N8n Subworkflows
Build reusable, composable n8n sub-workflows with typed inputs, stateless or stateful design, and discoverable naming conventions.
5.7k · bundle
wondelai Monetizing Innovation
Design products and pricing around validated willingness to pay, using the framework from Ramanujam & Tacke's "Monetizing Innovation" to avoid common monetization failures.
1.6k · bundle
alirezarezvani Commercial Policy
Design or revise a company's commercial policy governing discounts, approver thresholds, exception flows, and deal frameworks using data-backed matrices and linting tools.
20.4k · bundle
micsapp Plugin Structure
This skill should be used when the user asks to "create a plugin", "scaffold a plugin", "understand plugin structure", "organize plugin components", "set up plugin.json", "use ${CLAUDE_PLUGIN_ROOT}", "add commands/agents/skills/hooks", "configure auto-discovery", or needs guidance on plugin directory layout, manifest configuration, component organization, file naming conventions, or Claude Code plugin architecture best practices.
3 · bundle
curiositech MCP Server Design
Use when designing, building, or debugging a Model Context Protocol (MCP) server in Node/TypeScript. Triggers: stdio JSON-RPC handshake, tool descriptions as discovery surface, lazy startup vs eager catalog loading, telemetry placement, schema design for tool inputs (zod), tool naming conventions for discoverability, error handling that does not leak stack traces, MCP client compatibility (Claude Desktop, Claude Code, Cursor), local resource fetching, secrets and env var handling, distributing as npm + claude mcp add. NOT for MCP client implementation, MCP HTTP transport (different surface), Anthropic Agent SDK building, or non-MCP plugin systems.
10