shipwright-pipeline
Autonomous app builder that converts plain-English descriptions into
git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace /tmp/shipwright-pipeline && cp -r /tmp/shipwright-pipeline/plugins/ai-agency/shipwright/skills/shipwright-pipeline ~/.claude/skills/shipwright-pipelineSKILL.md
# Shipwright Pipeline
## Overview
Shipwright converts a plain-English app description into a fully built, tested, and deployment-ready application. It delegates execution to `product-agent`, an autonomous 9-phase build engine available on PyPI.
## Prerequisites
- Python 3.10+ available in PATH.
- `product-agent` installed (`pip install product-agent`).
- Node.js 18+ for JavaScript/TypeScript stacks.
## Supported Stacks
- **Next.js + Supabase** — Full-stack with auth, database, and edge functions
- **Next.js + Prisma** — Full-stack with type-safe ORM
- **SvelteKit** — Lightweight full-stack with Svelte
- **Astro** — Content-focused static and hybrid sites
## Instructions
1. Gather the app description from the user. Ask clarifying questions if the description is vague.
2. Confirm the target stack. If none specified, recommend based on the app type:
- Data-heavy with auth: Next.js + Supabase
- API-first with complex models: Next.js + Prisma
- Lightweight interactive: SvelteKit
- Content or marketing site: Astro
3. Run `product-agent` with the app description and selected stack.
4. Monitor the 9-phase pipeline: Intake, Architecture, Scaffold, Implement, Test, Integrate, Polish, Validate, Ship.
5. Report results to the user including test summary and any warnings.
## Output
- A complete, buildable project directory with all source code, tests, and configuration.
- A test report summarizing pass/fail counts.
- Build verification output confirming the project compiles and starts.
## Error Handling
- If `product-agent` is not installed, prompt the user to install it with `pip install product-agent`.
- If a phase fails, report the phase name, error message, and suggested fix.
- If the selected stack is not supported, list available stacks and ask the user to choose.
## Examples
**Build a SaaS dashboard:**
```
/shipwright-build Build a real-time analytics dashboard with user auth, team workspaces, and Stripe billing. Use Next.js + Supabase.
```
**Add features to an existing project:**
```
/shipwright-enhance Add dark mode toggle, export-to-CSV on all tables, and email notification preferences.
```
**Scaffold a content site:**
```
/shipwright-build Create a developer documentation site with search, versioned docs, and a blog. Use Astro.
```
## Resources
- [Shipwright on GitHub](https://github.com/Wynelson94/shipwright)
- [product-agent on PyPI](https://pypi.org/project/product-agent/)
- See `${CLAUDE_SKILL_DIR}/references/examples.md` for usage examples.Guard the beads execution record: enforce the write-flush-verify discipline that defeats the bd rapid-write race, audit epic dependency graphs for cycles and orphans, catch closures whose title overstates what shipped, flag open beads carrying no disposition or a disproven premise, and reconcile bd against its GitHub and Plane projections. Owns RECORD INTEGRITY; delegates graph analysis to bead-dependency-mapper and epic-closure drift to bead-epic-auditor rather than duplicating them. Use before closing an epic, after any batch of bd writes, when a bead premise looks stale, or when auditing whether the record matches reality. Trigger with "audit beads", "check the bead DAG", "did that close actually land", "bead hygiene".
Verify every factual assertion in a diff, PR body, commit message, bead note, or governing doc against the actual repository, and fail anything that cannot be substantiated by a command. Use before merging any PR that makes claims about counts, coverage, consumers, enforcement, provenance, or certification, and when auditing standing docs for rot. Trigger with "verify claims", "check this PR body", "is this claim true", "claim audit".
Design and build Omarchy (Quickshell/QML) bar-widget, panel, and service plugins that actually work on a stock install. Knows the hard runtime constraint (no node on the graphical session PATH), the first-party contracts (BarWidget, Panel, KeyboardPanel, PanelKeyCatcher, Service), the curl-from-QML data pattern, FileView persistence, and the marketplace submission bar. Use when starting a new Omarchy plugin, porting a plugin off an external runtime, wiring a service to a bar widget, or deciding how a widget should fetch and persist. Trigger with "build an omarchy plugin", "omarchy widget", "quickshell plugin", "port this plugin to QML".
Audit an Omarchy plugin before it reaches the marketplace: prove it installs and runs on a stock box (no node/python on the session PATH), run the omarchy-submit gate lane, validate on the rig with omarchy-plugin-validate and qmllint, and check the QML security invariants and first-party idiom contracts. Read-only: it reports and blocks, it does not rewrite the plugin. Use before submitting an entry, after any data-layer change, or when a plugin works on the dev box and you need to know whether it works for a real user. Trigger with "audit this omarchy plugin", "is this plugin submission ready", "will this plugin work when installed".
Audit and fix Claude Code SKILL.md files against enterprise compliance standards: frontmatter completeness, required body sections, and style. Use when validating or repairing skills in a plugin directory. Trigger with "audit skill", "fix skill compliance".
Learn how SKILL.md files work in Claude Code plugins, then build a production-quality agent skill from scratch. Covers frontmatter schema, body structure, testing, and iteration.
Step-by-step guide to writing a SKILL.md file for Claude Code. Learn how to plan, structure, and test auto-activating skills with proper frontmatter, allowed-tools, dynamic context injection, and supporting files.
|