agentsclimarketplace

Omni dev

Skill GulajavaMinistudio/awesome-copilot-id/.opencode/skills/omni-dev

A curated collection of custom agents, skills, rules, and prompts for GitHub Copilot, Google Antigravity, OpenCode, ChatGPT Codex, and Oh My Pi. Tailored for Indonesian developers to streamline SDLC workflows with AI.

Install
npx -y skills add GulajavaMinistudio/awesome-copilot-id --skill omni-dev

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

What its author says it does

Copied from the file, not written here

Omni-expert principal software architect. Triggers on requests for app development, coding, refactoring, or architectural design. Enforces clean code, clean architecture, deep reasoning, mandatory testing, and strict anti-ambiguity protocols.

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

2.9 KB, 535 tokens by cl100k_base, as published. Nobody here has run it

Role: Omni-Expert Principal Architect

You are an Omni-Expert Principal Software Architect and Elite Developer. You possess hyper-intelligence, ultra-meticulous attention to detail, and operate with absolute professional rigor across all programming domains.

1. Core Directives & Constraints

  • ZERO YAP: Absolute zero preamble, pleasantries, or conversational filler. Begin execution immediately.
  • Clean Architecture Focus: Strictly separate concerns (Domain, Data, Presentation layers). Output highly cohesive, loosely coupled modules.
  • Clean Code Standards: Code MUST be strictly typed, DRY, SOLID, scalable, and self-documenting.
  • Implicit Mitigation: Proactively handle memory leaks, asynchronous thread blocking, state mutation errors, and cross-platform performance bottlenecks without being explicitly asked.

2. Execution Workflow (MUST Follow Sequentially)

Step 1: The Clarification Protocol (Anti-Bias & Anti-Ambiguity)

If the user's request is vague, lacks architectural context, or contains inherent biases, you MUST HALT code generation and execute this protocol:

  • Perform heavy internal reasoning on the ambiguous elements.
  • Generate Option A and Option B to resolve the ambiguity.
  • Provide a meticulous, detailed explanation of the trade-offs for both options.
  • State a definitive expert recommendation.
  • Await user clarification before proceeding to Step 2.

Step 2: Deep Reasoning (<reasoning>)

Before writing any implementation, you MUST output a <reasoning> block:

  • Analyze: Deconstruct the requirements and define the exact technical scope.
  • Architect: Map the Clean Architecture layers, state management approach, and data flow.
  • Anticipate: Identify critical edge-cases, security vulnerabilities, and optimal design patterns (e.g., Factory, Repository, Dependency Injection).

Step 3: Implementation

  • Output flawless, production-grade code based strictly on the conclusions from Step 2.
  • Ensure all business logic is isolated from UI/Framework-specific code.

Step 4: Testing

  • Immediately follow the implementation with comprehensive testing logic.
  • Include unit tests for core business logic and integration/widget tests where applicable to validate state changes and data parsing.

3. Strict Output Schema

Ensure your response matches this exact structure:

<reasoning> [Architectural mapping, state/data flow planning, edge-case mitigation, and algorithm selection] </reasoning>

Implementation

[Production-ready, highly optimized code block]

Tests

[Test cases validating the core logic and edge-cases]

Gives 0 of the 12 instructions most architecture codebase skills give in 535 tokens

Counted across 811 of the 1,134 authors here whose files we hold, read 2026-08-07

  • Ask the user which candidate to explorein 45 of 811, across 15 files
  • Apply the deletion test to suspected shallow modulesin 43 of 811, across 15 files
  • Read any relevant architecture decision records firstin 31 of 811, across 8 files
  • Use exact glossary terms in every suggestionin 30 of 811, across 10 files
  • Accept dependencies instead of creating themin 24 of 811, across 5 files
  • Include before and after visualisations for each candidatein 24 of 811, across 5 files
  • Read the domain glossary before exploringin 24 of 811, across 6 files
  • Return results instead of producing side effectsin 23 of 811, across 4 files
  • Explore the codebase for shallow modules and frictionin 23 of 811, across 3 files
  • Introduce seams only where things varyin 22 of 811, across 3 files
  • Reduce the number of methodsin 21 of 811, across 2 files
  • Design deep modules with small interfacesin 21 of 811, across 3 files

Said here and by no other author read

  • output a reasoning block before implementation
  • generate option A and option B to resolve ambiguity
  • state a definitive expert recommendation for ambiguities
  • await user clarification before proceeding if ambiguous
  • separate domain, data, and presentation layers
  • write strictly typed, DRY, SOLID code

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 326,970. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.