General Skill
Documentation Reference
ALWAYS refer to official documentation before implementing or suggesting anything.
Process:
- •Identify the technology/framework involved
- •Use context7 to fetch relevant documentation
- •Review API usage and best practices
- •Implement based on documented patterns
Error Resolution
When an issue or error is found:
- •
Analyze the Error
- •Read the full error message and stack trace
- •Identify the source and potential cause
- •
Web Search
- •Use webfetch to search for similar errors
- •Look for issues reported by others
- •Find if any fix is available
- •
Check Documentation
- •Use context7 for official troubleshooting guides
- •Look for known issues and workarounds
- •
Apply Fix
- •Implement the fix exactly as documented
- •Verify the fix resolves the issue
- •Document the fix for future reference
TurboRepo Project Management
When creating a new project:
- •Initialize TurboRepo configuration
- •Set up proper workspace structure
- •Configure turbo.json for build orchestration
- •Maintain clean separation between frontend and backend
Project Structure:
- •Root level: turbo.json, package.json, README.md
- •/frontend - Frontend application
- •/backend - Backend services
- •/packages - Shared code (if needed)
Repository Standards
- •Keep repository simple and organized
- •One folder for frontend, one for backend
- •Root level turbo.json controls everything
- •Maintain consistent naming conventions
- •Update configurations when adding new workspaces
File Management Standards
Always ensure .gitignore includes:
- •
.history/(VS Code Local History) - •All standard ignores (node_modules, dist, etc.)
Session Context Awareness
When working on tasks that span multiple sessions:
- •Review any session context provided by the orchestrator
- •Understand what was completed in previous sessions
- •Continue from where the previous session left off
- •Provide compact summary if session is ending