A documentation-first starter kit for creating production-grade projects with Cursor AI and Claude Code through manual, step-by-step setup using copy-paste prompts and AI-optimized templates.
Starting-Documents is a meticulously organized collection of templates, guides, and prompts designed to help developers create production-ready applications using AI-assisted development. Unlike traditional boilerplates that give you code, this gives you a system - a repeatable, manual process for building any project with AI as your primary coding partner.
- Documentation First: Generate comprehensive docs before writing code
- Manual Setup: Copy-paste prompts over automation for flexibility
- AI-Optimized: Every file under 500 lines, functional patterns, clear naming
- Phase-Based Development: 6 structured phases from setup to production
- Context Persistent: Maintains AI understanding across sessions
- Stack Flexible: Core docs stay generic with stack-specific profiles
Starting-Documents/
βββ π Core Documentation
β βββ README.md # Original overview
β βββ README2.md # This file - comprehensive guide
β βββ START-HERE.md # Quick-start entry point
β βββ LICENSE # MIT license
β
βββ π 01-templates/ # Ready-to-use document templates
β βββ ai-config/ # AI assistant configuration
β β βββ CLAUDE.md # Persistent context template
β β βββ .cursor/rules/ # Modular rules system
β βββ project-docs/ # Core documentation templates
β βββ phases/ # Development phase checklists (0-5)
β βββ checklists/ # Progress tracking templates
β βββ adr/ # Architecture Decision Records
β βββ project-skeleton/ # Example package.template.json
β
βββ π 02-examples/ # Reference implementations
β βββ themes/ # Design system examples
β βββ TAN-THEME-RULES.md # Earthy minimalist theme
β
βββ π 03-guides/ # How-to guides and workflows
β βββ setup/ # Configuration guides
β β βββ NEW-PROJECT-SETUP.md # Manual setup (start here)
β β βββ DATABASE-OVERVIEW.md # SQLite β Supabase
β β βββ DEPLOYMENT-GUIDE.md # Vercel deployment
β β βββ MCP-SETUP-GUIDE.md # Model Context Protocol
β β βββ SNYK-SETUP-GUIDE.md # Security scanning
β β βββ CURSOR-RULES-SETUP-GUIDE-2025.md
β βββ workflow/ # Development workflows
β β βββ prompts/ # AI prompt templates
β β β βββ PROMPTS-INITIAL-DOCS.md
β β β βββ PROMPTS-PLANNING-TRACKING.md
β β β βββ PROMPTS-ADVANCED-MAINTENANCE.md
β β βββ experimental/ # Theoretical explorations
β β βββ [workflow guides]
β βββ maintenance/ # Ongoing maintenance
β βββ PROJECT-HISTORY-INS.md
β βββ audits/ # Audit prompt templates
β βββ _archive/ # Archived plans
β
βββ π profiles/ # Stack-specific configurations
β βββ nextjs-react/ # Next.js/React notes
β
βββ π project_brainstorm/ # Your project ideas (empty starter)
β
βββ π Configuration Files
βββ package.template.json # Example package.json
βββ .gitignore # Git ignore rules
βββ .prettierrc # Code formatting config
βββ .editorconfig # Editor configuration
AI assistant configuration templates for optimal performance:
- CLAUDE.md - Persistent memory template for Claude Code/Cursor sessions
- .cursor/ - Modern modular rules system
- rules.mdc - Index file (NOT always-apply)
- rules/000-core.mdc - Universal coding principles
- rules/900-context.mdc - Context persistence rules
- rules/modules/ - Optional domain-specific rules
Core documentation templates to define your project:
- PROJECT-OVERVIEW-TEMPLATE.md - Define purpose, goals, success metrics
- USER-FLOW-TEMPLATE.md - Map user journeys and interactions
- TECH-STACK-TEMPLATE.md - Document technology choices
- UI-RULES-TEMPLATE.md - UI/UX principles and patterns
- THEME-RULES-TEMPLATE.md - Design system and branding
- PROJECT-RULES-TEMPLATE.md - Code style and conventions
- API-RULES-TEMPLATE.md - API design patterns
- TESTING-RULES-TEMPLATE.md - Testing strategy and standards
Detailed development phase checklists (40-50 tasks each):
- phase-0-setup.md - Project initialization and configuration
- phase-0-claude-code.md - Claude-specific setup variant
- phase-0-cursor-claude.md - Dual-tool setup variant
- phase-1-frontend-foundation.md - UI components and layout
- phase-2-frontend-features.md - Interactive features
- phase-3-backend-sqlite.md - Database and API setup
- phase-4-testing-polish.md - Testing and refinement
- phase-5-production-supabase.md - Production deployment
Progress tracking templates:
- KEY-FEATURES-TEMPLATE.md - Feature implementation tracking
- PAGES-URLS-TEMPLATE.md - Route and page status
Complete theme examples:
- TAN-THEME-RULES.md - Earthy, minimalist design system
Example brainstorming documents (currently placeholder files)
Configuration and setup guides:
- NEW-PROJECT-SETUP.md - Manual step-by-step project creation
- DATABASE-OVERVIEW.md - SQLite to Supabase migration path
- DEPLOYMENT-GUIDE.md - Vercel deployment with troubleshooting
- MCP-SETUP-GUIDE.md - Model Context Protocol for AI-DB operations
- SNYK-SETUP-GUIDE.md - Security scanning configuration
- CURSOR-RULES-SETUP-GUIDE-2025.md - Modern Cursor rules implementation
Development workflow optimization:
- AI-WORKFLOW-OPTIMIZATION.md - 5-30x productivity techniques
- BEGINNER-TIPS.md - AI-first development for newcomers
- AI-Workflow-Combined.md - Integrated workflow strategies
- DUAL-AI-CHECKLIST-STRATEGY.md - Using multiple AI tools
- DUAL-AI-COORDINATION-GUIDE.md - Coordinating AI assistants
- CREW-AI-OVERVIEW.md - Multi-agent AI systems
- experimental/ - Theoretical explorations (e.g., Gemini CLI)
Structured AI prompt templates:
- PROMPTS-INITIAL-DOCS.md - Generate core documentation
- PROMPTS-PLANNING-TRACKING.md - Create phase plans and checklists
- PROMPTS-ADVANCED-MAINTENANCE.md - Advanced features and maintenance
Ongoing project maintenance:
- PROJECT-HISTORY-INS.md - Context persistence across sessions
- _archive/ - Archived improvement plans
Next.js and React specific configurations and notes
- technical-production-audit.md - Pre-deployment technical audit
- content-documentation-audit.md - Documentation completeness check
- Midproject-check-1.md - Mid-project review template
- Midproject-check-2.md - Alternative review approach
-
Start Here
- Read
START-HERE.mdfor overview - Review
03-guides/setup/NEW-PROJECT-SETUP.mdfor manual steps
- Read
-
Create Your Project Structure
mkdir my-new-project cd my-new-project mkdir -p _docs/phases project_brainstorm .cursor/rules -
Generate Core Documentation (Using AI)
- Follow prompts in
03-guides/workflow/prompts/PROMPTS-INITIAL-DOCS.md - Create: project-overview.md, user-flow.md, tech-stack.md
- Use templates from
01-templates/project-docs/as guides
- Follow prompts in
-
Set Up AI Configuration
- Copy
01-templates/ai-config/.cursor/to your project - Copy
01-templates/ai-config/CLAUDE.mdto your project root - Customize for your specific needs
- Copy
-
Plan Your Phases
- Copy relevant phase templates from
01-templates/phases/ - Customize checklists for your project
- Start with Phase 0 (setup)
- Copy relevant phase templates from
-
Begin Development
- Work through phases sequentially
- Update project-history.md every 5-10 file changes
- Use AI with provided prompts for implementation
- Brainstorm β
project-overview.md user-flow.md(end-to-end journeys)tech-stack.md(with migration plan)ui-rules.md+theme-rules.mdproject-rules.md- Optional:
api-rules.md,testing-rules.md, ADRs - Phases
phase-0throughphase-5 - AI rules (
.cursor/rules/) +CLAUDE.md - Deployment & CI (optional)
project-history.md(continuous updates)
All prompts to create these are in 03-guides/setup/NEW-PROJECT-SETUP.md and 03-guides/workflow/prompts/.
Phase 0: Setup & Configuration - Environment, tools, git setup
Phase 1: Frontend Foundation - Layout, navigation, design system
Phase 2: Frontend Features - Interactive components, state, forms
Phase 3: Backend Integration - SQLite database, API routes, auth
Phase 4: Testing & Polish - Tests, performance, accessibility
Phase 5: Production Deployment - Supabase migration, Vercel, monitoring
Example package.json showing recommended dependencies and scripts
Modern modular rules for Cursor AI:
- Index file with
alwaysApply: false - Core rules under 100 lines
- Context management rules
- Optional domain-specific modules
Persistent context template maintaining:
- Project conventions
- Architecture decisions
- Recent changes
- Current status
Create comprehensive documentation before writing code. This ensures clarity, reduces rework, and provides excellent context for AI assistants.
- Files under 500 lines for optimal AI processing
- Functional programming patterns
- Descriptive naming conventions
- Clear file organization
- Update project-history.md every 5-10 file changes
- Maintain CLAUDE.md for session continuity
- Use modular Cursor rules to avoid context bloat
- Start with SQLite for rapid prototyping
- Migrate to Supabase when ready for production
- Use phases to manage complexity
- Use Cursor for implementation and refinement
- Use Claude Code for planning and architecture
- Coordinate through shared documentation
-
Morning Planning (When Sharp)
- Review project documentation
- Plan complex features
- Update phase checklists
-
Afternoon Implementation (AI-Assisted)
- Use Cursor Composer for multi-file changes
- Let AI handle repetitive tasks
- Focus on reviewing and guiding
-
Evening Cleanup
- Update project-history.md
- Run tests and linting
- Commit changes with clear messages
- Start with
BEGINNER-TIPS.mdandSTART-HERE.md - Focus on Phase 0 initially - don't rush ahead
- Use the TAN theme example as a starting point
- Ask AI to explain concepts with "As a beginner, explain..."
- Jump to
AI-WORKFLOW-OPTIMIZATION.mdfor 5-30x productivity gains - Explore
CREW-AI-OVERVIEW.mdfor multi-agent workflows - Create custom rule modules in
.cursor/rules/modules/ - Add new stack profiles under
/profiles/
- Every 5-10 file changes: Update
project-history.md - Weekly: Review and update
CLAUDE.md - Before deployment: Run audits from
/03-guides/maintenance/audits/ - Monthly: Update dependencies and review phase progress
Contributions welcome! Priority areas:
- Additional stack profiles (Python, Vue, Angular)
- More theme examples beyond TAN
- Template improvements (keep under 500 lines)
- Documentation fixes and clarifications
Follow 01-templates/project-docs/PROJECT-RULES-TEMPLATE.md when contributing.
PRs should maintain the manual-first, documentation-driven approach.
MIT License - See LICENSE file for details
- Manual control - Copy-paste prompts give you flexibility over automation
- Documentation-first - Clear specs before code reduces rework
- AI-optimized structure - 500-line limit and functional patterns improve AI comprehension
- Context persistence - CLAUDE.md and project-history.md maintain understanding across sessions
- Phased development - Manageable progression from setup to production
Last Updated: December 2024