hono-api-scaffolder
Generate structured API routes, middleware, and documentation for Cloudflare Workers projects using Hono.
Works with
1
total installs
1
this week
697
GitHub stars
0
upvotes
Install Skill
Run in your terminal
1
installs
1
this week
697
stars
What it does
Creates resource-grouped route files with Zod validation, typed bindings, and error handling
Includes auth middleware templates, CORS setup, and end-to-end RPC type safety patterns
Generates API_ENDPOINTS.md documentation with endpoint signatures, auth requirements, and response schemas
Designed to run after project initialization via cloudflare-worker-builder or vite-flare-st
Installation Guide
How to use hono-api-scaffolder on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your machine
- ›Node.js 16+ with npm — verify with
node --version - ›Active project directory where you want to add
hono-api-scaffolder
Run the install command
Execute the skills CLI command in your project's root directory to begin installation:
Fetches hono-api-scaffolder from jezweb/claude-skills and configures it for Cursor.
Select Cursor when prompted
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate hono-api-scaffolder. Access via /hono-api-scaffolder in your agent's command palette.
Security Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Documentation
Hono API Scaffolder
Add structured API routes to an existing Cloudflare Workers project. This skill runs AFTER the project shell exists (via cloudflare-worker-builder or vite-flare-starter) and produces route files, middleware, and endpoint documentation.
Workflow
Step 1: Gather Endpoints
Determine what the API needs. Either ask the user or infer from the project description. Group endpoints by resource:
Users: GET /api/users, GET /api/users/:id, POST /api/users, PUT /api/users/:id, DELETE /api/users/:id
Posts: GET /api/posts, GET /api/posts/:id, POST /api/posts, PUT /api/posts/:id
Auth: POST /api/auth/login, POST /api/auth/logout, GET /api/auth/me
Step 2: Create Route Files
One file per resource group. Use the template from assets/route-template.ts:
// src/routes/users.ts
import { Hono } from 'hono'
import { zValidator } from '@hono/zod-validator'
import { z } from 'zod'
import type { Env } from '../types'
const app = new Hono<{ Bindings: Env }>()
// GET /api/users
app.get('/', async (c) => {
const db = c.env.DB
const { results } = await db.prepare('SELECT * FROM users').all()
return c.json({ users: results })
})
// GET /api/users/:id
app.get('/:id', async (c) => {
const id = c.req.param('id')
const user = await db.prepare('SELECT * FROM users WHERE id = ?').bind(id).first()
if (!user) return c.json({ error: 'Not found' }, 404)
return c.json({ user })
})
// POST /api/users
const createUserSchema = z.object({
name: z.string().min(1),
email: z.string().email(),
})
app.post('/', zValidator('json', createUserSchema), async (c) => {
const body = c.req.valid('json')
// ... insert logic
return c.json({ user }, 201)
})
export default app
Step 3: Add Middleware
Based on project needs, add from assets/middleware-template.ts:
Auth middleware — protect routes requiring authentication:
import { createMiddleware } from 'hono/factory'
import type { Env } from '../types'
export const requireAuth = createMiddleware<{ Bindings: Env }>(async (c, next) => {
const token = c.req.header('Authorization')?.replace('Bearer ', '')
if (!token) return c.json({ error: 'Unauthorized' }, 401)
// Validate token...
await next()
})
CORS — use Hono's built-in:
import { cors } from 'hono/cors'
app.use('/api/*', cors({ origin: ['https://example.com'] }))
Step 4: Wire Routes
Mount all route groups in the main entry point:
// src/index.ts
import { Hono } from 'hono'
import type { Env } from './types'
import users from './routes/users'
import posts from './routes/posts'
import auth from './routes/auth'
import { errorHandler } from './middleware/error-handler'
const app = new Hono<{ Bindings: Env }>()
// Global error handler
app.onError(errorHandler)
// Mount routes
app.route('/api/users', users)
app.route('/api/posts', posts)
app.route('/api/auth', auth)
// Health check
app.get('/api/health', (c) => c.json({ status: 'ok' }))
export default app
Step 5: Create Types
// src/types.ts
export interface Env {
DB: D1Database
KV: KVNamespace // if needed
R2: R2Bucket // if needed
API_SECRET: string // secrets
}
Step 6: Generate API_ENDPOINTS.md
Document all endpoints. See references/endpoint-docs-template.md for the format:
## POST /api/users
Create a new user.
- **Auth**: Required (Bearer token)
- **Body**: `{ name: string, email: string }`
- **Response 201**: `{ user: User }`
- **Response 400**: `{ error: string, details: ZodError }`
Key Patterns
Zod Validation
Always validate request bodies with @hono/zod-validator:
import { zValidator } from '@hono/zod-validator'
app.post('/', zValidator('json', schema), async (c) => {
const body List & Monetize Your Skill
Submit your Claude Code skill and start earning
Get started →Use Cases
Task Automation & Efficiency
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Knowledge Enhancement
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Quality Improvement
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
Implementation Guide
Prerequisites
- ›Claude Desktop or compatible AI client with skill support
- ›Clear understanding of task or problem to solve
- ›Willingness to iterate and refine outputs
Time Estimate
15-45 minutes depending on use case complexity
Steps
- 1Install skill using provided installation command
- 2Test with simple use case relevant to your work
- 3Evaluate output quality and relevance
- 4Iterate on prompts to improve results
- 5Integrate into regular workflow if valuable
Common Pitfalls
- ⚠Expecting perfect results without iteration
- ⚠Not providing enough context in prompts
- ⚠Using skill for tasks outside its intended scope
- ⚠Accepting outputs without review and validation
Best Practices
✓ Do
- +Start with clear, specific prompts
- +Provide relevant context and constraints
- +Review and refine all outputs before using
- +Iterate to improve output quality
- +Document successful prompt patterns
✗ Don't
- −Don't use without understanding skill limitations
- −Don't skip validation of outputs
- −Don't share sensitive information in prompts
- −Don't expect skill to replace human judgment
💡 Pro Tips
- ★Be specific about desired format and style
- ★Ask for multiple options to choose from
- ★Request explanations to understand reasoning
- ★Combine AI efficiency with human expertise
When to Use This
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
Learning Path
- 1Familiarize yourself with skill capabilities and limitations
- 2Start with low-risk, non-critical tasks
- 3Progress to more complex and valuable use cases
- 4Build expertise through regular use and experimentation
Related Skills
wordpress-elementor
84jezweb/claude-skills
react-native
20jezweb/claude-skills
zustand-state-management
7jezweb/claude-skills
rest-api-design
7aj-geddes/useful-ai-prompts
typescript-best-practices
96jwynia/agent-skills
google-search-console
41kostja94/marketing-skills
Reviews
- AAva Gonzalez★★★★★Dec 28, 2024
Useful defaults in hono-api-scaffolder — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- CChaitanya Patil★★★★★Dec 20, 2024
I recommend hono-api-scaffolder for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- TTariq Perez★★★★★Dec 8, 2024
Solid pick for teams standardizing on skills: hono-api-scaffolder is focused, and the summary matches what you get after install.
- LLi Dixit★★★★★Dec 4, 2024
hono-api-scaffolder has been reliable in day-to-day use. Documentation quality is above average for community skills.
- NNikhil Nasser★★★★★Nov 27, 2024
hono-api-scaffolder is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- NNikhil Abbas★★★★★Nov 23, 2024
hono-api-scaffolder reduced setup friction for our internal harness; good balance of opinion and flexibility.
- WWilliam Harris★★★★★Nov 19, 2024
I recommend hono-api-scaffolder for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- PPiyush G★★★★★Nov 11, 2024
Useful defaults in hono-api-scaffolder — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- NNikhil Chen★★★★★Oct 18, 2024
hono-api-scaffolder fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- NNikhil Ramirez★★★★★Oct 14, 2024
I recommend hono-api-scaffolder for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
showing 1-10 of 42
Discussion
Comments — not star reviews- No comments yet — start the thread.