A production-oriented framework for using AI in software delivery without weakening engineering accountability.
This project demonstrates how I structure AI-assisted software delivery as a senior engineer: with clear context, reusable prompts, human review checkpoints, secure tool boundaries, accessibility awareness, and measurable quality controls.
Shipwright AI Framework is a public portfolio project built on a production-minded Next.js starter. It is not a vibe-coding demo or a prompt dump. It is a structured engineering system for using AI responsibly across planning, implementation support, review, documentation, security analysis, accessibility workflows, and delivery evaluation.
The app and repository documentation are designed for engineering managers, tech leads, recruiters, AI enablement teams, and product teams adopting AI-assisted workflows.
AI can improve software delivery only when it is governed by strong engineering judgment, secure workflows, clear context, human review, and measurable quality controls.
This project makes that operating model concrete by showing:
- where AI is allowed to assist
- where humans must decide
- how prompts are governed
- how AI-generated code is reviewed
- how context is managed
- how security and privacy risks are controlled
- how accessibility workflows remain human-reviewed
- how delivery quality is measured over time
- Responsible AI usage policies
- Prompt-library governance
- AI-assisted PR review discipline
- Context engineering templates
- Security and privacy controls
- Accessibility-aware workflows
- Token-optimization guidance
- Human-in-the-loop approval checkpoints
- Workflow evaluation metrics
- Production-minded frontend delivery
- Operating model
- Responsible AI policy
- Prompt library
- AI PR review guidelines
- Context engineering
- Security threat model
- Token optimization
- Evaluation framework
- Accessibility AI workflow
- Example delivery workflows
The repository includes an end-to-end example called Accessible Button Component Delivery. It shows:
- human requirement definition
- AI planning prompt
- AI implementation prompt
- human architecture review
- code review checklist
- accessibility checks
- test checklist
- final PR summary
- human sign-off
- AI can propose, draft, summarize, and accelerate.
- Humans remain accountable for architecture, security, compliance, customer impact, and production approval.
- Confidential customer data, secrets, credentials, private keys, proprietary code, and sensitive business information must not be shared with AI tools unless the tool, contract, and data-processing setup explicitly allow it.
- AI-generated outputs require review for correctness, maintainability, accessibility, security, and architectural fit.
- The project uses source-informed and expert-review-ready language. It does not claim certification or expert approval.
AI assistance is treated as a reviewed contribution, not an autonomous production authority.
Key checkpoints:
- requirement approval
- context approval
- architecture review
- implementation review
- security and privacy review
- accessibility review
- test evidence review
- production or release approval
The project documents controls for:
- prompt injection
- secrets leakage
- customer data exposure
- insecure tool/plugin design
- excessive agent permissions
- repository write access risk
- dependency manipulation
- generated vulnerable code
- fake citations and unverifiable claims
- destructive action approval
Workflow quality is scored using practical measures:
- code quality
- review quality
- bug detection
- security issue detection
- accessibility issue detection
- documentation quality
- token efficiency
- developer time saved
- hallucination rate
- human correction rate
- rework rate
- Next.js App Router
- TypeScript
- Tailwind CSS
- Radix UI / shadcn-style source components
- pnpm
- ESLint
- Prettier
- Vitest
- React Testing Library
- Playwright
- GitHub Actions
pnpm install
pnpm devOpen http://localhost:3000.
The /jev-triage page uses Jev, TypeSafe AI's structured decision model, to suggest a risk score and a human review path for a pull request summary. To enable it, copy .env.example to .env.local and set TYPESAFE_API_KEY. Without a key, the page stays disabled. See docs/integrations/jev-pr-triage.md for boundaries, data handling, and abuse controls.
This screenshot shows the /jev-triage page rendering a response from a local mock of POST /v1/systemone, used to test the integration end to end.
pnpm lint
pnpm typecheck
pnpm test:run
pnpm test:e2e
pnpm format:check
pnpm build.
├─ docs/
├─ src/
│ ├─ app/
│ ├─ components/
│ ├─ content/
│ ├─ lib/
│ ├─ styles/
│ └─ types/
├─ tests/e2e/
├─ playwright.config.ts
├─ vitest.config.ts
└─ vitest.setup.tsThis project demonstrates how I structure AI-assisted software delivery as a senior engineer: with clear context, reusable prompts, human review checkpoints, secure tool boundaries, accessibility awareness, and measurable quality controls.
This project is source-informed and prepared for expert review. It does not claim legal, compliance, security, or accessibility certification.

