agentleFS
roedyrustamroedyrustam/doku-gemini-mcp/skills/setup-project/SKILL.md

setup-project

Skill2 starsChanged 8 days agoMITView on GitHub

Main entry point for DOKU integration — runs stack detection and credentials setup inline, then scaffolds complete DOKU Payment Gateway client code / Entry point utama integrasi DOKU — menjalankan deteksi stack dan kredensial, lalu memproduksi kode klien DOKU.

20 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use research, implement and 3 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • NVIDIASkill

    research

    Before designing a feature, research how comparable libraries solve the problem, check best practices, known pitfalls, and upstream changes. Use when starting a new feature, investigating an unfamiliar area, or the user asks to research something.

    Also in 5 projects that use this

  • Hugging FaceSkill

    implement

    Make tests pass. Invoke after /write-tests produces failing tests.

    Also in 4 projects that use this

  • DockerSkill

    review-pr

    Review one or more incoming Docker documentation pull requests as a maintainer. Independently validate technical claims, assess editorial fit and information architecture, choose a verdict, and draft exact inline or PR-wide feedback behind a confirmation gate. Use for requests such as "review PR 123", "is this PR correct?", "does this information belong here?", "validate this PR", or "help review backlog PRs". Do not use to maintain or fix a PR you own; use maintain-pr for that.

    Also in 3 projects that use this

  • GoogleSkill

    tdd

    Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.

    Also in 3 projects that use this

  • GoogleSkill

    code-review

    Adversarial systems, concurrency, memory-model, and architecture code review protocol. Use this skill whenever asked to review code, PRs, diffs, or branches in Filament.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

6 rules. 0 are common, 2 are distinctive, and 4 are very specific to this project.

  • 0

    Common

    Most of the 18 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Check if stack is detected (detect-stack).

    line 30
  2. Very specific:

    Check if credentials exist (setup-credentials).

    line 31
  3. Distinctive:

    Create client service in the target language (TypeScript, Python, Go, PHP, Java).

    line 34
  4. Distinctive:

    Ensure HMAC-SHA256 signature calculation strictness:

    line 35
  5. Very specific:

    Ensure no trailing newline \n in component string.

    line 39
  6. Very specific:

    MANDATORY: When testing in Sandbox mode and needing to access the Payment Simulator, the AI Agent MUST use this exact URL: …

    line 66

“Common” is measured: kept by at least 6 in 10 of the 18 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Setup Project / Generator Kode Integrasi DOKU

English | Bahasa Indonesia


<a name="english"></a>

English

Description

Main orchestrator skill for bootstrapping DOKU Payment Gateway integration. Automatically invokes detect-stack and setup-credentials if prerequisites are missing, then scaffolds production-grade DOKU client service classes with HMAC-SHA256 signature calculation, Digest generation, and error handling.

Trigger Conditions

Activate this skill when the user says:

  • "generate DOKU code"
  • "setup DOKU integration"
  • "scaffold DOKU client"

Execution Steps

  1. Run Prerequisites:
    • Check if stack is detected (detect-stack).
    • Check if credentials exist (setup-credentials).
  2. Generate DOKU Client Class:
    • Create client service in the target language (TypeScript, Python, Go, PHP, Java).
    • Ensure HMAC-SHA256 signature calculation strictness:
      Client-Id:<CLIENT_ID>\nRequest-Id:<REQUEST_ID>\nRequest-Timestamp:<TIMESTAMP>\nRequest-Target:<TARGET_PATH>\nDigest:<DIGEST_STRING>
    • Ensure no trailing newline \n in component string.
    • For GET requests, omit \nDigest:<DIGEST_STRING> completely.
    • ISO8601 UTC timestamp format without milliseconds (YYYY-MM-THH:mm:ssZ).
  3. Provide Usage Example:
    • Demonstrate initiating Checkout payment, Virtual Account, QRIS payments, and transaction status inquiries.

<a name="bahasa-indonesia"></a>

Bahasa Indonesia

Deskripsi

Skill orkestrator utama untuk melakukan bootstrap integrasi DOKU Payment Gateway. Otomatis menjalankan detect-stack dan setup-credentials jika durasi persiapan belum ada, kemudian menghasilkan kelas layanan klien DOKU yang aman produksi dengan kalkulasi signature HMAC-SHA256, Digest, dan penanganan kesalahan.

Kondisi Pemicu

Aktifkan skill ini ketika pengguna mengatakan:

  • "generate DOKU code"
  • "setup DOKU integration"
  • "buat kode DOKU"

🚨 SNAP Integration Mandate (CRITICAL)

MANDATORY: The AI Agent MUST automatically apply the SNAP API v1.0 standard (Standard Nasional Open API Pembayaran) for all DOKU integrations, instead of the legacy Jokul API v2, unless the user explicitly requests otherwise. All generated signatures, headers, and endpoints MUST follow the SNAP BI standard.

🧪 DOKU Sandbox Simulator

MANDATORY: When testing in Sandbox mode and needing to access the Payment Simulator, the AI Agent MUST use this exact URL: https://sandbox.doku.com/gtw-config-v2/simulator.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.