Complete guide for setting up a new web project using this AI-friendly documentation boilerplate
This boilerplate gives you a complete AI-friendly documentation structure for modern web projects with:
- π AI-Optimized Architecture - Single source of truth with machine-readable data
- π€ Advanced AI Integration - MCP integration with context injection patterns
- π Structured Documentation - Clear hierarchy with progressive disclosure
- π§ Modern Tech Stack - Next.js, TypeScript, modern tooling
- π Machine-Readable Status - YAML-based progress tracking
# Copy the boilerplate to your new project
cp -r boilerplate/web-project/* your-new-project/
# Or if you're starting fresh
mkdir your-new-project
cp -r boilerplate/web-project/* your-new-project/
cd your-new-project# Replace all instances of [Project Name] with your actual project name
find . -type f -name "*.md" -exec sed -i 's/\[Project Name\]/Your Project Name/g' {} \;Edit the following files to match your technology choices:
README.md- Update tech stack section.ai/context.yaml- Update project metadatadocs/architecture/overview.md- Update architecture detailsstandards/coding.md- Update tech stack references
git init
git add .
git commit -m "Initial commit: AI-friendly documentation structure"- Replace
[Project Name]with your project name - Update tech stack details
- Set current development phase
- Define completion percentage and priorities
- Update project overview and purpose
- Customize current status and priorities
- Update tech stack and architecture details
- Modify documentation structure if needed
- Update project name and current phase
- Customize completed tasks based on your status
- Update current priorities and roadmap
- Modify success metrics for your project
- **Backend**: [Your Choice] (Supabase, AWS, Firebase, etc.)
- **Database**: [Your Choice] (PostgreSQL, MongoDB, etc.)
- **API**: [Your Choice] (GraphQL, REST, tRPC, etc.)- **Authentication**: [Your Choice] (Supabase Auth, NextAuth, Auth0, etc.)
- **Security**: [Your Features] (JWT, RLS, CORS, etc.)- **Hosting**: [Your Choice] (Vercel, Netlify, AWS, etc.)
- **CI/CD**: [Your Choice] (GitHub Actions, GitLab CI, etc.)- Define your business domain model
- Specify core entities and relationships
- Document business rules and requirements
- Create feature roadmap
- Customize architectural patterns for your project
- Update component patterns and state management
- Modify error handling and performance patterns
Update .ai/mcp-config.json with your project structure:
{
"mcpServers": {
"your-project-docs": {
"command": "npx",
"args": ["@modelcontextprotocol/server-filesystem", "./docs"]
},
"your-project-standards": {
"command": "npx",
"args": ["@modelcontextprotocol/server-filesystem", "./standards"]
}
}
}The boilerplate provides a complete documentation structure following AI-friendly architecture:
your-new-project/
βββ README.md # Main project README (customize this)
βββ SETUP_GUIDE.md # This setup guide (delete after setup)
βββ .ai/ # AI-specific configuration
β βββ context.yaml # Master context file for AI agents
β βββ mcp-config.json # MCP server configuration
β βββ agent-instructions.md # AI behavior guidelines
βββ docs/ # Project documentation
β βββ index.md # Single entry point
β βββ status/ # Current state only
β β βββ progress.yaml # Machine-readable status
β β βββ priorities.md # Current priorities only
β βββ architecture/ # Technical implementation
β β βββ overview.md # System architecture
β β βββ database.md # Data model
β β βββ api.md # API specifications
β βββ guides/ # How-to documentation
β βββ setup.md # Environment setup
β βββ deployment.md # Deployment processes
βββ standards/ # Immutable standards
β βββ coding.md # Code conventions
β βββ patterns.md # Architectural patterns
β βββ business-rules.md # Domain logic
βββ [other files] # Additional documentation
- Project Name: Replace
[Project Name]throughout - Tech Stack: Update with your technology choices
- Business Logic: Define your domain model
- Current Status: Update progress.yaml
- MCP Configuration: Customize server names
- Architecture: Update with your system design
- Deployment: Customize deployment strategy
- Testing: Update testing approach
- Security: Define security requirements
- Performance: Set performance targets
- Design System: Customize UI/UX guidelines
- Internationalization: Add language support details
- Monitoring: Define observability strategy
- Compliance: Add regulatory requirements
# Install dependencies
yarn install
# Set up environment variables
cp env.example .env
# Initialize database (if applicable)
yarn db:setup
# Start development server
yarn dev# Install MCP package
yarn add -D @modelcontextprotocol/server-filesystem
# Create MCP configuration
mkdir -p .cursor
# Copy the MCP configuration from .ai/mcp-config.json
# Test MCP integration
# Restart Cursor AI and test with prompts- Update Status: Modify
docs/status/progress.yamlwith your current status - Set Priorities: Define your development priorities and roadmap
- Create Components: Start building your application following the established patterns
- Document Progress: Keep documentation updated as you progress
- Package not found: Ensure
@modelcontextprotocol/server-filesystemis installed - Configuration errors: Check JSON syntax in
.ai/mcp-config.json - AI not recognizing: Restart Cursor AI completely after configuration
- Inconsistent status: Update
docs/status/progress.yamlfirst - Broken references: Use single reference pattern from architecture
- Redundant information: Follow single source of truth principle
- Tech stack mismatch: Update all relevant files consistently
- Business logic confusion: Start with
standards/business-rules.md - Pattern inconsistency: Follow
standards/patterns.mdstandards
- API Documentation: Use
docs/architecture/api.mdas template - Database Setup: Customize
docs/architecture/database.mdfor your database - Deployment Guide: Update
docs/guides/deployment.mdfor your platform
- Coding Standards: Follow
standards/coding.mdfor consistency - Architectural Patterns: Use
standards/patterns.mdfor design patterns - Business Rules: Follow
standards/business-rules.mdfor domain logic
- MCP Documentation: https://modelcontextprotocol.io
- Next.js Documentation: https://nextjs.org/docs
- Your Backend Docs: [Your Backend Documentation URL]
Your project now has:
- β AI-friendly documentation structure with single source of truth
- β Advanced MCP integration for AI development assistance
- β Machine-readable status for efficient AI consumption
- β Clear document hierarchy with progressive disclosure
- β Eliminated redundancy and circular references
Next steps:
- Customize the templates for your specific project
- Set up MCP integration for AI assistance
- Begin development following established patterns
- Maintain documentation as you progress
Remember: This boilerplate follows AI-friendly architecture principles. Start with the basics and enhance gradually as your project grows.