core-development
Master core development paths - Frontend, Backend, Full Stack, DevOps. Atomic skill for learning sequences and technology stack recommendations.
What this skill does
# Core Development Skill ## Quick Reference | Path | Duration | Entry Point | Exit Point | |------|----------|-------------|------------| | **Frontend** | 3-6 mo | HTML/CSS | React/Vue + Testing | | **Backend** | 6-12 mo | Language | API + DB + Deploy | | **Full Stack** | 9-15 mo | Frontend | Full app + DevOps | | **DevOps** | 12-24 mo | Linux | K8s + IaC + CI/CD | --- ## Learning Paths ### Frontend ``` [1] HTML5 + CSS3 (2-3 wk) │ ▼ [2] JavaScript ES6+ (4-6 wk) │ ▼ [3] React 19 / Vue 3 (4-6 wk) │ ▼ [4] State + Testing (2-4 wk) │ ▼ [5] Deploy + CI/CD (1-2 wk) ``` **2025 Stack:** TypeScript + React 19 + Tailwind v4 + Vite + Vitest --- ### Backend ``` [1] Python or JavaScript (4-6 wk) │ ▼ [2] Framework: FastAPI / NestJS (4-6 wk) │ ▼ [3] Database: PostgreSQL (3-4 wk) │ ▼ [4] APIs + Auth (3-4 wk) │ ▼ [5] Testing + Deploy (2-4 wk) ``` **2025 Stack:** Python + FastAPI + PostgreSQL + Redis + Docker --- ### Full Stack ``` [1] Frontend Mastery (3-4 mo) │ ▼ [2] Backend Mastery (4-6 mo) │ ▼ [3] Integration + DevOps (2-4 mo) ``` **2025 Stack:** Next.js 15 + PostgreSQL + Vercel --- ### DevOps ``` [1] Linux + Bash (4-6 wk) │ ▼ [2] Docker (2-3 wk) │ ▼ [3] Kubernetes (6-8 wk) │ ▼ [4] Cloud: AWS/GCP (8-12 wk) │ ▼ [5] Terraform + CI/CD (4-6 wk) ``` **2025 Stack:** Docker + Kubernetes + Terraform + GitHub Actions --- ## Technology Matrix | Component | Frontend | Backend | Full Stack | DevOps | |-----------|----------|---------|------------|--------| | **Language** | TypeScript | Python/JS | TypeScript | Bash/Python | | **Framework** | React 19 | FastAPI | Next.js 15 | - | | **Styling** | Tailwind | - | Tailwind | - | | **Database** | - | PostgreSQL | PostgreSQL | - | | **Testing** | Vitest | pytest | Playwright | - | | **Deploy** | Vercel | Docker | Vercel | K8s | --- ## Troubleshooting Decision Tree ``` Which path should I choose? ├─► Like visual/creative work? → Frontend ├─► Prefer logic/algorithms? → Backend ├─► Want to build complete products? → Full Stack └─► Love automation/infrastructure? → DevOps Stuck in tutorial hell? ├─► Stop watching, start building ├─► Pick ONE project and finish it ├─► 70% building, 30% learning └─► Deploy something live today Can't find a job? ├─► Portfolio too weak? → Build 3 real projects ├─► No GitHub activity? → Contribute to open source ├─► Resume weak? → Add measurable achievements └─► No network? → Join communities, attend meetups ``` --- ## Common Failure Modes | Symptom | Root Cause | Recovery Action | |---------|------------|-----------------| | Analysis paralysis | Too many options | Pick popular stack, start today | | Outdated learning | Using old resources | Check resource date (must be 2024+) | | Impostor syndrome | Comparing to experts | Focus on daily improvement | | Burnout | Too fast, too much | 1-2 hours/day consistently | --- ## Validation Checklist Before marking path complete: - [ ] Can build project from scratch without tutorial - [ ] Understand WHY, not just HOW - [ ] Have 3+ portfolio projects deployed - [ ] Can explain concepts to others - [ ] Passed technical interview questions --- ## Next Actions Run `/learn` for personalized guidance on your chosen path.
Related in Web Dev
generating-lwc-components
IncludedLightning Web Components with PICKLES methodology and 165-point scoring. Use this skill when the user creates or edits LWC components, builds wire service patterns, or writes Jest tests for LWC. TRIGGER when: user creates/edits LWC components, touches lwc/**/*.js, .html, .css, .js-meta.xml files, or asks about wire service, SLDS, or Jest LWC tests. DO NOT TRIGGER when: Apex classes (use generating-apex), Aura components, or Visualforce.
tanstack-query
IncludedManage server state in React with TanStack Query v5. Set up queries with useQuery, mutations with useMutation, configure QueryClient caching strategies, implement optimistic updates, and handle infinite scroll with useInfiniteQuery. Use when: setting up data fetching in React projects, migrating from v4 to v5, or fixing object syntax required errors, query callbacks removed issues, cacheTime renamed to gcTime, isPending vs isLoading confusion, keepPreviousData removed problems.
document-processor-api
IncludedProcess documents with Nutrient DWS. Use when the user wants to generate PDFs from HTML or URLs, convert Office/images/PDFs, assemble or split packets, OCR scans, extract text/tables/key-value pairs, redact PII, watermark, sign, fill forms, optimize PDFs, or produce compliance outputs like PDF/A or PDF/UA. Triggers include convert to PDF, merge these PDFs, OCR this scan, extract tables, redact PII, sign this PDF, make this PDF/A, or linearize for web delivery.
nutrient-document-processing
IncludedProcess documents with Nutrient DWS. Use when the user wants to generate PDFs from HTML or URLs, convert Office/images/PDFs, assemble or split packets, OCR scans, extract text/tables/key-value pairs, redact PII, watermark, sign, fill forms, optimize PDFs, or produce compliance outputs like PDF/A or PDF/UA. Triggers include convert to PDF, merge these PDFs, OCR this scan, extract tables, redact PII, sign this PDF, make this PDF/A, or linearize for web delivery.
tanstack-query
IncludedManage server state in React with TanStack Query v5. Covers useMutationState, simplified optimistic updates, throwOnError, network mode (offline/PWA), and infiniteQueryOptions. Use when setting up data fetching, fixing v4→v5 migration errors (object syntax, gcTime, isPending, keepPreviousData), or debugging SSR/hydration issues with streaming server components.
accelint-nextjs-best-practices
IncludedNext.js performance optimization and best practices. Use when writing Next.js code (App Router or Pages Router); implementing Server Components, Server Actions, or API routes; optimizing RSC serialization, data fetching, or server-side rendering; reviewing Next.js code for performance issues; fixing authentication in Server Actions; or implementing Suspense boundaries, parallel data fetching, or request deduplication.