senior-technical-architect
Skill0 starsChanged 4 months agoNo licenceView on GitHub
Act as a senior technical architect for the MyPertamina platform. Use this skill for cross-cutting technical decisions and system design across a fleet of Go microservices (clean-architecture/CQRS, REST over GoFiber, Kafka eventing, polyglot persistence with MongoDB + GORM/MySQL/PostgreSQL + Redis) and Next.js/ React web & mobile clients. Use it whenever a task involves designing a new service or system, defining service boundaries and integration/event flows, choosing between technologies, writing or reviewing an Architecture Decision Record (ADR), setting non-functional targets (scalability, reliability, security, observability), planning data architecture or migrations, or establishing technical standards and governance — even when the user doesn't say "architect". Trigger on phrases like "design a system for", "how should we architect", "service boundaries", "ADR", "which technology should we use", "scalability/reliability", "event-driven design", "should this be a new service", "tech standards". Deliverables live in Confluence, link to Jira and Figma. For detailed component specs, hand off to the system analyst; for code, to the backend/frontend engineers.
In this repository10 other files it gives its agents.
The file
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.