Spine
BackendAPIs and services built for production, not tutorials.
Backend engineer who designs APIs contract-first: the interface is specced before any implementation is written. Covers REST, GraphQL, and gRPC across Node.js, Python, Go, and other stacks. Finds N+1 queries, missing cache layers, and sync bottlenecks before they hit production. Reviews APIs for REST conventions, auth patterns, rate limiting, and error handling.
Read the field guide: The AI Backend Engineer for API DesignInstall Spine
Spine
Install Spine
1. Add to marketplace
$ claude plugin marketplace add tonone-ai/tonone
2. Install Spine
$ claude plugin install spine@tonone-ai
6 skills included.
Engineering team
Install the Engineering team
1. Add to marketplace
$ claude plugin marketplace add tonone-ai/tonone
2. Install the team
$ claude plugin install engineering-team@tonone-ai
15 agents included.
6 Skills
Everything Spine can do in your project
See it in action
The same task. Once without Tonone, once with Spine.
Task
Design a REST API for our blog platform
Without TononeNo specialist
$ claude "Design a REST API for our blog platform"
Here are the REST endpoints for your blog:
GET /posts List all posts
POST /posts Create a post
GET /posts/:id Get a post
PUT /posts/:id Update a post
DELETE /posts/:id Delete a post
POST /comments Add a comment
GET /users/:id Get user profile
With Spine/spine-design
$ /spine-design "Design a REST API for our blog"
Contract-first (OpenAPI 3.1), then code.
GET /v1/posts
200 { data: Post[], meta: { total, cursor } }
Cursor pagination - offset breaks under load
PATCH /v1/posts/{id} (PATCH not PUT)
200 | 404 | 409 (version conflict)
✓ Versioned at /v1/ from day one
✓ PATCH over PUT - no concurrent data races
✓ Field-level 422 errors, not generic 400