shipwright
NewClaude skills that make your AI ship production-grade Next.js/React/TS code, not demos. Catches leaked secrets, missing error states, unvalidated input, and 'use client' sprawl.
Summary
js, React, and TypeScript projects.
- It catches common pitfalls like leaked secrets, missing error states, unvalidated input, and excessive 'use client' directives, helping developers ship robust, secure, and maintainable code instead of demos.
Install & Usage
mkdir -p .claude/skillsmkdir -p .claude/skills && curl -o .claude/skills/shipwright.md https://raw.githubusercontent.com/EponymousBearer/shipwright/main/SKILL.md/shipwrightUse Cases
Usage Examples
/shipwright review src/app/api/*.ts for input validation and error handling
Check this component for missing error states and empty states: src/components/UserList.tsx
/shipwright audit --fix 'use client' sprawl in pages/ directory
Security Audits
Frequently Asked Questions
What is shipwright?
Shipwright is a Claude Code skill that enforces production-grade standards for Next.js, React, and TypeScript projects. It catches common pitfalls like leaked secrets, missing error states, unvalidated input, and excessive 'use client' directives, helping developers ship robust, secure, and maintainable code instead of demos.
How to install shipwright?
To install shipwright: create the skills directory (mkdir -p .claude/skills), then run: mkdir -p .claude/skills && curl -o .claude/skills/shipwright.md https://raw.githubusercontent.com/EponymousBearer/shipwright/main/SKILL.md. Finally, /shipwright in Claude Code.
What is shipwright best for?
shipwright is a skill categorized under General. Created by EponymousBearer.
What can I use shipwright for?
shipwright is useful for: Scan a Next.js project for hardcoded API keys or secrets before committing.; Review a React component for missing loading, empty, and error state handling.; Audit a TypeScript codebase for unvalidated user input in API routes or forms.; Identify and refactor unnecessary 'use client' directives to improve server-side rendering.; Check a pull request for production-readiness, including proper error boundaries and data validation.; Enforce consistent patterns for server actions, client components, and data fetching in Next.js..