Template-driven development workflow for LINE OA durian plant sales app with strict safety rules, GitHub issue management, knowledge system, and mode-based execution (Claude/Copilot).
A comprehensive development workflow system for the Praneet Panmai LINE App - a mobile-first durian plant sales application with tiered pricing calculator and LINE LIFF integration.
This skill implements a template-driven, safety-first development workflow with:
**You MUST NEVER:**
**You MUST ALWAYS:**
```bash
/mode manual # Set Claude implementation mode (default)
/mode copilot # Set GitHub Copilot implementation mode
/mode status # Show current execution mode
```
```bash
/fcs [topic-name] # Create new Context GitHub Issue
/fcs list # Show all active Context Issues
```
```bash
/plan [task description] # Create Task GitHub Issue
/impl [issue-number] # Implementation workflow
/impl [issue-number] [msg] # Implementation with context
/pr [feedback] # Create Pull Request to staging
```
```bash
/khub # Read Knowledge Hub #102 (MANDATORY first)
/kupdate [category] "[topic]" # Create Knowledge GitHub Issue
/klink [knowledge-issue-number] # Link knowledge entry to hub
/ksync # Synchronize Knowledge Hub
/ksearch "[query]" # Search knowledge entries
/krecent # Show last 5 knowledge updates
/kcategory [category] # Show category knowledge
```
```bash
/rrr [message] # Create daily retrospective GitHub Issue
```
**Create Context Issue:**
```bash
/fcs authentication-system
```
**This will:**
**Continue discussion in issue until context is complete.**
**When context reaches `[Ready for Planning]`:**
```bash
/plan Add LINE LIFF login integration with member verification
```
**This will:**
**Before starting implementation, verify:**
1. **Staging Sync:**
```bash
git checkout staging && git pull origin staging
```
2. **Task Verification:**
- Confirm Task GitHub Issue `#[issue-number]` exists
- Verify it has `[TASK]` label
3. **Context Status:**
- Verify Context GitHub Issue is `[Ready for Planning]` or `[Implementation Ready]`
4. **Environment Check:**
```bash
git status # Working directory must be clean
```
**Start implementation:**
```bash
/impl 123
```
**This will execute:**
1. **Create Feature Branch:**
```bash
git checkout -b feature/task-123-line-liff-login
```
2. **Execute Implementation:**
- Follow task requirements from GitHub Issue #123
- Use TodoWrite for complex multi-step tasks
- Implement all required functionality
3. **Build Validation (MANDATORY):**
```bash
npm run build # Must be 100% success (zero errors)
```
4. **Lint Validation (MANDATORY):**
```bash
npm run lint # Must be 100% pass (zero warnings)
```
5. **Format Check (MANDATORY):**
- Prettier auto-formatting runs
- Ensures consistent code formatting
6. **Type Check (MANDATORY):**
```bash
npm run type-check # Comprehensive TypeScript validation
```
7. **Run Tests (if applicable):**
```bash
npm test
```
8. **Commit Changes:**
```bash
git add .
git commit -m "feat: Add LINE LIFF login integration
- Address #123: LINE LIFF login with member verification
- Build validation: 100% PASS (npm run build)
- Lint validation: 100% PASS (npm run lint)
- Format validation: 100% PASS (prettier)
🤖 Generated with Claude Code
Co-Authored-By: Claude <[email protected]>"
```
9. **Push Branch:**
```bash
git push -u origin feature/task-123-line-liff-login
```
**Create PR to staging:**
```bash
/pr Implemented LINE LIFF login with member verification. All validations passed.
```
**This will:**
**After successful implementation:**
1. **Check Knowledge Hub first (MANDATORY):**
```bash
/khub # Read Knowledge Hub #102 to check existing entries
```
2. **Verify category numbers:**
- Check existing KNOW-[CATEGORY]-XXX numbers
- Identify next available number to avoid duplicates
3. **Create Knowledge Entry:**
```bash
/kupdate frontend "LINE LIFF SDK integration with TypeScript"
```
4. **Auto-prompt for hub linking:**
- System asks: "Link to Knowledge Hub #102? (y/n)"
- Respond "y" to automatically link entry
5. **Synchronize hub:**
```bash
/ksync # Ensure hub reflects all knowledge entries
```
`KNOW-[CATEGORY]-[NUMBER]`
Examples:
**MANDATORY Pre-Creation Checklist:**
1. **ALWAYS run `/khub` first** - Read Knowledge Hub #102 completely
2. **Check existing numbers** in your category section
3. **Identify next available number** (if 001, 002 exist, use 003)
4. **Never assume** - always verify before creating
**Example (Correct Workflow):**
```bash
/khub # See: KNOW-DEVICE-001, KNOW-DEVICE-002 exist
/kupdate device "SHT30 sensor fix" # Creates KNOW-DEVICE-003 ✅
```
```bash
/ksearch "LIFF SDK" # Full-text search
/kcategory frontend # Show all frontend knowledge
/krecent # Last 5 entries
/khub # Go to Knowledge Hub #102
```
**Location:** `/docs/ISSUE-TEMP.md`
Contains:
**Location:** `/docs/TASK-ISSUE-TEMP.md`
Contains:
**Location:** `/docs/KNOWLEDGE-TEMP.md`
Contains:
**Switch modes:**
```bash
/mode manual # Claude implementation
/mode copilot # GitHub Copilot implementation
/mode status # Show current mode
```
**All implementations MUST pass 100%:**
1. **Build:** `npm run build` - Zero errors
2. **Lint:** `npm run lint` - Zero warnings
3. **Format:** Prettier - Consistent formatting
4. **Type Check:** `npm run type-check` - No TypeScript errors
5. **Tests:** `npm test` - All tests passing (if applicable)
**NEVER commit code that fails any validation step.**
```
feature/* → staging → main
│ │
Railway Railway
(staging) (production)
```
**Repository:** https://github.com/mojisejr/praneet-panmai-line-app
**Tech Stack:**
**Application:** Mobile-first LINE OA integrated web app for durian plant sales with tiered pricing calculator, member authentication, and role-based access control.
1. **GitHub Issues Only:** All context, tasks, and knowledge are GitHub Issues - NEVER create local .md files
2. **Knowledge Hub #102:** Central knowledge discovery point - always check before creating knowledge entries
3. **No PR Merging:** Provide PR link and wait for user instructions - never merge yourself
4. **100% Validation:** All validation steps must pass completely before commit
5. **Feature Branches Only:** Never work directly on main or staging branches
6. **Template-Driven:** Always use proper templates via commands
**Common mistakes to avoid:**
**Always follow the complete workflow from context → task → implementation → PR → knowledge capture.**
Leave a review
No reviews yet. Be the first to review this skill!
# Download SKILL.md from killerskills.ai/api/skills/praneet-panmai-line-app-development-workflow/raw