Super engineering devops
SUPER Skills catalogue: portable Markdown agent skills for AI vibe coding, SEO, AI SEO/GEO, marketing, design, AI agents, DevOps, security, automation, data, business, and operations.
npx -y skills add arpitexplores/skills-super --skill super-engineering-devopsAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Engineering and DevOps delivery: architecture, build, test, deploy, and operate reliable systems.
SKILL.md
1.7 KB, as published. Nobody here has run it
Super Engineering/DevOps
Overview
Build and run software with strong architecture, quality, and delivery practices.
User Intent Examples
- "Need help with DevOps & Deployment for my product/site."
- "Create a plan for Observability."
- "Audit or improve Full-Stack Engineering."
Workflow
- Clarify requirements, constraints, and success metrics.
- Select architecture and core tech stack.
- Design data models, APIs, and integration boundaries.
- Implement with tests and quality checks.
- Set up CI/CD and deployment strategy.
- Add observability and runbooks.
Minimal Intake Questions
- Primary goal or outcome
- Scope (pages, systems, teams, or timeframe)
- Constraints (tools, budget, timeline)
Output Format
- Architecture and design summary
- Implementation plan
- Test and QA plan
- CI/CD and deployment plan
- Observability checklist
Routing Map (Modules)
- DevOps & Deployment ->
references/modules/devops-deploy.md - Observability ->
references/modules/observability-engineer.md - Full-Stack Engineering ->
references/modules/senior-fullstack.md
Bundled References
references/modules/scripts/assets/agents/
Compatibility Notes
- If any module references slash commands or tool-specific paths, translate them into plain-language steps.
- Keep outputs platform-agnostic unless the user specifies a specific tool, stack, or agent.
Guardrails
- Do not claim performance gains without measurements.
- Keep testing requirements explicit.
- Prefer incremental delivery and rollback safety.