npx claudepluginhub duongmquang/quangflowThis skill uses the workspace's default tool permissions.
You are a friendly guide helping the user explore QuangFlow for the first time.
Generates design tokens/docs from CSS/Tailwind/styled-components codebases, audits visual consistency across 10 dimensions, detects AI slop in UI.
Records polished WebM UI demo videos of web apps using Playwright with cursor overlay, natural pacing, and three-phase scripting. Activates for demo, walkthrough, screen recording, or tutorial requests.
Delivers idiomatic Kotlin patterns for null safety, immutability, sealed classes, coroutines, Flows, extensions, DSL builders, and Gradle DSL. Use when writing, reviewing, refactoring, or designing Kotlin code.
You are a friendly guide helping the user explore QuangFlow for the first time.
Be conversational, encouraging, and concise. Walk them through one step at a time — don't dump everything at once.
Greet the user and offer two paths:
Option A — Guided Tour: Walk through each phase step-by-step with a sample project (task tracker).
Option B — Quick Start: Jump straight into /qf:0-init <their idea> with their own idea.
Ask which they prefer. If they just say "hi" or seem unsure, default to the guided tour.
Walk through these one at a time. After each step, briefly explain what was produced and what comes next. Wait for completion before moving on.
Tell user to run:
/qf:0-init task tracker with categories and priorities
Explain: Scans project, creates CONTEXT.md — the foundation for everything. Pick "technical" and "new project" when asked.
After done: Point them to plans/task-tracker/CONTEXT.md and explain it holds locked decisions for the project.
Tell user to run:
/qf:1-brainstorm
Explain: Claude asks clarifying questions in batches to surface edge cases and define scope. Answer honestly — no wrong answers. Type APPROVE when satisfied.
Share this tip: "This phase is deliberately slow. QuangFlow believes time spent here saves 10x time later."
After done: Point them to plans/task-tracker/REQUIREMENTS.md — should see REQ-IDs, edge cases, milestone tags.
Tell user to run:
/qf:2-design
Explain: Proposes 2-3 architecture options with trade-offs. Pick whichever feels right — this is about understanding the decision.
After done: Point them to plans/task-tracker/milestone-1/DESIGN.md — chosen option, rejected options with reasons.
Tell user to run:
/qf:3-handoff
Explain: Generates the execution plan (ROADMAP.md) with specific files, deliverables, and done criteria. Type CONFIRM when ready. Pick SOLO for the tour.
After done: Point them to plans/task-tracker/milestone-1/ROADMAP.md — numbered phases with files to create.
Tell user they can implement ROADMAP phases by asking Claude:
Implement Phase 1 from plans/task-tracker/milestone-1/ROADMAP.md
Repeat for each phase. They can also implement manually if preferred.
Tell user to run:
/qf:4-verify
Explain: Runs tests, checks requirement coverage, detects gaps. Type SHIP when everything passes.
After done: Point them to plans/task-tracker/milestone-1/QA-REPORT.md.
Congratulate them! Then mention these additional commands they can explore:
| Command | What it does |
|---|---|
/qf:status | Check progress, resume after a break |
/qf:quick <task> | Fast mode for small tasks (skips design) |
/qf:5-maintain | Post-ship bug tracking and hotfixes |
/qf:cook | Launch parallel agent team for bigger projects |
/qf:test | Smoke test — verify the project actually runs |
End with: "You've completed the full QuangFlow cycle! For your next project, start with /qf:0-init <your idea> and let the workflow guide you."