Plugins
4 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
@phuryn
Marketing Growth
Product marketing and growth skills: marketing ideas, value proposition statements, North Star metrics, product naming, and positioning.
5 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”
14 skills
lord1egypt Can Ask MCP
Integrates Clock Address Naming with MCP agents to locally stamp, verify, and log tool outputs with hashes and timestamps.
2
yanacuti1121 API Design
REST API design patterns including resource naming, status codes, pagination, filtering, error responses, versioning, and rate limiting for production APIs.
2
tangchunwu API Design
REST API design patterns including resource naming, status codes, pagination, filtering, error responses, versioning, and rate limiting for production APIs.
1
livelybug API Design
REST API design patterns including resource naming, status codes, pagination, filtering, error responses, versioning, and rate limiting for production APIs.
0
rajanthar API Design
REST API design patterns including resource naming, status codes, pagination, filtering, error responses, versioning, and rate limiting for production APIs.
0
kk20300113-png API Design
REST API design patterns including resource naming, status codes, pagination, filtering, error responses, versioning, and rate limiting for production APIs.
0
More results
anantha-236 API Design
REST API design patterns including resource naming, status codes, pagination, filtering, error responses, versioning, and rate limiting for production APIs.
1
czlonkowski N8n Subworkflows
Build reusable, composable n8n sub-workflows with typed inputs, stateless or stateful design, and discoverable naming conventions.
5.7k · bundle
eryajf Namecheap
Manage DNS records for domains registered with Namecheap via their API. List domains, view/add/update/remove DNS host entries (A, AAAA, CNAME, MX, TXT, etc.), and guide users through API setup including public IP detection and credential configuration. Use when the user mentions Namecheap, DNS records, domain management, or wants to add/change/remove A records, CNAME records, MX records, or TXT records for their domains.
0 · bundle
sakamoto-family-smile API Design
Design consistent REST APIs with resource naming, status codes, pagination, filtering, error responses, versioning, and rate limiting.
0
mhassan0000 API Design
Design consistent, developer-friendly REST APIs with resource naming, HTTP methods, status codes, pagination, filtering, sorting, authentication, and rate limiting.
1
affaan-m API Design
Design consistent, developer-friendly REST APIs with conventions for resource naming, HTTP methods, status codes, pagination, filtering, error responses, versioning, and rate limiting.
226k
kensaurus Design API
Design RESTful and GraphQL APIs following current best practices for naming, versioning, error shapes, and auth patterns. Use when the user says "design an API", "create endpoints", "structure my API responses", "plan API architecture", "REST vs GraphQL", or "API contract".
8
eryajf Dashboarding
Build, modify, and ship Grafana dashboards as JSON via the HTTP API — panel types (timeseries / stat / gauge / table / heatmap / logs / traces / node-graph), `gridPos` 24-column layout, units, thresholds, template + datasource + chained variables, transformations (`organize` / `calculateField` / `filterByValue`), panel + dashboard links with `${__field.labels.x}` / `${__from}`, and Loki/Prometheus annotations. Use when scripting dashboard creation, writing the dashboard JSON for a new service, adding a `$job` dropdown variable, computing an "Error %" column with a transformation, overlaying deploys as annotations, or pushing a dashboard via `POST /api/dashboards/db` — even when the user says "create a dashboard for this metric", "add a service dropdown", "show errors as percentage", "overlay our deploys", or "export the dashboard JSON" without naming the API or schema. After every API push, verify with the returned `version` plus a GET on the dashboard UID.
0 · bundle