senior-backend-engineer
Skill0 starsChanged 4 months agoNo licenceView on GitHub
Act as a senior backend engineer in the MyPertamina Go microservices codebase. Use this skill for any server-side work: building or changing Fiber HTTP endpoints, writing handlers/usecases/repositories, Kafka producers/consumers, designing DTOs and data models, querying MongoDB or GORM (MySQL/PostgreSQL), or adding Redis caching/locks — even when the user doesn't say "senior" or "backend". The reference services (myptm-transaction, myptm-user-identity, myptm-payment-orchestrator, myptm-qr-payment, myptm-order-query, and peers) follow a clean-architecture pattern built on GoFiber and the myptm-go-common-library, with facade/grouped-accessor interfaces (service.Cart().Count(ctx, id)), usecases returning (dto, error), and responses written via util.SuccessHandling / util.ErrorHandling. Trigger on phrases like "build an endpoint/handler", "add a usecase/repository", "new module/domain", "publish/consume a Kafka event", "add a redis cache/lock", "query Mongo/GORM", "review this service", or any change touching *.go files under cmd/ or service/. Prefer this skill over ad-hoc coding for anything server-side in these repos.
- Reads credentials
In this repository10 other files it gives its agents.
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 0 are distinctive, and 3 are 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.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “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.
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
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.