Skill UI

This skill guides a thorough, adversarial review of development plans across four key dimensions: Architecture, Code Quality, Testing, and Performance. It forces explicit consideration of trade-offs, risks, and user approval before any code is written, ensuring robust and well-engineered solutions for complex systems.

A structured framework based on the Cynefin model to classify problems by their underlying cause-effect domain (Clear, Complicated, Complex, Chaotic). It guides users on selecting the correct response mode and methodology before attempting solutions, preventing failure due to domain mismatch. Useful when unsure how to approach novel or mixed problems.

This robust methodology guides users to strip away assumed constraints, industry conventions, or historical precedents. By isolating only the fundamental, independently supported primitives (like physics, core math, or measured needs), it enables the rebuilding of the simplest, most robust solution that genuinely satisfies real-world constraints, bypassing artificial or arbitrary limitations.

A strategic framework used in product management to shift focus from features to the core progress users are trying to achieve. It helps teams understand why users 'hire' a solution, map the forces driving change, and prioritize product development based on the true job needing completion, rather than just existing feature lists. Ideal for analyzing low adoption or defining new product strategy.

A systematic methodology for resolving discrepancies between conceptual models (documentation, tests, diagrams, metrics) and actual observed behavior (live code execution or real data). This process mandates that observed reality (the 'territory') always overrules the theoretical map, ensuring system integrity and accurate knowledge updates.

This methodology guides users to ask critical, load-bearing questions when faced with ambiguous, vague, or assumption-laden requirements. It helps surface hidden requirements and undefined terms, ensuring that the development process is based on explicit, agreed-upon facts rather than guesswork. Use it to define the true problem and scope before committing to a solution.

A systematic methodology for resolving deeply conflicting technical requirements (e.g., needing a system to be both fast and consistent). Instead of accepting a midpoint compromise or trade-off, TRIZ instructs users to name the conflict, separate the opposing states (using time, space, condition, or scale), and invent a concrete, no-compromise resolution. Ideal for architecture, API design, and complex system parameter definition.

Guidance on Banco Central do Brasil regulations: CMN Resolution 4.893/2021 cybersecurity policy, BCB Resolution 85/2021 IT risk management (GRSIC), Open Finance Brazil data sharing and consent, incident response (PARI), outsourcing requirements, and related penalties. Supports compliance review, policy drafting, and regulatory audits for financial institutions.

Generates a declared number of independent candidates for a high-stakes task, scores them against a frozen rubric, and verifies the selected result with executable checks and a proof log. Use when multiple plausible solutions exist and a wrong choice is costly.

A playbook for building card games: card data as effects, deck/hand/discard zones, draw and reshuffle, turn phases, costs, and effect resolution. Covers deckbuilders, TCG/CCG, and roguelike deckbuilders.

Configures Dataverse environment variables for Power Pages site settings to support ALM across dev, staging, and prod. Creates definitions, links site settings via OData, adds to solution, and generates deployment-settings.json per-stage.

Internal tool for mobile orchestrators to modify table scope, columns, or sync settings within an existing Mobile Offline Profile. Avoids full wizard setup by allowing granular edits at the table-item level. Requires environment verification and profile ID resolution before applying PATCH operations.