tutorial-notes

Use this skill when the user wants to design system architecture, choose a technology stack, define coding conventions, create architecture diagrams, or map out system workflows and data flows. Trigger whenever the user says things like "design the architecture for", "what tech stack should I use", "how should I structure this system", "draw a diagram for", "design a microservice", "how should modules communicate", "what pattern should I use for", "design the database schema", "design an API", or asks how to architect any software system end-to-end. Also trigger when the user shares a PRD or project plan and wants the technical design, or asks to review/critique an existing architecture. This skill covers system design, component breakdown, tech stack selection, coding conventions, and Mermaid/PlantUML diagrams.

Use this skill when the user wants to brainstorm product ideas, evaluate or critique an existing product concept, improve or sharpen a product idea, or rewrite product requirements (PRD, user stories, feature specs) to be clearer and more actionable. Trigger whenever the user says things like "I have an idea for a product", "what do you think of this idea", "help me improve my product concept", "write a PRD", "rewrite my requirements", "give me product ideas for X", or asks for feedback on any product-related document. Also trigger for startup ideas, SaaS concepts, feature proposals, or any discussion that involves defining what a product should do and for whom.

Use this skill when the user wants to plan a project or product delivery, break down work into structured items, or create a work breakdown structure (WBS). Trigger whenever the user says things like "plan this project", "break this down into tasks", "create a backlog for", "list the work items for", "what do we need to build X", "create epics and tasks for", "help me plan a sprint", "write a project plan", or asks how to deliver a feature, product, or system end-to-end. Also trigger when a user shares a PRD, architecture doc, or product idea and wants to know what needs to be done to ship it. This skill produces a full hierarchy: Features → Epics → Tasks → Sub-tasks, with estimates, priorities, and dependencies.