Elevate projects to production quality using proven patterns...
Transform any project into production-quality software using proven patterns.
The Problem: Most projects fail in predictable ways—users can't set them up, accidents cause data loss, crashes waste hours of progress, code becomes unmaintainable, errors are cryptic. These aren't bugs; they're missing patterns.
The Solution: Elevate systematically applies 12 battle-tested patterns that distinguish amateur code from production software.
| Mode | When to Use | What Happens |
|---|---|---|
| New Project | Starting from scratch | Detect type → Generate scaffold with all patterns |
| Audit | Reviewing existing code | Detect type → Scan → Gap report |
| Transform | Elevating existing project | Audit + Propose + Generate missing pieces |
Three non-negotiable properties. If your project lacks any of these, fix them first.
Setup should verify. Mistakes should undo. Crashes should resume.
| # | Pattern | Litmus Test |
|---|---|---|
| 1 | Health (Doctor) | Can a new user run tool doctor and know what's missing? |
| 2 | Safety (Safety Net) | Can a mistake be undone in under 60 seconds? |
| 3 | Resilience (Statekeeper) | Can interrupted work resume without losing progress? |
| # | Pattern | Problem It Solves |
|---|---|---|
| 4 | Architecture | "The code is a tangled mess" |
| 5 | Data Models | "What shape is this data?" |
| 6 | Code Organization | "Where does this code go?" |
| 7 | Error Handling | "It failed but I don't know why" |
| 8 | Testing | "I'm afraid to change anything" |
| 9 | Build & Deploy | "How do I ship this?" |
| 10 | CLI UX | "This tool is confusing" |
| 11 | Documentation | "How does this work?" |
| 12 | State Persistence | "Where did my data go?" |
Scan for file markers to identify project type and load the appropriate checklist:
| File Markers | Project Type | Checklist |
|---|---|---|
pyproject.toml + [project.scripts] |
Python CLI | python-cli.md |
package.json + "bin" field |
Node.js CLI | node-cli.md |
manifest.json + "background" |
Browser Extension | browser-extension.md |
pyproject.toml + fastapi in deps |
REST API (Python) | rest-api.md |
package.json + express/hono/fastify |
REST API (Node) | rest-api.md |
mcp.json OR @modelcontextprotocol imports |
MCP Server | mcp-server.md |
action.yml or action.yaml |
GitHub Action | github-action.md |
For each of the 12 patterns, grep for indicators and score as Present, Partial, or Missing:
# Triad
grep -rE "(doctor|check|verify|preflight)" . # Health
grep -rE "(undo|restore|trash|dry-run)" . # Safety
grep -rE "(checkpoint|resume|state\.json)" . # Resilience
# Structure
grep -rE "(@dataclass|interface |TypedDict)" . # Data Models
grep -rE "(pytest|vitest|conftest|\.test\.)" . # Testing
# Quality
grep -rE "(retry|backoff|graceful)" . # Error Handling
## Gap Analysis: <project-name>
**Project Type**: <detected-type>
**Patterns Detected**: X/12
### Present
- [x] Pattern Name - evidence found
### Partial
- [~] Pattern Name - what exists, what's missing
### Missing
- [ ] Pattern Name - why it matters
For each gap, propose specific changes. Prioritize by impact:
For missing patterns, generate files from templates/<project-type>/:
A fully elevated project passes:
--json + --quietElevate: Because production-quality isn't about perfection—it's about patterns.