agentleFS
roedyrustamroedyrustam/doku-gemini-mcp/skills/detect-stack/SKILL.md

detect-stack

Skill2 starsChanged 8 days agoMITView on GitHub

Detect project programming language, framework, package manager, and structure for DOKU Payment Gateway integration, then save configuration / Deteksi bahasa pemrograman, framework, dan konfigurasi proyek untuk integrasi DOKU.

  • Reads credentials

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

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

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

    line 80

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

Detect Stack / Deteksi Stack Proyek

English | Bahasa Indonesia


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

English

Description

Detects the active project's tech stack (language, runtime, framework, ORM, package manager) to prepare code generation and configuration for DOKU Payment Gateway integrations. Saves the detected environment settings to .doku-config.json.

Trigger Conditions

Activate this skill when the user says:

  • "detect stack"
  • "check project framework for DOKU"
  • "identify tech stack"

Step-by-Step Execution Protocol

  1. Scan Workspace Root Files:
    • package.json -> Node.js / TypeScript (Express, Fastify, Next.js, Hono, NestJS).
    • requirements.txt / pyproject.toml / Pipfile -> Python (FastAPI, Django, Flask).
    • go.mod -> Go (Gin, Echo, Fiber, Net/HTTP).
    • composer.json -> PHP (Laravel, Symfony).
    • pom.xml / build.gradle -> Java (Spring Boot).
  2. Extract Environment & Configuration Details:
    • Package manager (npm, pnpm, yarn, bun, pip, uv, go).
    • Active TypeScript / JS target version.
    • Presence of .env or .env.example.
  3. Generate Configuration File (.doku-config.json):
    {
      "stack": {
        "language": "typescript",
        "framework": "express",
        "packageManager": "pnpm",
        "hasEnv": true
      },
      "doku": {
        "isProduction": false,
        "apiVersion": "v2",
        "snapVersion": "v1.0"
      }
    }
  4. Report Findings: Summarize detected stack and confirm configuration saved.

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

Bahasa Indonesia

Deskripsi

Mendeteksi tech stack proyek (bahasa, runtime, framework, ORM, package manager) untuk menyiapkan pembuatan kode dan konfigurasi integrasi DOKU Payment Gateway. Hasil deteksi disimpan ke .doku-config.json.

Kondisi Pemicu

Aktifkan skill ini ketika pengguna mengatakan:

  • "detect stack"
  • "periksa framework proyek untuk DOKU"
  • "identifikasi tech stack"

🚨 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.