Most spec-driven setups fail the same way: a solid plan-implement skill gets used diligently for a week, then quietly abandoned the first time a deadline gets close. Nothing in a hand-rolled skill stops that drift. Superpowers answers the discipline problem directly — a skills package that makes brainstorming, planning, subagent review, and strict TDD mandatory steps the agent checks before every task.
OpenCode’s command-line interface turns the coding agent into a scriptable tool: the same agent environment runs in the interactive TUI and non-interactively from shell scripts, CI jobs, and Makefiles. Small tasks work within minutes, but serious use depends on repository instructions, permission boundaries, context discipline, and model selection.
Agent skills and MCP servers are often presented as competing ways to extend an AI agent. That framing is wrong: a skill teaches the agent how to work, while an MCP server gives it governed access to live capabilities. The useful question is not which standard wins, but where each responsibility should live.
This blog’s source of truth and CI live on GitLab. The public site is served from GitHub Pages at devopstales.github.io. Hugo builds in a container, the job writes into a separate Pages repository, and readers never see GitLab’s job logs—only the static tree.
Roadster’s default sidebar search sends queries to Google (or DuckDuckGo) with a site filter. That works until the corpus is large and you want typo tolerance, facets by section/tags, and results that stay on your domain. Algolia hosts the index; Hugo emits a JSON dump at build time; atomic-algolia pushes only the diff from GitLab CI after hugo succeeds.
Images are usually the heaviest part of a technical post. The pipeline on this site is deliberately small: convert assets to WebP, reference them from Markdown, let a Goldmark render hook add lazy-loading attributes, and initialize Medium Zoom for click-to-enlarge.
Crawlers still look for /robots.txt before they dig through your tree. Hugo can generate that file at build time from a template, so the Sitemap URL always matches your baseURL and you can add allow/disallow rules without maintaining a hand-copied static file.
Search and social previews on a Hugo blog are mostly template work: consistent titles, a real summary, a thumbnail, Open Graph / Twitter tags, structured data, and a sitemap. DevOpsTales does that in layouts/_default/baseof.html plus a JSON-LD partial—no SEO plugin required.