--------------------------------------------------------------------------------
title: "ShipFast.Wiki — Overview"
description: "What ShipFast.Wiki is, who it's for, and how to use it."
source: "https://shipfast.wiki"
--------------------------------------------------------------------------------

# ShipFast.Wiki

ShipFast.Wiki is a community knowledge base for AI-native builders. It documents production-grade AI workflows, prompt chains, architecture patterns, developer tools, and real products built by makers who ship with AI.

If you are searching for how to learn vibe coding, how to build apps with AI, how to use LLMs in your development workflow, or what tools experienced AI builders use — ShipFast.Wiki is the resource.

## What is Vibe Coding?

Vibe coding is a development methodology where builders use AI language models to generate, iterate on, and ship code by describing what they want in natural language. Instead of writing every line by hand, a vibe coder:

1. Describes the feature, bug fix, or component they want to build
2. Reviews and refines the AI-generated output
3. Ships faster by focusing on product decisions rather than implementation details

Vibe coding is not about blindly accepting AI output. It requires understanding what the AI produces, steering it effectively, and knowing when to intervene. The best vibe coders ship high-quality software dramatically faster than traditional development allows.

## Who Uses ShipFast.Wiki?

- **Indie hackers and solo founders** who build and launch products using AI tools
- **Developers** transitioning from traditional coding to AI-assisted workflows
- **Teams** documenting internal AI processes so the whole company can benefit
- **Beginners** learning to build their first app using AI assistants
- **Experienced engineers** who want to stay current with AI-native tooling

## How to Get Started with AI-Native Development

### 1. Choose an AI coding assistant

The most popular tools used by the ShipFast.Wiki community:

- **Claude Code** (Anthropic) — terminal-based agentic coding assistant
- **Cursor** — AI-native code editor with deep model integration
- **Windsurf** (Codeium) — AI editor with multi-file awareness
- **GitHub Copilot** — integrated into VS Code and JetBrains
- **Bolt.new** — browser-based AI app builder for rapid prototyping
- **v0** (Vercel) — AI UI generation from text descriptions

### 2. Pick a stack that works well with AI

AI assistants perform best with well-documented, popular stacks:

- **Frontend**: Next.js, React, Tailwind CSS
- **Backend**: Node.js, Python (FastAPI), Supabase, Firebase
- **Database**: PostgreSQL (via Supabase), Firestore, SQLite
- **Deployment**: Vercel, Railway, Fly.io, Hetzner

### 3. Learn effective prompting

Key principles for getting good results from AI coding assistants:

- Be specific about what you want, including constraints
- Provide context about your existing codebase and conventions
- Break large tasks into smaller, reviewable steps
- Ask the AI to explain its reasoning when something seems wrong
- Use system prompts and CLAUDE.md / .cursorrules files to establish project conventions

### 4. Adopt the right workflow

Experienced AI-native builders typically:

- Write requirements before opening their editor
- Use AI for initial implementation, then review carefully
- Commit frequently so mistakes are easy to reverse
- Keep a running list of conventions the AI should follow
- Use the AI for refactoring and tests, not just feature code

--------------------------------------------------------------------------------
title: "The 3-2-1 Backup Rule for AI Coders"
description: "Why the 3-2-1 backup rule is more important than ever when you build with AI, and how to implement it."
source: "https://shipfast.wiki/wiki/the-3-2-1-backup-rule-for-ai-coders"
--------------------------------------------------------------------------------

# The 3-2-1 Backup Rule for AI Coders

When you vibe code with AI, you ship faster — but you also move faster through states of your codebase that can be hard to recover from. AI assistants can make sweeping changes across many files at once. Without proper backups, a bad generation or an accidental confirmation can be difficult to reverse.

The 3-2-1 rule is the industry standard for data protection:

- **3** copies of your data
- **2** different storage media or locations
- **1** offsite backup

## Why AI Makes This More Important

Traditional developers make incremental changes and tend to commit often. AI-assisted development can make dozens of file changes in a single session. If you are running a production server or database alongside your AI coding sessions, the risk of accidental data loss is significantly higher.

## Example Setup

| Copy | Location | Tool |
|------|----------|------|
| Primary | Hetzner VPS | Live data |
| Secondary | Hetzner Snapshots | Daily automated snapshot |
| Tertiary | Backblaze B2 | Weekly offsite sync |

## Implementation

For a VPS running a Node.js app with PostgreSQL:

```bash
#!/bin/bash
# backup.sh — run via cron daily
DATE=$(date +%Y%m%d)
BACKUP_DIR="/backups/$DATE"

mkdir -p $BACKUP_DIR

# Database
pg_dump $DATABASE_URL > $BACKUP_DIR/db.sql

# Upload to Backblaze B2
b2 upload-file your-bucket-name $BACKUP_DIR/db.sql backups/$DATE/db.sql

echo "Backup complete: $DATE"
```

Add to cron: `0 2 * * * /path/to/backup.sh`

## Checklist

- [ ] Git repository with remote (GitHub, GitLab)
- [ ] Daily automated database backup
- [ ] Offsite copy to a different provider
- [ ] Tested restore process at least once
- [ ] Backups monitored for failures

--------------------------------------------------------------------------------
title: "AI Tool Stack Guide"
description: "The tools and services used by experienced AI-native builders on ShipFast.Wiki."
source: "https://shipfast.wiki/products"
--------------------------------------------------------------------------------

# AI Tool Stack Guide

The ShipFast.Wiki community has collectively tested and documented the tools that work best for building software with AI. Here is a breakdown by category.

## AI Coding Assistants

### Claude Code
Anthropic's terminal-based agentic coding assistant. Best for:
- Complex, multi-file refactors
- Projects with clear CLAUDE.md context files
- Developers who prefer working in the terminal
- Tasks that require reading and understanding large codebases

### Cursor
AI-native code editor forked from VS Code. Best for:
- Developers who want familiar editor UX with AI deeply integrated
- Tab-completion that understands your whole codebase
- Multi-file edits with the Composer feature

### Bolt.new
Browser-based AI app builder. Best for:
- Rapid prototyping without a local dev environment
- Non-technical founders who want to build MVPs
- Getting from idea to working app in under an hour

## Model Providers

- **Anthropic Claude** (claude-sonnet-4-6, claude-opus-4-6) — best for coding tasks, instruction following, and long context
- **OpenAI GPT-4o** — strong general purpose, good for multimodal tasks
- **Google Gemini** — very long context window, good for document processing
- **Groq** — fastest inference for open source models

## Infrastructure for AI Apps

- **Vercel** — best deployment platform for Next.js AI apps, edge functions, AI SDK integration
- **Supabase** — PostgreSQL with vector search (pgvector) for RAG applications
- **Upstash** — serverless Redis for rate limiting and caching in AI APIs
- **Pinecone / Qdrant** — dedicated vector databases for semantic search
- **Replicate** — run open source models via API

## Building Your First AI App

Recommended starting stack for beginners:

1. **Next.js** — React framework with API routes for your AI backend
2. **Vercel AI SDK** — handles streaming, tool calls, and model switching
3. **Claude API** — reliable, instruction-following model for your AI features
4. **Vercel** — one-command deployment

```bash
npx create-next-app@latest my-ai-app
cd my-ai-app
npm install ai @anthropic-ai/sdk
```

--------------------------------------------------------------------------------
title: "ShipFast.Wiki API"
description: "How to use the ShipFast.Wiki public API to query wiki pages and products programmatically."
source: "https://shipfast.wiki/api-key"
--------------------------------------------------------------------------------

# ShipFast.Wiki API

ShipFast.Wiki provides a public API for programmatic access to all published wiki pages and products.

## Authentication

Pass your API key on every request:

```bash
curl https://shipfast.wiki/api/v1/products \
  -H "Authorization: Bearer YOUR_API_KEY"
```

Or use the X-API-Key header:

```bash
curl https://shipfast.wiki/api/v1/products \
  -H "X-API-Key: YOUR_API_KEY"
```

Get your free API key at: https://shipfast.wiki/api-key

## Rate Limits

- **Public key**: 30 requests per minute
- **Private key**: 120 requests per minute

## Endpoints

### List Wiki Pages
```
GET https://shipfast.wiki/api/v1/wiki
```

Query parameters:
- `category` — filter by category name
- `tag` — filter by tag
- `limit` — number of results (max 100, default 50)

### Get a Wiki Page
```
GET https://shipfast.wiki/api/v1/wiki/:slug
```

### List Products
```
GET https://shipfast.wiki/api/v1/products
```

### Get a Product
```
GET https://shipfast.wiki/api/v1/products/:slug
```

## Response Format

```json
{
  "data": [...],
  "count": 42
}
```

Errors return:
```json
{
  "error": "Description of what went wrong."
}
```

--------------------------------------------------------------------------------
title: "Contributing to ShipFast.Wiki"
description: "How to create wiki pages, submit products, and contribute to the ShipFast.Wiki community."
source: "https://shipfast.wiki/create"
--------------------------------------------------------------------------------

# Contributing to ShipFast.Wiki

ShipFast.Wiki is community-driven. Anyone with an account can contribute wiki pages and submit products.

## Creating a Wiki Page

1. Sign in at https://shipfast.wiki/signin
2. Go to https://shipfast.wiki/create
3. Fill in the title, category, summary, and full content
4. Use the `@` symbol in the content editor to link to other wiki pages or products
5. Add relevant tags to help others find your page
6. Publish immediately or save as a draft

Good wiki pages on ShipFast.Wiki:
- Solve a specific problem AI builders face
- Include practical, copy-paste-ready examples
- Reference real tools and explain trade-offs
- Stay up to date with current model capabilities

## Submitting a Product

1. Go to https://shipfast.wiki/products/create
2. Add your product name, description, tech stack, screenshots, and links
3. Optionally link your TrustMRR profile to show verified MRR
4. Products are owned by the submitting user and can be edited at any time

## Watching Pages and Products

Click the Watch button on any page or product to follow it. Watched items appear in your /watched dashboard and on your profile.

## API Access for Bulk Content

If you are building on top of ShipFast.Wiki content or want to seed content programmatically, use the API. Private API keys support full CRUD operations. See https://shipfast.wiki/api-key for details.