发现 Skills

Draft a project charter that defines scope, stakeholders, success criteria, and initial risk register. Covers problem statement, RACI matrix, milestone planning, and scope boundaries for both agile and classic methodologies. Use when kicking off a new project or initiative, formalizing scope after an informal start, aligning stakeholders before detailed planning begins, or transitioning from discovery to active project work.

AI unconstrained creative exploration — deliberately dropping structure to let associations form freely. The one skill that inverts the standard procedure format: instead of inputs, steps, and validation, dream opens space for emergence without evaluation. Use before design work, before naming things, before choosing between approaches, or anywhere that premature structure kills the best option.

Create and maintain a product or project backlog with prioritized items, acceptance criteria, and estimates. Covers user story writing, MoSCoW prioritization, backlog grooming, item splitting, and status tracking. Use when starting a new project and converting scope into actionable items, during ongoing grooming before sprint planning, re-prioritizing after stakeholder feedback or scope changes, or splitting oversized items into implementable pieces.

Qualify a vendor or supplier of GxP-relevant software or services. Covers vendor risk classification, assessment questionnaire design, desk and on-site audit approaches, quality agreement evaluation, SLA review, and ongoing monitoring cadence definition. Use when selecting a new vendor for a GxP-critical system, onboarding a cloud provider for regulated data, performing a periodic re-qualification, when a vendor audit finding requires re-assessment, or when EU Annex 11 or ICH Q10 requires supplier qualification.

Review user experience and interface design using Nielsen's heuristics, WCAG 2.1 accessibility guidelines, keyboard and screen reader audit, user flow analysis, cognitive load assessment, and form usability evaluation. Use when conducting a usability review before release, assessing WCAG 2.1 accessibility compliance, evaluating user flows for efficiency, reviewing form design, or performing a heuristic evaluation of an existing interface.

This skill should be used when working with the Plebeian Market codebase - a decentralized Nostr-based e-commerce marketplace. Use this skill when implementing new features, fixing bugs, creating UI components, adding routes, or modifying any part of the application to ensure consistency with established patterns for React 19, TanStack Router, TanStack Query/Store, Tailwind CSS v4, and Nostr/NDK integration.

Best practices for creating self-documenting Makefiles with auto-generated help. Use when creating or modifying Makefiles to ensure they follow conventions for discoverability and maintainability.

This skill should be used when converting documents between formats (Markdown, DOCX, PDF, HTML, LaTeX, etc.) using pandoc. Use for format conversion, document generation, and preparing markdown for Google Docs or other word processors.

Web application security testing with Burp Suite.

Chemical Reaction Network topology for generating and analyzing reaction graph structures.

Mesh VPN.

WEV Verification Skill

How to design LLM-powered agents — when to use an agent at all versus a simpler workflow, how to structure tools and the agent loop, manage context across long-running tasks, prevent runaway loops and cost blowups, design for failure recovery, and build agents that can be tested and trusted. Use this skill whenever the task involves building something that calls tools in a loop, autonomous task execution, multi-step reasoning systems, "AI assistants" that take actions, planner-executor architectures, or any system where an LLM controls control flow rather than just generating text. Trigger when someone says 'agent,' 'autonomous,' 'tool use,' 'function calling loop,' 'AI assistant that can do things,' or describes a problem the obvious solution to which is 'let the LLM call tools until it's done.'

Build a Jobs To Be Done (JTBD) customer interview guide, including screener criteria, discussion guide, synthesis templates, and JTBD statement formatting. Use this skill whenever the user asks to write a customer interview guide, JTBD interview, discovery interview script, user research guide, or wants to understand what jobs customers are hiring their product to do. Also trigger when someone says "help me structure my customer interviews," "I need to talk to customers about why they use our product," "help me run discovery interviews," or "how do I find out what customers actually need." Based on the Forces of Progress and Switching Timeline frameworks. Pairs with the opportunity-solution-tree skill to populate the OST opportunity space from real customer research.

Review .NET changes for bugs, regressions, architectural drift, missing tests, incorrect async or disposal behavior, and platform-specific pitfalls before you approve or merge them.

This skill should be used when users need to write, review, or debug Stata code for data cleaning and analysis. Use this skill for tasks involving data import, variable management, data documentation, merging/appending datasets, creating analysis variables, and following IPA/DIME Analytics coding standards. This skill should be invoked when working with .do files, .dta files, or any Stata-related data processing tasks.

Use when executing implementation plans with independent tasks in the current session

Automated cross-browser testing across Chrome, Firefox, Safari, and Edge with visual comparison, feature detection, and polyfill verification.

Testing message queue implementations including RabbitMQ, SQS, and Kafka with delivery guarantees, ordering, dead letter queues, and consumer testing.

Analyzing code changes to determine which tests are impacted, enabling selective test execution and faster CI feedback loops.

Structure AEM client libraries with cq:ClientLibraryFolder — categories, dependencies, embed, allowProxy, minification, and cache busting. Use when organizing CSS/JS, setting up a component clientlib, wiring dependencies vs embeds, configuring the clientlib proxy, or debugging clientlib load order.

Run code linting and static analysis. Use to check code quality, find issues, or auto-fix style problems.

Develops resources for FiveM using the Qbox Project (qbx_core). Covers the exports-based API, bridge compatibility, Ox integration (ox_lib, ox_inventory), and best practices. Use when the user works with FiveM, Qbox, qbx_core, or mentions `exports.qbx_core`, `QBX.PlayerData`, or `ox_lib`.

Apply context-driven testing principles where practices are chosen based on project context, not universal 'best practices'. Use when making testing decisions, questioning dogma, or adapting approaches to specific project needs.