Use when anyone asks about KoNote hosting costs, deployment options, per-agency pricing, budget scenarios, cost assumptions, managed service model, Azure vs OVHcloud comparison, onboarding costs, or needs to update cost figures. Also use when a new developer or manager needs deployment context.
Use when proposing new features, reviewing code changes, evaluating integration requests, or onboarding to KoNote — checks proposals against Design Rationale Records (DRRs) to identify conflicts with established architectural decisions, rejected anti-patterns, and privacy/security constraints before implementation begins.
Check web pages and code for WCAG 2.2 AA accessibility compliance. Use when the user mentions accessibility, WCAG, a11y, screen readers, colour contrast, keyboard navigation, alt text, or asks to check if something is accessible or usable by people with disabilities.
Generate a beginner-friendly overview of a codebase or project. Use when the user asks to understand a project, wants an overview, is new to a codebase, asks what a project does, or wants to know how code is organised.
Convenes expert panels for problem-solving. Use when user mentions panel, experts, multiple perspectives, MECE, DMAIC, RAPID, Six Sigma, root cause analysis, strategic decisions, or process improvement.
Use when making aesthetic decisions for web interfaces - choosing design direction, color palettes, typography, spacing systems, visual hierarchy, or UI polish. Use when user asks to make something look nicer, improve UX, choose a style, or needs guidance on crafted interface design. NOT for writing implementation code (use frontend-design for that).
Provide clear, personalised explanations of code, concepts, or architecture. Use when the user asks to explain something, wants to understand how code works, asks why something is done a certain way, or says they don't understand something.
Conduct in-depth requirements interviews to define features or applications. Use when the user wants to explore, define, or refine requirements for a project, feature, or app. Triggers on requests to interview about a plan, document requirements, define specifications, explore feature scope, clarify project needs, or when the user says they have an idea they want to flesh out. Also use when given a plan or document to review and the user wants thorough questioning about implementation details.