--- name: starter classification: capability classification-reason: Pattern guidance may overlap with model's built-in knowledge as it improves deprecation-risk: medium effort: medium description: | Static web development for beginners — HTML/CSS/JS and Next.js App Router. Triggers: static website, portfolio, landing page, beginner argument-hint: "[init|guide|help]" agent: bkit:starter-guide allowed-tools: - Read - Write - Edit - Glob - Grep - WebSearch - WebFetch user-invocable: true imports: - ${PLUGIN_ROOT}/templates/design-starter.template.md next-skill: phase-1-schema pdca-phase: plan task-template: "[Init-Starter] {feature}" --- # Beginner (Starter) Skill ## Actions | Action | Description | Example | |--------|-------------|---------| | `init` | Project initialization (/init-starter feature) | `/starter init my-portfolio` | | `guide` | Display development guide | `/starter guide` | | `help` | Beginner help | `/starter help` | ### init (Project Initialization) 1. Create project directory structure (HTML/CSS/JS or Next.js) 2. Generate package.json (when Next.js selected) 3. Create CLAUDE.md (Level: Starter specified) 4. Create docs/ folder structure (for PDCA documents) 5. Initialize the pipeline store — `writeBkitMemory()` in `lib/pdca/status.js`, which writes `.bkit/state/memory.json` (the migrated path of `.bkit-memory.json`). This holds the project level and the 9-phase `pipelineStatus`, read by the pipeline Stop hooks for phases 5, 6 and 9. It is NOT where the PDCA phase lives — that is `.bkit/state/pdca-status.json`. ### guide (Development Guide) - Analyze current project state - Suggest next steps appropriate for Starter level - Phase 1-3 focused Pipeline guide ### help (Beginner Help) - Explain HTML/CSS/JS basic concepts - Answer frequently asked questions - Provide example code ## Target Audience - Those learning programming for the first time - Those who want to create a simple website - Those who need a portfolio site ## Tech Stack ### Option A: Pure HTML/CSS/JS (For Complete Beginners) ``` HTML5 → Web page structure CSS3 → Styling JavaScript → Dynamic features (optional) ``` ### Option B: Next.js (Using Framework) ``` Next.js 14+ → React-based framework Tailwind CSS → Utility CSS TypeScript → Type safety (optional) ``` ### Language Tier Guidance (v1.3.0) > **Recommended**: Tier 1 languages only (Python, TypeScript, JavaScript) > > Starter level focuses on AI-Native development with maximum AI tool support. | Tier | Allowed | Reason | |------|---------|--------| | Tier 1 | ✅ Yes | Full AI support, Vibe Coding optimized | | Tier 2 | ⚠️ Limited | Consider Dynamic level instead | | Tier 3-4 | ❌ No | Upgrade to Dynamic/Enterprise | ## Project Structure ### Option A: HTML/CSS/JS ``` project/ ├── index.html # Main page ├── about.html # About page ├── css/ │ └── style.css # Styles ├── js/ │ └── main.js # JavaScript ├── images/ # Image files ├── docs/ # PDCA documents │ ├── 01-plan/ │ └── 02-design/ └── README.md ``` ### Option B: Next.js ``` project/ ├── src/ │ ├── app/ │ │ ├── layout.tsx # Common layout │ │ ├── page.tsx # Main page │ │ └── about/ │ │ └── page.tsx # About page │ └── components/ # Reusable components ├── public/ # Static files ├── docs/ # PDCA documents ├── package.json ├── tailwind.config.js └── README.md ``` ## Core Concept Explanations ### HTML (Web Page Structure) ```html
I am ...