Packs
4 packscurated
Build GraphQL API
Design a GraphQL schema, implement resolvers with DataLoader, and integrate with Apollo.
4 skills · pack
curated
Full-Stack Backend Platforms
For developers building backends with Convex, Firebase, or Django, covering schema design, real-time features, and deployment.
10 skills · pack
@fradser
Hardware
Hardware and EDA toolkit. Drives the KiCad CLI for schematic/PCB export and checks, and OpenSCAD for parametric 3D/2D part design and STL/DXF/PNG output.
2 skills · pack
@alirezarezvani
Engineering
37 advanced engineering skills: agent designer, agent workflow designer, RAG architect, database designer + schema designer + SQL assistant, migration architect, observability designer, dependency auditor, changelog generator (with semantic version bumper and hotfix/rollback procedures), API design reviewer, API test suite builder, CI/CD pipeline builder, MCP server builder, skill security auditor
33 skills · pack
Results for “schema”
5 skillsbreakdown-feature-implementation
Creates detailed technical implementation plans for features based on a Feature PRD, including system architecture, database schema, API design, and frontend component hierarchy.
36.2k
build-blueprint
Designs an edit blueprint and uncertainty register for video projects, following a narrative loop and schema constraints.
3
More results
scope
Turns product ideas into structured specs for AI tools or stakeholder review, with quick feature specs and full project scopes.
54 · bundle
superpowers-sage-wp-rest-api
WordPress REST API — register_rest_route, WP_REST_Controller, WP_REST_Request, REST namespace, custom endpoints, Application Passwords, JWT REST authentication, permission_callback, schema validation, WP_REST_Response, REST API versioning, rest_ensure_response, coexistence with Acorn Routes, register_rest_route vs routes/web.php decision, REST API debugging, wp rest-api namespace list, wp json discovery, CORS, REST nonce, cookie auth, REST API disable, JSON schema validation
13 · bundle
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