DuyAI avatar

DuyAI

Community

@xegheplimo-web

0Followers
|
6Public Repos
|
7Published Skills

DuyAI provides MIT-licensed skills for repository auditing, governed project bootstrapping, Open Design orchestration, and disciplined engineering practices like TDD and systematic debugging.

Skills Distribution
DomainDeveloper To...Code Review & Repo.. (30%)Testing & Debuggin.. (30%)Project Governance.. (25%)Design Orchestrati.. (15%)

Agent Skills by DuyAI

Showing 7 vetted skills indexed across 1 GitHub repositories.

Frequently Asked Questions About DuyAI

FAQPage Schema
What tasks can I accomplish using DuyAI's skills?

You can audit repositories and plan execution from critique, bootstrap governed projects with agent permissions, orchestrate the full Open Design loop from request to merge, enforce test-driven development, perform root-cause debugging, handle code review feedback rigorously, and verify work before claiming completion.

Who are DuyAI's skills designed for?

They target software engineers and project owners who need disciplined development practices: repository reviewers, maintainers enforcing governance and agent permissions, and developers practicing TDD, systematic debugging, and verification-before-completion on Linux, macOS, or Windows.

What is required to run DuyAI's orchestration skills?

The project-review-orchestrator, project-agent-bootstrapper, and open-design-orchestrator skills require terminal access as their toolset. They run cross-platform on Linux, macOS, and Windows, and interrelate—for example, the orchestrator pairs with the bootstrapper for governed project setup.

Are DuyAI's skills free and open source?

Yes. All published skills carry the MIT license, permitting free use, modification, and redistribution. They are authored by the Project Owner and Hermes Agent, with current versions at 0.1.0 across the orchestration and bootstrapping skills.

How do the discipline skills like TDD and systematic debugging work?

They are trigger-based practices: test-driven-development requires a verified failing test and RED-GREEN-REFACTOR before implementation; systematic-debugging mandates root-cause investigation before any fix; verification-before-completion requires running verification commands and confirming output before claiming success.