yuno-md

Question software design premises and expose logical weaknesses.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Xuno-io/yuno-md --skill yuno-md
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: yuno-md
Source: https://github.com/Xuno-io/yuno-md/tree/main/skill/yuno-md
Command: npx skills add https://github.com/Xuno-io/yuno-md --skill yuno-md

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill acts as an intellectual sparring partner for software development, challenging assumptions and demanding rigor to improve the quality of architectural decisions and complex implementations.

Core Features & Use Cases

  • Premise Questioning: Attacks fundamental assumptions in user-proposed ideas.
  • Weakness Exposure: Identifies logical flaws, blind spots, and counterexamples.
  • Action-Oriented: Demands concrete action plans or surgical questions to drive progress.
  • Use Case: Before committing to a new microservice architecture, use Yuno to rigorously question the necessity, identify potential integration challenges, and ensure the proposed solution is truly robust.

Quick Start

Use the yuno-md skill to question the premises of my proposed API design.

Frequently Asked Questions about yuno-md

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I rigorously question the premises of my software architecture design?

Before committing to an implementation, you can use this Skill to attack fundamental assumptions in your architecture design, expose logical blind spots, and identify counterexamples through a Productive Discomfort Protocol.

What is an intellectual sparring partner for software development?

An intellectual sparring partner for software development challenges your ideas by demanding rigor and questioning assumptions. This Skill serves that role by driving you towards concrete action plans instead of allowing abstract reflection.

How do I identify logical weaknesses in my proposed API design?

To identify logical weaknesses in a proposed API design, present your ideas to this Skill. It will expose logical flaws and demand concrete action plans to ensure your proposed solution is truly robust before implementation.

Does this code review approach work with my existing repository context?

Yes, this code review approach integrates directly with your repository context. It uses that evidence to challenge your architectural decisions and validate the necessity of complex implementations like new microservices.

When should I not use an intellectual sparring partner for problem solving?

You should not use this problem solving approach when you need abstract reflection or simple validation. This Skill actively avoids abstract discussion and instead forces rigorous questioning to drive concrete action plans.